apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "54859" uid: 8d436a09-0933-4260-b916-bfa1d32629e7 spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-06T17:49:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.804463ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 1.62815ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 1.343308ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 1.030659ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 887.316µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:32Z" - latency: 1.501485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:12:32Z" - latency: 1.012371ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:11:32Z" - latency: 918.577µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:10:32Z" - latency: 985.272µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:09:32Z" - latency: 1.133525ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:08:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "55791" uid: 1aeb539c-eb17-4a6f-898a-56323bb88bc1 spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T17:48:32Z" message: 'load-balancer-api-external: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.803834ms message: 'load-balancer-api-external: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:32Z" - latency: 8.252411ms message: 'load-balancer-api-external: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:18:32Z" - latency: 3.484469ms message: 'load-balancer-api-external: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 8.316017ms message: 'load-balancer-api-external: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:17:32Z" - latency: 3.187151ms message: 'load-balancer-api-external: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 9.04714ms message: 'load-balancer-api-external: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:16:32Z" - latency: 4.750492ms message: 'load-balancer-api-external: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 6.304452ms message: 'load-balancer-api-external: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:15:32Z" - latency: 3.995736ms message: 'load-balancer-api-external: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 10.847956ms message: 'load-balancer-api-external: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "55790" uid: 56235865-5c09-42b9-bb06-51ea7c01f782 spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-06T17:48:32Z" message: 'load-balancer-api-internal: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.878593ms message: 'load-balancer-api-internal: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:32Z" - latency: 8.268489ms message: 'load-balancer-api-internal: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:18:32Z" - latency: 3.027416ms message: 'load-balancer-api-internal: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 8.326073ms message: 'load-balancer-api-internal: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:17:32Z" - latency: 5.817513ms message: 'load-balancer-api-internal: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 9.07712ms message: 'load-balancer-api-internal: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:16:32Z" - latency: 4.650596ms message: 'load-balancer-api-internal: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 6.379255ms message: 'load-balancer-api-internal: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:15:32Z" - latency: 4.006779ms message: 'load-balancer-api-internal: tcp connection to a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 10.806242ms message: 'load-balancer-api-internal: resolved host name a24db72f7093546ebb78a7f446cb991f-3442e0978c4f8a80.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-06T18:14:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-network-check-target-ip-10-0-128-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "54858" uid: 784db0c9-34fe-4f0c-9a44-cedea72d527d spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T17:49:32Z" message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.508277ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 2.566792ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 2.413717ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 2.519068ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 2.30795ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:32Z" - latency: 2.354081ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:12:32Z" - latency: 2.444052ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:11:32Z" - latency: 2.300534ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:10:32Z" - latency: 2.061445ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:09:32Z" - latency: 2.366056ms message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:08:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-network-check-target-ip-10-0-137-203 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "54857" uid: 8adb8b3e-01fe-486d-bc03-e58ab0d5018e spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-06T17:49:32Z" message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.809118ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 1.92031ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 1.889575ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 1.85356ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 1.856477ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:32Z" - latency: 1.943407ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:12:32Z" - latency: 2.087144ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:11:32Z" - latency: 1.990419ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:10:32Z" - latency: 1.922975ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:09:32Z" - latency: 1.909426ms message: 'network-check-target-ip-10-0-137-203: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:08:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-network-check-target-ip-10-0-138-108 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "54856" uid: c730368e-c30a-47ba-86e1-98d27065677e spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-06T17:49:32Z" message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 878.256µs message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 996.52µs message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 1.056315ms message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 876.198µs message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 888.223µs message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:13:32Z" - latency: 1.652994ms message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:12:32Z" - latency: 932.88µs message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:11:32Z" - latency: 1.032662ms message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:10:32Z" - latency: 1.317707ms message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:09:32Z" - latency: 883.411µs message: 'network-check-target-ip-10-0-138-108: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:08:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-06T17:42:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-108-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-108.ec2.internal uid: 2036e9fd-6245-4a51-8da4-944ad3d8a5a7 resourceVersion: "55789" uid: e9258024-93ee-41b8-82bc-d57f55263cb2 spec: sourcePod: network-check-source-989f8b8dc-zcmj7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-06T17:48:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.155824ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:18:32Z" - latency: 1.682845ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:18:32Z" - latency: 818.86µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:17:32Z" - latency: 1.759452ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:17:32Z" - latency: 892.118µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:16:32Z" - latency: 1.817089ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:16:32Z" - latency: 1.123458ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:15:32Z" - latency: 1.777452ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:15:32Z" - latency: 731.103µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-06T18:14:32Z" - latency: 1.879486ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-06T18:14:32Z" kind: List metadata: resourceVersion: ""