apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "89817" uid: b53ac76a-69a5-486a-aeb0-caf3e3a990c5 spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T20:34:54Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.135126ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:54Z" - latency: 1.04475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:54Z" - latency: 934.438µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 1.303798ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 906.215µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 1.108153ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 1.362978ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 1.026314ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:54Z" - latency: 1.635324ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:54Z" - latency: 1.173527ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:14:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "88592" uid: 88ac3b78-cab3-4fa2-93c1-1ae3e018e635 spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T20:33:54Z" message: 'load-balancer-api-external: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.206626ms message: 'load-balancer-api-external: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 6.689141ms message: 'load-balancer-api-external: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:21:54Z" - latency: 53.536061ms message: 'load-balancer-api-external: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 6.657803ms message: 'load-balancer-api-external: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:20:54Z" - latency: 54.071082ms message: 'load-balancer-api-external: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 6.329183ms message: 'load-balancer-api-external: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:19:54Z" - latency: 53.179922ms message: 'load-balancer-api-external: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 6.300125ms message: 'load-balancer-api-external: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:18:54Z" - latency: 52.868035ms message: 'load-balancer-api-external: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 6.346681ms message: 'load-balancer-api-external: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "88593" uid: a0b4c7e5-7b35-4054-ae00-7dfe9e61dc2a spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T20:33:54Z" message: 'load-balancer-api-internal: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 53.638444ms message: 'load-balancer-api-internal: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 6.609495ms message: 'load-balancer-api-internal: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:21:54Z" - latency: 53.530113ms message: 'load-balancer-api-internal: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 6.714897ms message: 'load-balancer-api-internal: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:20:54Z" - latency: 54.080036ms message: 'load-balancer-api-internal: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 6.274973ms message: 'load-balancer-api-internal: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:19:54Z" - latency: 105.392609ms message: 'load-balancer-api-internal: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 6.252635ms message: 'load-balancer-api-internal: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:18:54Z" - latency: 52.979079ms message: 'load-balancer-api-internal: tcp connection to a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 6.261238ms message: 'load-balancer-api-internal: resolved host name a387d27a2dc53463097c2534c2d2347e-212d01575edb5520.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:17:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-network-check-target-ip-10-0-135-188 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "89815" uid: 2bc746c3-cb35-4d13-8d19-8066a6e198cc spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:34:54Z" message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.290745ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:54Z" - latency: 1.919138ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:54Z" - latency: 1.909594ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 2.315342ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 2.382437ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 2.302925ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 2.338417ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 1.967918ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:54Z" - latency: 2.409326ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:54Z" - latency: 2.386546ms message: 'network-check-target-ip-10-0-135-188: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:14:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-network-check-target-ip-10-0-139-149 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "89814" uid: 71d6b14d-1f48-4e61-a8a3-669525cadef8 spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:34:54Z" message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 811.276µs message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:54Z" - latency: 896.12µs message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:54Z" - latency: 1.579368ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 1.660598ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 1.419463ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 1.363509ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 1.796325ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 987.225µs message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:54Z" - latency: 1.279434ms message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:54Z" - latency: 896.49µs message: 'network-check-target-ip-10-0-139-149: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:14:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-network-check-target-ip-10-0-139-195 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "89816" uid: fd6ecc74-bac4-4c48-a364-783387a997c7 spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T20:34:54Z" message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.764194ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:23:54Z" - latency: 1.567213ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:22:54Z" - latency: 1.832228ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 1.964301ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 1.795599ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 2.093065ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 1.862414ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 1.820058ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:16:54Z" - latency: 1.789709ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:15:54Z" - latency: 1.7991ms message: 'network-check-target-ip-10-0-139-195: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:14:54Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T20:27:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-149-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-149.us-west-1.compute.internal uid: 9b915f5d-0c32-49db-a3f2-d43f8d79bd17 resourceVersion: "88590" uid: e0319cdc-0d95-43d5-af0b-2aea1277a9b2 spec: sourcePod: network-check-source-6f78d59f99-bhrtb targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T20:33:54Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.457144ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:21:54Z" - latency: 1.993117ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:21:54Z" - latency: 902.739µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:20:54Z" - latency: 1.971727ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:20:54Z" - latency: 955.903µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:19:54Z" - latency: 1.723809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:19:54Z" - latency: 979.954µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:18:54Z" - latency: 1.808052ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:18:54Z" - latency: 1.008183ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:17:54Z" - latency: 1.985397ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:17:54Z" kind: List metadata: resourceVersion: ""