apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "77849" uid: 044fbc53-a003-44be-b0b9-ec4475d9caca spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-08-04T19:25:42Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 850.764µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:14:42Z" - latency: 1.384151ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:13:42Z" - latency: 988.54µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 1.195782ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 1.155462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 968.683µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 1.381656ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 1.08497ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:07:42Z" - latency: 1.094612ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:06:42Z" - latency: 1.585193ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "75887" uid: 2def1a3a-85cf-42cc-9da8-be6da105bec3 spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T19:24:42Z" message: 'load-balancer-api-external: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.455717ms message: 'load-balancer-api-external: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 11.134118ms message: 'load-balancer-api-external: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:12:42Z" - latency: 5.234424ms message: 'load-balancer-api-external: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 8.683053ms message: 'load-balancer-api-external: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:11:42Z" - latency: 4.277547ms message: 'load-balancer-api-external: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 12.086065ms message: 'load-balancer-api-external: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:10:42Z" - latency: 5.263199ms message: 'load-balancer-api-external: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 8.89227ms message: 'load-balancer-api-external: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:09:42Z" - latency: 3.922501ms message: 'load-balancer-api-external: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 8.737351ms message: 'load-balancer-api-external: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:08:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "75886" uid: 1b1c4582-505e-4f06-b311-01cb2a8fc5a8 spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-08-04T19:24:42Z" message: 'load-balancer-api-internal: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.466012ms message: 'load-balancer-api-internal: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 11.225183ms message: 'load-balancer-api-internal: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:12:42Z" - latency: 3.986294ms message: 'load-balancer-api-internal: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 8.722508ms message: 'load-balancer-api-internal: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:11:42Z" - latency: 4.28574ms message: 'load-balancer-api-internal: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 12.115936ms message: 'load-balancer-api-internal: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:10:42Z" - latency: 5.247078ms message: 'load-balancer-api-internal: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 8.931656ms message: 'load-balancer-api-internal: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:09:42Z" - latency: 4.126742ms message: 'load-balancer-api-internal: tcp connection to a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 8.760381ms message: 'load-balancer-api-internal: resolved host name a75c7d9625af84829aae734a52e181c2-2a47b3d592b11321.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-08-04T20:08:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-network-check-target-ip-10-0-136-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "77848" uid: bae5b8bb-658a-4469-9cd3-9c6c18d5b710 spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-08-04T19:25:42Z" message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.195016ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:14:42Z" - latency: 2.195643ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:13:42Z" - latency: 2.410613ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 1.976474ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 2.099527ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 1.999291ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 2.222796ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 2.153616ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:07:42Z" - latency: 2.230638ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:06:42Z" - latency: 1.880196ms message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-network-check-target-ip-10-0-140-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "77847" uid: a6dac2bf-541c-4b12-9d1b-5929276be35a spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T19:25:42Z" message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.119422ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:14:42Z" - latency: 2.149953ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:13:42Z" - latency: 2.209526ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 2.062377ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 2.440318ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 2.315605ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 2.353842ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 2.283286ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:07:42Z" - latency: 2.275149ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:06:42Z" - latency: 2.257946ms message: 'network-check-target-ip-10-0-140-250: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-network-check-target-ip-10-0-143-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "77846" uid: a6a98c5c-065c-49a9-8b7e-f11693687258 spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-08-04T19:25:42Z" message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 849.833µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:14:42Z" - latency: 978.964µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:13:42Z" - latency: 941.444µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 880.346µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 1.355783ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 956.483µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 910.489µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 979.946µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:07:42Z" - latency: 932.366µs message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:06:42Z" - latency: 1.691756ms message: 'network-check-target-ip-10-0-143-62: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:05:42Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-08-04T19:18:41Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-62-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-62.ec2.internal uid: c2e85d6f-4ffc-4bc4-a721-75e9f5f782cf resourceVersion: "75885" uid: 2b5cda8c-f177-4c8a-8f4a-21ed91611a2f spec: sourcePod: network-check-source-65bdbbff45-8zhmc targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-08-04T19:24:42Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.196358ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:12:42Z" - latency: 1.932514ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T20:12:42Z" - latency: 909.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:11:42Z" - latency: 1.788248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T20:11:42Z" - latency: 1.082081ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:10:42Z" - latency: 1.955521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T20:10:42Z" - latency: 963.468µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:09:42Z" - latency: 1.903083ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T20:09:42Z" - latency: 1.324562ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-08-04T20:08:42Z" - latency: 1.746826ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-08-04T20:08:42Z" kind: List metadata: resourceVersion: ""