apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "142379" uid: 4e6fbf7a-1e6f-4b80-a8ae-88421c1dbdd3 spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T20:07:27Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.414588ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 2.051518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:55:27Z" - latency: 1.578373ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:54:27Z" - latency: 1.040927ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:53:27Z" - latency: 1.011485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:52:27Z" - latency: 1.060692ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:51:27Z" - latency: 1.465545ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:50:27Z" - latency: 1.567982ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:49:27Z" - latency: 994.932µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:48:27Z" - latency: 902.031µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "145855" uid: a7ef8550-d3a3-4b3b-8d9f-243352a65731 spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:06:27Z" message: 'load-balancer-api-external: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.802301ms message: 'load-balancer-api-external: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:27Z" - latency: 6.69514ms message: 'load-balancer-api-external: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:00:27Z" - latency: 4.868654ms message: 'load-balancer-api-external: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:27Z" - latency: 7.019763ms message: 'load-balancer-api-external: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:59:27Z" - latency: 5.222007ms message: 'load-balancer-api-external: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:27Z" - latency: 6.934932ms message: 'load-balancer-api-external: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:58:27Z" - latency: 5.961112ms message: 'load-balancer-api-external: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:57:27Z" - latency: 7.683324ms message: 'load-balancer-api-external: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:57:27Z" - latency: 4.876953ms message: 'load-balancer-api-external: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 7.044438ms message: 'load-balancer-api-external: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:56:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "145856" uid: 946e761c-6b58-4147-9989-038f18ebab27 spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T20:06:27Z" message: 'load-balancer-api-internal: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.796344ms message: 'load-balancer-api-internal: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:27Z" - latency: 6.575574ms message: 'load-balancer-api-internal: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T21:00:27Z" - latency: 4.82513ms message: 'load-balancer-api-internal: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:27Z" - latency: 7.047629ms message: 'load-balancer-api-internal: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:59:27Z" - latency: 5.1832ms message: 'load-balancer-api-internal: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:27Z" - latency: 6.887722ms message: 'load-balancer-api-internal: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:58:27Z" - latency: 5.567224ms message: 'load-balancer-api-internal: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:57:27Z" - latency: 7.621436ms message: 'load-balancer-api-internal: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:57:27Z" - latency: 4.891235ms message: 'load-balancer-api-internal: tcp connection to ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 6.952917ms message: 'load-balancer-api-internal: resolved host name ac75f896b02ee4a50a06ba86ff68d584-38b413f506e01858.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T20:56:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-network-check-target-ip-10-0-132-25 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "142378" uid: 04e2c66a-f893-47bb-8128-285b051d09ea spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:07:27Z" message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.096815ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 2.441881ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:55:27Z" - latency: 2.024762ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:54:27Z" - latency: 2.228712ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:53:27Z" - latency: 1.943528ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:52:27Z" - latency: 2.132445ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:51:27Z" - latency: 2.364482ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:50:27Z" - latency: 2.425282ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:49:27Z" - latency: 2.48452ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:48:27Z" - latency: 2.483924ms message: 'network-check-target-ip-10-0-132-25: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-network-check-target-ip-10-0-135-70 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "142377" uid: ca3b3cd1-7060-4784-bea2-c7c278d3f242 spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:07:27Z" message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.213145ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 2.438637ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:55:27Z" - latency: 1.885839ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:54:27Z" - latency: 1.870355ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:53:27Z" - latency: 1.928517ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:52:27Z" - latency: 1.894341ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:51:27Z" - latency: 1.758071ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:50:27Z" - latency: 2.108271ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:49:27Z" - latency: 2.041286ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:48:27Z" - latency: 1.993759ms message: 'network-check-target-ip-10-0-135-70: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-network-check-target-ip-10-0-139-53 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "142376" uid: 41d3b7e6-4d6c-42cc-81c4-aecde97360b4 spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T20:07:27Z" message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.116107ms message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 889.377µs message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:55:27Z" - latency: 982.414µs message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:54:27Z" - latency: 752.897µs message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:53:27Z" - latency: 933.892µs message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:52:27Z" - latency: 928.833µs message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:51:27Z" - latency: 1.876533ms message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:50:27Z" - latency: 1.791334ms message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:49:27Z" - latency: 1.07273ms message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:48:27Z" - latency: 1.019187ms message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:47:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T20:00:26Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-53-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-53.us-east-2.compute.internal uid: 3538623b-2376-4475-9b7d-91bc70e2e36f resourceVersion: "145854" uid: 165ec4e0-b79d-43ed-8c69-8c9fedf5f06e spec: sourcePod: network-check-source-6f78d59f99-qtbqg targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T20:06:27Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 746.478µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T21:00:27Z" - latency: 1.626964ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T21:00:27Z" - latency: 780.796µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:59:27Z" - latency: 1.814606ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:59:27Z" - latency: 906.571µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:58:27Z" - latency: 1.92821ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:58:27Z" - latency: 1.189236ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:57:27Z" - latency: 2.026521ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:57:27Z" - latency: 827.652µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T20:56:27Z" - latency: 2.099571ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T20:56:27Z" kind: List metadata: resourceVersion: ""