apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63106" uid: a96a8101-3a43-4a52-ba44-c9e07f24da9a spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T16:51:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 968.188µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 1.198114ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 978.731µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 921.501µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 1.128234ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 1.04316ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:21:40Z" - latency: 1.210651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:20:40Z" - latency: 1.033969ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:19:40Z" - latency: 1.421705ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:18:40Z" - latency: 1.040424ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63108" uid: 5a6ae5a6-bc02-4066-b648-588c15363e09 spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T16:50:40Z" message: 'load-balancer-api-external: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.256482ms message: 'load-balancer-api-external: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 9.189675ms message: 'load-balancer-api-external: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:26:40Z" - latency: 5.047446ms message: 'load-balancer-api-external: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 8.378325ms message: 'load-balancer-api-external: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:25:40Z" - latency: 3.194128ms message: 'load-balancer-api-external: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 8.420176ms message: 'load-balancer-api-external: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:24:40Z" - latency: 4.584688ms message: 'load-balancer-api-external: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 8.537277ms message: 'load-balancer-api-external: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:23:40Z" - latency: 4.880154ms message: 'load-balancer-api-external: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 8.483094ms message: 'load-balancer-api-external: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:22:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63107" uid: 248ffeb2-0b9b-4db4-ad1c-f055c067f44f spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T16:50:40Z" message: 'load-balancer-api-internal: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.210464ms message: 'load-balancer-api-internal: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 9.217272ms message: 'load-balancer-api-internal: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:26:40Z" - latency: 5.032776ms message: 'load-balancer-api-internal: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 8.445179ms message: 'load-balancer-api-internal: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:25:40Z" - latency: 3.754877ms message: 'load-balancer-api-internal: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 8.344246ms message: 'load-balancer-api-internal: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:24:40Z" - latency: 3.525843ms message: 'load-balancer-api-internal: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 8.449087ms message: 'load-balancer-api-internal: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:23:40Z" - latency: 4.880385ms message: 'load-balancer-api-internal: tcp connection to a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 8.507227ms message: 'load-balancer-api-internal: resolved host name a245e34dd3d554b72a3da15bff19b291-f055fe87d68f08ee.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T17:22:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-132-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63102" uid: 324f91ee-2cc7-46e4-af47-c632cf719727 spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-22T16:51:40Z" message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 713.864µs message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 1.945685ms message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 804.874µs message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 759.589µs message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 710.824µs message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 737.357µs message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:21:40Z" - latency: 1.459029ms message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:20:40Z" - latency: 1.803598ms message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:19:40Z" - latency: 1.533235ms message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:18:40Z" - latency: 818.051µs message: 'network-check-target-ip-10-0-132-57: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-132-94 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63104" uid: e4e4915a-24f9-4970-b5e5-baf75fabc5ca spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T16:51:40Z" message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.966915ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 2.448025ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 2.090223ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 1.841259ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 2.068422ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 1.55594ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:21:40Z" - latency: 1.769287ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:20:40Z" - latency: 1.93965ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:19:40Z" - latency: 1.646188ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:18:40Z" - latency: 2.000673ms message: 'network-check-target-ip-10-0-132-94: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-network-check-target-ip-10-0-136-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63103" uid: fc3427c6-c3fc-4bdf-a9d4-ed7f525c71c1 spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T16:51:40Z" message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.96205ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 3.069128ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 2.179094ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 2.400948ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 2.305317ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 2.250714ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:21:40Z" - latency: 2.238992ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:20:40Z" - latency: 2.695377ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:19:40Z" - latency: 2.154979ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:18:40Z" - latency: 2.122479ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:17:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T16:44:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-57-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-57.ec2.internal uid: d6007a1b-6995-4dcf-b93f-6f919736a9fe resourceVersion: "63105" uid: 4e9b3f21-e69e-40da-ab4a-002e7f8bfc95 spec: sourcePod: network-check-source-7bc5b6bf85-pg865 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T16:50:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 711.894µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:26:40Z" - latency: 2.040396ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:26:40Z" - latency: 2.176689ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:25:40Z" - latency: 1.80119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:25:40Z" - latency: 713.529µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:24:40Z" - latency: 1.622249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:24:40Z" - latency: 842.498µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:23:40Z" - latency: 2.078545ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:23:40Z" - latency: 722.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T17:22:40Z" - latency: 1.728099ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T17:22:40Z" kind: List metadata: resourceVersion: ""