apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "169221" uid: fc8ec146-6dd3-4ac9-8269-d082e5f551c6 spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T01:27:28Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.182627ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 1.274355ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 813.169µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 1.810619ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:09:28Z" - latency: 1.165985ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:08:28Z" - latency: 1.235621ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:07:28Z" - latency: 1.15723ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:06:28Z" - latency: 1.039377ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:05:28Z" - latency: 1.384861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:04:28Z" - latency: 1.784932ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:03:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "170779" uid: f82bb0e8-1566-45d2-b788-d540d33e007b spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T01:26:28Z" message: 'load-balancer-api-external: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 51.020072ms message: 'load-balancer-api-external: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:14:28Z" - latency: 7.853673ms message: 'load-balancer-api-external: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:14:28Z" - latency: 53.402509ms message: 'load-balancer-api-external: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:13:28Z" - latency: 7.03675ms message: 'load-balancer-api-external: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:13:28Z" - latency: 57.110462ms message: 'load-balancer-api-external: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 9.151461ms message: 'load-balancer-api-external: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:12:28Z" - latency: 55.552113ms message: 'load-balancer-api-external: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 8.496631ms message: 'load-balancer-api-external: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:11:28Z" - latency: 55.051662ms message: 'load-balancer-api-external: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 6.220453ms message: 'load-balancer-api-external: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:10:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "170780" uid: 38c45d9e-c8d5-47ab-b298-ce9e86a3488f spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T01:26:28Z" message: 'load-balancer-api-internal: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.570502ms message: 'load-balancer-api-internal: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:14:28Z" - latency: 7.706124ms message: 'load-balancer-api-internal: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:14:28Z" - latency: 54.644217ms message: 'load-balancer-api-internal: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:13:28Z" - latency: 7.160544ms message: 'load-balancer-api-internal: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:13:28Z" - latency: 57.344201ms message: 'load-balancer-api-internal: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 9.250109ms message: 'load-balancer-api-internal: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:12:28Z" - latency: 55.51581ms message: 'load-balancer-api-internal: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 8.630329ms message: 'load-balancer-api-internal: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:11:28Z" - latency: 55.088981ms message: 'load-balancer-api-internal: tcp connection to aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 6.312232ms message: 'load-balancer-api-internal: resolved host name aece31dc849e6402abdece8830c7a683-e1048f7a7a1c1f18.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T03:10:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-network-check-target-ip-10-0-136-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "169220" uid: d0d34fcb-4ca0-4c97-9d4d-ff1fe525e541 spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T01:27:28Z" message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.538612ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 2.324407ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 2.425567ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 2.62444ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:09:28Z" - latency: 2.278478ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:08:28Z" - latency: 2.105885ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:07:28Z" - latency: 2.644358ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:06:28Z" - latency: 2.727735ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:05:28Z" - latency: 2.51926ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:04:28Z" - latency: 2.011769ms message: 'network-check-target-ip-10-0-136-16: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:03:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-network-check-target-ip-10-0-138-19 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "169218" uid: d6878917-a79a-458e-844d-f748c3a8c7cf spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T01:27:28Z" message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.624927ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 1.017774ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 797.748µs message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 1.261155ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:09:28Z" - latency: 1.258199ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:08:28Z" - latency: 1.005329ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:07:28Z" - latency: 980.198µs message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:06:28Z" - latency: 1.750894ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:05:28Z" - latency: 846.511µs message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:04:28Z" - latency: 1.394525ms message: 'network-check-target-ip-10-0-138-19: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:03:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-network-check-target-ip-10-0-140-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "169219" uid: ac8d35b6-2036-49a5-9b90-c8210904644c spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T01:27:28Z" message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.508659ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 2.03452ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 1.913266ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 2.178215ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:09:28Z" - latency: 2.2874ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:08:28Z" - latency: 1.971494ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:07:28Z" - latency: 2.262492ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:06:28Z" - latency: 1.734269ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:05:28Z" - latency: 2.120079ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:04:28Z" - latency: 2.087083ms message: 'network-check-target-ip-10-0-140-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:03:28Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T01:20:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-19-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-19.us-west-2.compute.internal uid: 395dcde2-48f2-47d2-a2c1-b8d83990e36c resourceVersion: "170778" uid: 3fa1ffd2-98ea-4115-8333-dd03733a9680 spec: sourcePod: network-check-source-6f78d59f99-9rfn6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T01:26:28Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.274018ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:14:28Z" - latency: 2.202653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T03:14:28Z" - latency: 1.806612ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:13:28Z" - latency: 1.769297ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T03:13:28Z" - latency: 1.257172ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:12:28Z" - latency: 2.544493ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T03:12:28Z" - latency: 854.251µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:11:28Z" - latency: 1.881381ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T03:11:28Z" - latency: 895.537µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T03:10:28Z" - latency: 1.740583ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T03:10:28Z" kind: List metadata: resourceVersion: ""