apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "153329" uid: 6a8b7e6e-d92b-413a-99fc-3358ebb4356b spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T19:39: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.41615ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:32Z" - latency: 1.720703ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:32Z" - latency: 1.135706ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:32Z" - latency: 1.474953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:32Z" - latency: 1.422539ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:32Z" - latency: 1.044258ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:32Z" - latency: 2.153639ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:32Z" - latency: 1.398714ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:14:32Z" - latency: 1.06764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:13:32Z" - latency: 10.895745ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:12:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "150703" uid: 33c824e9-48d9-4afa-b53b-f44a936509fb spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:38:32Z" message: 'load-balancer-api-external: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 10.612759ms message: 'load-balancer-api-external: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:32Z" - latency: 7.269174ms message: 'load-balancer-api-external: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:20:32Z" - latency: 10.420937ms message: 'load-balancer-api-external: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:32Z" - latency: 39.840385ms message: 'load-balancer-api-external: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:19:32Z" - latency: 11.492233ms message: 'load-balancer-api-external: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:32Z" - latency: 9.232941ms message: 'load-balancer-api-external: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:18:32Z" - latency: 5.123497ms message: 'load-balancer-api-external: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:32Z" - latency: 12.671115ms message: 'load-balancer-api-external: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:17:32Z" - latency: 6.643361ms message: 'load-balancer-api-external: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:32Z" - latency: 8.047308ms message: 'load-balancer-api-external: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:16:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "150705" uid: 0a7a3b3d-6aa5-497b-93c1-98a4909657ea spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T19:38:32Z" message: 'load-balancer-api-internal: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 13.391677ms message: 'load-balancer-api-internal: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:32Z" - latency: 7.289259ms message: 'load-balancer-api-internal: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:20:32Z" - latency: 10.488271ms message: 'load-balancer-api-internal: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:32Z" - latency: 39.777394ms message: 'load-balancer-api-internal: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:19:32Z" - latency: 11.048444ms message: 'load-balancer-api-internal: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:32Z" - latency: 9.200671ms message: 'load-balancer-api-internal: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:18:32Z" - latency: 5.11114ms message: 'load-balancer-api-internal: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:32Z" - latency: 12.731913ms message: 'load-balancer-api-internal: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:17:32Z" - latency: 6.502937ms message: 'load-balancer-api-internal: tcp connection to ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:32Z" - latency: 8.103447ms message: 'load-balancer-api-internal: resolved host name ae460b1a16a784ac3b0a6ca1c74cc418-75cef14e3b88e730.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T20:16:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-ip-10-0-132-214 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "153326" uid: 1001724b-b62f-4697-9771-b414ccbd029a spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:39:32Z" message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.01425ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:32Z" - latency: 1.053558ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:32Z" - latency: 1.897358ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:32Z" - latency: 1.575414ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:32Z" - latency: 1.224993ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:32Z" - latency: 1.030067ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:32Z" - latency: 1.113494ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:32Z" - latency: 1.854934ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:14:32Z" - latency: 1.311706ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:13:32Z" - latency: 20.575504ms message: 'network-check-target-ip-10-0-132-214: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:12:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-ip-10-0-141-42 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "153478" uid: c0eda2f8-54bb-4fa7-9b54-9b53daa86d97 spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:39:35Z" message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.519369ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:35Z" - latency: 935.329µs message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:35Z" - latency: 1.262773ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:35Z" - latency: 999.627µs message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:35Z" - latency: 2.97297ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:35Z" - latency: 2.290634ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:35Z" - latency: 2.785969ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:35Z" - latency: 869.226µs message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:14:35Z" - latency: 1.404449ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:13:35Z" - latency: 9.639798ms message: 'network-check-target-ip-10-0-141-42: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:12:35Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-ip-10-0-142-167 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "153660" uid: 1fc60943-87a1-4d85-b2f3-59e2f0ba6526 spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T19:39:37Z" message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.93839ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:21:37Z" - latency: 2.274132ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:37Z" - latency: 2.151646ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:37Z" - latency: 2.794372ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:37Z" - latency: 1.236079ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:37Z" - latency: 2.234372ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:37Z" - latency: 1.556999ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:15:37Z" - latency: 3.128848ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:14:37Z" - latency: 2.892864ms message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:13:37Z" - latency: 734.275µs message: 'network-check-target-ip-10-0-142-167: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:12:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T19:32:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-214-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-214.us-east-2.compute.internal uid: e879f380-3e17-4bba-b07a-70dbf9b278f7 resourceVersion: "150701" uid: e40fdc2e-bc60-4061-85aa-383ca0a44326 spec: sourcePod: network-check-source-6f78d59f99-kzbbk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T19:38:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.273305ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:20:32Z" - latency: 1.836393ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:20:32Z" - latency: 11.482085ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:19:32Z" - latency: 2.795185ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:19:32Z" - latency: 2.639103ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:18:32Z" - latency: 2.715508ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:18:32Z" - latency: 2.057788ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:17:32Z" - latency: 2.332267ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:17:32Z" - latency: 1.005456ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T20:16:32Z" - latency: 2.138841ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T20:16:32Z" kind: List metadata: resourceVersion: ""