apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "54614" uid: 442660f7-4d61-4f0a-9a43-023949d1e71d spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T22:37:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.035744ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 1.026126ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 933.218µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 1.083036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 978.121µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:24Z" - latency: 885.554µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:24Z" - latency: 2.209864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:24Z" - latency: 1.076285ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:24Z" - latency: 944.44µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:24Z" - latency: 1.190551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "55537" uid: be94c3c9-dfe2-488e-b53d-813a553b2289 spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T22:36:24Z" message: 'load-balancer-api-external: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.409804ms message: 'load-balancer-api-external: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:06:24Z" - latency: 6.511886ms message: 'load-balancer-api-external: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:06:24Z" - latency: 4.417439ms message: 'load-balancer-api-external: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 6.467349ms message: 'load-balancer-api-external: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:05:24Z" - latency: 5.439706ms message: 'load-balancer-api-external: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 8.12462ms message: 'load-balancer-api-external: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:04:24Z" - latency: 3.940458ms message: 'load-balancer-api-external: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 7.436204ms message: 'load-balancer-api-external: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:03:24Z" - latency: 4.437317ms message: 'load-balancer-api-external: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 7.193081ms message: 'load-balancer-api-external: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:02:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "55536" uid: d91d1a28-8e4a-4e35-9238-493e7f2e3905 spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T22:36:24Z" message: 'load-balancer-api-internal: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.176769ms message: 'load-balancer-api-internal: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:06:24Z" - latency: 6.454408ms message: 'load-balancer-api-internal: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:06:24Z" - latency: 4.326062ms message: 'load-balancer-api-internal: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 6.42008ms message: 'load-balancer-api-internal: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:05:24Z" - latency: 5.429636ms message: 'load-balancer-api-internal: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 8.144953ms message: 'load-balancer-api-internal: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:04:24Z" - latency: 4.200824ms message: 'load-balancer-api-internal: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 7.363763ms message: 'load-balancer-api-internal: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:03:24Z" - latency: 4.596337ms message: 'load-balancer-api-internal: tcp connection to a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 7.371848ms message: 'load-balancer-api-internal: resolved host name a8082d16bf4c84956a313ccd983ff840-591f23f1c8ca401a.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T23:02:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-network-check-target-ip-10-0-132-3 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "54611" uid: 4ccd9365-2435-4f5d-8127-bc9b97b127f2 spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:37:24Z" message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.612µs message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 1.369553ms message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 1.00369ms message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 905.754µs message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 957.263µs message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:24Z" - latency: 848.383µs message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:24Z" - latency: 1.370882ms message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:24Z" - latency: 952.086µs message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:24Z" - latency: 909.635µs message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:24Z" - latency: 1.552224ms message: 'network-check-target-ip-10-0-132-3: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-network-check-target-ip-10-0-135-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "54612" uid: 7ef0228c-4665-49bc-8af6-871be3cf24de spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:37:24Z" message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.545895ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 2.946505ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 2.549682ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 2.630746ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 2.709187ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:24Z" - latency: 2.339319ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:24Z" - latency: 2.486513ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:24Z" - latency: 2.318261ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:24Z" - latency: 2.609733ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:24Z" - latency: 2.584087ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-network-check-target-ip-10-0-136-56 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "54613" uid: e5aeb828-06da-4425-ac7f-f94122e3906a spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-06T22:37:24Z" message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.476426ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 2.824828ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 2.539085ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 2.414664ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 2.193142ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:01:24Z" - latency: 1.910988ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:00:24Z" - latency: 1.86268ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:59:24Z" - latency: 2.244504ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:58:24Z" - latency: 2.157289ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:57:24Z" - latency: 2.204844ms message: 'network-check-target-ip-10-0-136-56: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T22:56:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T22:30:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-3-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-3.ec2.internal uid: 882f7231-e36d-46c3-b203-83c7e2d658cf resourceVersion: "55535" uid: 7c8eac16-a44b-41f5-bc80-78b63ecc0724 spec: sourcePod: network-check-source-989f8b8dc-2hvdl targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T22:36:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.996µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:06:24Z" - latency: 1.836706ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:06:24Z" - latency: 909.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:05:24Z" - latency: 1.728769ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:05:24Z" - latency: 961.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:04:24Z" - latency: 2.711549ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:04:24Z" - latency: 995.868µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:03:24Z" - latency: 1.77801ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:03:24Z" - latency: 1.310165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T23:02:24Z" - latency: 1.785196ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T23:02:24Z" kind: List metadata: resourceVersion: ""