apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64862" uid: 46dafe8c-f4d9-43f9-a861-c5bddcc1134a spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-21T04:19:05Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.245197ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 1.119861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 766.61µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 1.079692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 786.445µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 1.294158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:05Z" - latency: 1.167908ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:05Z" - latency: 1.294202ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:05Z" - latency: 1.489524ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:05Z" - latency: 1.099243ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64863" uid: 67da89be-2f0d-4e39-ae2e-74e5f45d2082 spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T04:18:05Z" message: 'load-balancer-api-external: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.885486ms message: 'load-balancer-api-external: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 8.887601ms message: 'load-balancer-api-external: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:54:05Z" - latency: 4.72138ms message: 'load-balancer-api-external: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 8.446156ms message: 'load-balancer-api-external: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:53:05Z" - latency: 3.755616ms message: 'load-balancer-api-external: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 8.623138ms message: 'load-balancer-api-external: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:52:05Z" - latency: 4.786573ms message: 'load-balancer-api-external: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 9.84274ms message: 'load-balancer-api-external: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:51:05Z" - latency: 3.685135ms message: 'load-balancer-api-external: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 8.939705ms message: 'load-balancer-api-external: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:50:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64864" uid: fa619e50-cf27-4789-ac6c-92153b438cb5 spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-21T04:18:05Z" message: 'load-balancer-api-internal: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.874543ms message: 'load-balancer-api-internal: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 8.755197ms message: 'load-balancer-api-internal: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:54:05Z" - latency: 5.404642ms message: 'load-balancer-api-internal: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 8.509811ms message: 'load-balancer-api-internal: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:53:05Z" - latency: 3.890288ms message: 'load-balancer-api-internal: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 8.713061ms message: 'load-balancer-api-internal: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:52:05Z" - latency: 4.76587ms message: 'load-balancer-api-internal: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 9.785196ms message: 'load-balancer-api-internal: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:51:05Z" - latency: 3.703253ms message: 'load-balancer-api-internal: tcp connection to a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 8.922997ms message: 'load-balancer-api-internal: resolved host name a4455bdb64fb349088fa3395215f793b-3558c3542f9d813a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-21T04:50:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-network-check-target-ip-10-0-130-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64858" uid: 8ad01deb-7562-4fef-877b-52317123a32c spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T04:19:05Z" message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 953.492µs message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 1.240606ms message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 871.857µs message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 857.373µs message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 1.488968ms message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 863.901µs message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:05Z" - latency: 755.598µs message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:05Z" - latency: 1.623582ms message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:05Z" - latency: 979.225µs message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:05Z" - latency: 1.041357ms message: 'network-check-target-ip-10-0-130-0: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-network-check-target-ip-10-0-135-112 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64861" uid: 311e8d69-0a1f-4494-b778-9526512fb841 spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-21T04:19:05Z" message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.142554ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 1.900213ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 1.714242ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 2.126421ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 2.130962ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 2.263552ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:05Z" - latency: 1.85883ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:05Z" - latency: 1.967995ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:05Z" - latency: 2.189053ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:05Z" - latency: 2.583762ms message: 'network-check-target-ip-10-0-135-112: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-network-check-target-ip-10-0-143-205 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64859" uid: 0cc65e93-082d-4264-a1d4-0b3eb91d3fbb spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-21T04:19:05Z" message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.29668ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 1.809595ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 1.762959ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 2.131363ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 1.684323ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 2.167019ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:49:05Z" - latency: 2.271227ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:48:05Z" - latency: 2.186386ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:47:05Z" - latency: 2.009005ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:46:05Z" - latency: 2.016047ms message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:45:05Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-21T04:12:04Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-0-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-0.ec2.internal uid: 221577f9-682e-4f2c-b002-c86982288d41 resourceVersion: "64860" uid: 76f4a50b-e275-4bf5-81f3-2b8bbe17135b spec: sourcePod: network-check-source-7bc5b6bf85-9wdf7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-21T04:18:05Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.805µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:54:05Z" - latency: 1.785642ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:54:05Z" - latency: 747.394µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:53:05Z" - latency: 2.082683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:53:05Z" - latency: 1.142082ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:52:05Z" - latency: 1.526737ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:52:05Z" - latency: 1.142474ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:51:05Z" - latency: 1.81408ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:51:05Z" - latency: 881.651µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-21T04:50:05Z" - latency: 1.726313ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-21T04:50:05Z" kind: List metadata: resourceVersion: ""