apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "100343" uid: 2e6a78bc-3b36-44d5-b50b-ed5572cef4c1 spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:20:17Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.174926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:17Z" - latency: 1.395051ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:17Z" - latency: 864.559µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:17Z" - latency: 861.837µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:17Z" - latency: 1.328341ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 1.087672ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 909.716µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 1.180262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 1.227896ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 2.673381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "98239" uid: 7d742f7d-edcf-4878-85dc-3029af97fdaf spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:19:17Z" message: 'load-balancer-api-external: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.871092ms message: 'load-balancer-api-external: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 7.380598ms message: 'load-balancer-api-external: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:19:17Z" - latency: 58.733101ms message: 'load-balancer-api-external: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 6.122734ms message: 'load-balancer-api-external: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:18:17Z" - latency: 57.775313ms message: 'load-balancer-api-external: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 8.749718ms message: 'load-balancer-api-external: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:17:17Z" - latency: 57.192735ms message: 'load-balancer-api-external: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 10.492271ms message: 'load-balancer-api-external: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:16:17Z" - latency: 53.836062ms message: 'load-balancer-api-external: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 6.760933ms message: 'load-balancer-api-external: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:15:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "98240" uid: eaeb8d8c-1c49-47b3-b398-140bf43118d9 spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:19:17Z" message: 'load-balancer-api-internal: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 65.25924ms message: 'load-balancer-api-internal: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 7.427557ms message: 'load-balancer-api-internal: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:19:17Z" - latency: 59.335733ms message: 'load-balancer-api-internal: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 6.159452ms message: 'load-balancer-api-internal: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:18:17Z" - latency: 55.872725ms message: 'load-balancer-api-internal: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 8.838339ms message: 'load-balancer-api-internal: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:17:17Z" - latency: 57.173637ms message: 'load-balancer-api-internal: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 10.558802ms message: 'load-balancer-api-internal: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:16:17Z" - latency: 53.824281ms message: 'load-balancer-api-internal: tcp connection to a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 6.864419ms message: 'load-balancer-api-internal: resolved host name a37cf823f4ff54d85b23692eedd79e51-8af2da30c05d0787.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:15:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-network-check-target-ip-10-0-132-134 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "100342" uid: 007f668a-1b05-4b4b-98db-8c27989bd07a spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:20:17Z" message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.397673ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:17Z" - latency: 2.667034ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:17Z" - latency: 2.556895ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:17Z" - latency: 2.525278ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:17Z" - latency: 2.441443ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 2.51661ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 2.457631ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 2.821701ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 2.512776ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 1.934387ms message: 'network-check-target-ip-10-0-132-134: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-network-check-target-ip-10-0-137-220 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "100340" uid: 34c0f90f-2baa-4b0e-9389-68e18fa10f34 spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:20:17Z" message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 883.676µs message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:17Z" - latency: 931.826µs message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:17Z" - latency: 1.330966ms message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:17Z" - latency: 878.438µs message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:17Z" - latency: 914.463µs message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 1.156174ms message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 1.093794ms message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 1.305062ms message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 993.728µs message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 1.626452ms message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-network-check-target-ip-10-0-142-237 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "100341" uid: bd3718ee-c56e-4f36-bfb0-a4b6670ca1f7 spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:20:17Z" message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.127093ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:23:17Z" - latency: 2.550825ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:22:17Z" - latency: 2.170839ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:21:17Z" - latency: 2.160004ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:20:17Z" - latency: 2.10934ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 2.662296ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 2.782203ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 2.595958ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 2.067559ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 2.721688ms message: 'network-check-target-ip-10-0-142-237: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:14:17Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:13:17Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-137-220-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-137-220.us-west-1.compute.internal uid: a4a0ec5f-3cfd-4e9f-aa85-c101534d5c88 resourceVersion: "98236" uid: 90aa17e9-55ba-41c3-b389-c5eaf9d719fd spec: sourcePod: network-check-source-6f78d59f99-rv9lg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:19:17Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.398384ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:19:17Z" - latency: 1.797457ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:19:17Z" - latency: 1.203367ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:18:17Z" - latency: 1.762938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:18:17Z" - latency: 998.213µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:17:17Z" - latency: 2.690961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:17:17Z" - latency: 1.04061ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:16:17Z" - latency: 2.184629ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:16:17Z" - latency: 958.626µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:15:17Z" - latency: 1.808279ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:15:17Z" kind: List metadata: resourceVersion: ""