apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26456" uid: 6b398b3b-4f9d-420a-81ec-e4a9df6ad6da spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:46:18Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.075926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:18Z" - latency: 1.209105ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 1.226337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 924.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 959.622µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 1.058474ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 1.118456ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:22:18Z" - latency: 1.246207ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:21:18Z" - latency: 1.111458ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:20:18Z" - latency: 1.176304ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:19:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26186" uid: 86565af1-3e6f-4172-9712-1595c1bd1ce1 spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:45:18Z" message: 'load-balancer-api-external: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.694289ms message: 'load-balancer-api-external: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 9.936532ms message: 'load-balancer-api-external: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:27:18Z" - latency: 18.397887ms message: 'load-balancer-api-external: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 9.688849ms message: 'load-balancer-api-external: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:26:18Z" - latency: 3.34781378s message: 'load-balancer-api-external: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 8.443049ms message: 'load-balancer-api-external: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:25:18Z" - latency: 14.964629ms message: 'load-balancer-api-external: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 8.436179ms message: 'load-balancer-api-external: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:24:18Z" - latency: 18.333331ms message: 'load-balancer-api-external: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 8.494029ms message: 'load-balancer-api-external: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:23:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26185" uid: ba1d13c9-bba6-4c0e-ae08-9e524cf2f67f spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T18:45:18Z" message: 'load-balancer-api-internal: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 18.304703ms message: 'load-balancer-api-internal: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 9.886341ms message: 'load-balancer-api-internal: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:27:18Z" - latency: 18.415024ms message: 'load-balancer-api-internal: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 9.592416ms message: 'load-balancer-api-internal: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:26:18Z" - latency: 18.547843ms message: 'load-balancer-api-internal: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 8.411848ms message: 'load-balancer-api-internal: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:25:18Z" - latency: 37.284752ms message: 'load-balancer-api-internal: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 8.385734ms message: 'load-balancer-api-internal: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:24:18Z" - latency: 19.611346ms message: 'load-balancer-api-internal: tcp connection to a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 8.454761ms message: 'load-balancer-api-internal: resolved host name a90dbb53e21b64025bd8a889899b3b8c-58613a4e2a30bb43.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T19:23:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-131-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26453" uid: 74284366-d67a-4ff4-88a3-a5f1f637cca0 spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:18Z" message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040387ms message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:18Z" - latency: 1.00308ms message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 964.003µs message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 1.914764ms message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 919.804µs message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 1.029045ms message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 942.336µs message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:22:18Z" - latency: 1.373881ms message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:21:18Z" - latency: 1.374168ms message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:20:18Z" - latency: 974.722µs message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:19:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-135-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26455" uid: f034a4f3-4083-446f-84c1-67fed5705740 spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:18Z" message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.68716ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:18Z" - latency: 2.30782ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 2.348578ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 2.562864ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 2.740797ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 2.442031ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 2.622025ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:22:18Z" - latency: 2.815649ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:21:18Z" - latency: 3.21778ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:20:18Z" - latency: 2.441905ms message: 'network-check-target-ip-10-0-135-218: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:19:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-137-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26454" uid: 918ec52f-dee8-495f-ab40-2ed6fb6a974b spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:46:18Z" message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.545449ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:28:18Z" - latency: 2.346546ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 2.183124ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 2.165381ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 2.090311ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 2.310921ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 2.139574ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:22:18Z" - latency: 2.31861ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:21:18Z" - latency: 1.977513ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:20:18Z" - latency: 2.294994ms message: 'network-check-target-ip-10-0-137-165: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:19:18Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T18:39:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-21-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-21.ec2.internal uid: 9b3d3c94-9d3c-43fd-8158-86f307beca27 resourceVersion: "26184" uid: 746c3488-6c13-483c-aa3e-c138c25eb96c spec: sourcePod: network-check-source-6f78d59f99-487nw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T18:45:18Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.2612ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:27:18Z" - latency: 1.900915ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:27:18Z" - latency: 966.919µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:26:18Z" - latency: 1.797349ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:26:18Z" - latency: 809.593µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:25:18Z" - latency: 2.229693ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:25:18Z" - latency: 941.637µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:24:18Z" - latency: 1.934531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:24:18Z" - latency: 899.279µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T19:23:18Z" - latency: 2.074582ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T19:23:18Z" kind: List metadata: resourceVersion: ""