apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "44898" uid: 03826d3c-130c-4812-bf76-798bce04823d spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-11T19:36:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 799.233µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 1.45475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 1.337111ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 1.492693ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:54:44Z" - latency: 1.19753ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:53:44Z" - latency: 1.161147ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:52:44Z" - latency: 1.736801ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:51:44Z" - latency: 1.202762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:50:44Z" - latency: 831.533µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:49:44Z" - latency: 870.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:48:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "46588" uid: 9400bee4-46aa-4cfa-9b9d-f33b1dedda7a spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T19:35:44Z" message: 'load-balancer-api-external: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.50297ms message: 'load-balancer-api-external: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:59:44Z" - latency: 7.043857ms message: 'load-balancer-api-external: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:59:44Z" - latency: 4.919121ms message: 'load-balancer-api-external: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:58:44Z" - latency: 6.760199ms message: 'load-balancer-api-external: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:58:44Z" - latency: 4.748843ms message: 'load-balancer-api-external: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 6.82105ms message: 'load-balancer-api-external: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:57:44Z" - latency: 5.254963ms message: 'load-balancer-api-external: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 6.261525ms message: 'load-balancer-api-external: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:56:44Z" - latency: 5.188548ms message: 'load-balancer-api-external: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 7.00952ms message: 'load-balancer-api-external: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:55:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "46587" uid: 3fe4268f-8968-4014-a2f2-e459854c4533 spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-11T19:35:44Z" message: 'load-balancer-api-internal: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.41872ms message: 'load-balancer-api-internal: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:59:44Z" - latency: 6.955634ms message: 'load-balancer-api-internal: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:59:44Z" - latency: 4.932081ms message: 'load-balancer-api-internal: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:58:44Z" - latency: 6.659513ms message: 'load-balancer-api-internal: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:58:44Z" - latency: 4.804697ms message: 'load-balancer-api-internal: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 6.804393ms message: 'load-balancer-api-internal: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:57:44Z" - latency: 5.272275ms message: 'load-balancer-api-internal: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 6.151132ms message: 'load-balancer-api-internal: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:56:44Z" - latency: 4.197875ms message: 'load-balancer-api-internal: tcp connection to a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 6.9479ms message: 'load-balancer-api-internal: resolved host name a7af4b5bcca284f9394f3af3a8627e81-d63641c153668ee5.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-11T19:55:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-ip-10-0-137-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "44897" uid: f975617d-eb49-4a93-bf44-220d5f7c9561 spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-11T19:36:44Z" message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.167933ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 2.026454ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 2.217825ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 2.752071ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:54:44Z" - latency: 2.033272ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:53:44Z" - latency: 2.241541ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:52:44Z" - latency: 2.371068ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:51:44Z" - latency: 2.432543ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:50:44Z" - latency: 1.945904ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:49:44Z" - latency: 1.839727ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:48:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-ip-10-0-139-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "44896" uid: b320826b-5efb-475d-b5b1-52801f0b0ec7 spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-11T19:36:44Z" message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.568502ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 2.017669ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 1.999495ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 2.219387ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:54:44Z" - latency: 1.98519ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:53:44Z" - latency: 1.94206ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:52:44Z" - latency: 2.187825ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:51:44Z" - latency: 1.929045ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:50:44Z" - latency: 1.78634ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:49:44Z" - latency: 1.946023ms message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:48:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-ip-10-0-140-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "44895" uid: 61651aae-5e88-4d7b-84fd-0ed8d0a59e77 spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-11T19:36:44Z" message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.004786ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 1.622343ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 959.257µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 991.734µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:54:44Z" - latency: 849.624µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:53:44Z" - latency: 926.992µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:52:44Z" - latency: 1.93599ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:51:44Z" - latency: 1.417741ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:50:44Z" - latency: 1.142648ms message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:49:44Z" - latency: 983.195µs message: 'network-check-target-ip-10-0-140-225: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:48:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-11T19:29:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-225-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-225.ec2.internal uid: 2e09d1dd-2a55-4390-9022-dff40cf5b0f9 resourceVersion: "46586" uid: add77fd5-b189-4ebf-9228-63f156e3bab2 spec: sourcePod: network-check-source-6947749cfc-x6xxc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-11T19:35:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 822.308µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:59:44Z" - latency: 1.843596ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:59:44Z" - latency: 1.060699ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:58:44Z" - latency: 2.084491ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:58:44Z" - latency: 826.458µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:57:44Z" - latency: 1.823915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:57:44Z" - latency: 1.465168ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:56:44Z" - latency: 1.675615ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:56:44Z" - latency: 824.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-11T19:55:44Z" - latency: 1.805873ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-11T19:55:44Z" kind: List metadata: resourceVersion: ""