apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63029" uid: 84363fac-fa3a-4ea3-a583-48a8550c7e03 spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-23T13:51:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 891.785µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 1.107784ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 1.370184ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 1.506447ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 1.005959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 842.336µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:21:51Z" - latency: 2.425819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:20:51Z" - latency: 1.188277ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:19:51Z" - latency: 1.160987ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:18:51Z" - latency: 957.326µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:17:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63031" uid: f292110f-fcf9-4917-bbf5-9f282f610b11 spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T13:50:51Z" message: 'load-balancer-api-external: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.935514ms message: 'load-balancer-api-external: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 9.217209ms message: 'load-balancer-api-external: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:26:51Z" - latency: 4.708664ms message: 'load-balancer-api-external: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 6.588315ms message: 'load-balancer-api-external: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:25:51Z" - latency: 4.751517ms message: 'load-balancer-api-external: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 7.895398ms message: 'load-balancer-api-external: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:24:51Z" - latency: 4.237879ms message: 'load-balancer-api-external: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 6.574499ms message: 'load-balancer-api-external: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:23:51Z" - latency: 4.031429ms message: 'load-balancer-api-external: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 7.007292ms message: 'load-balancer-api-external: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:22:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63030" uid: 66795974-cfae-4d7c-82b4-396173bf3698 spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-23T13:50:51Z" message: 'load-balancer-api-internal: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.988497ms message: 'load-balancer-api-internal: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 9.129953ms message: 'load-balancer-api-internal: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:26:51Z" - latency: 3.942716ms message: 'load-balancer-api-internal: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 6.683957ms message: 'load-balancer-api-internal: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:25:51Z" - latency: 4.74672ms message: 'load-balancer-api-internal: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 7.965317ms message: 'load-balancer-api-internal: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:24:51Z" - latency: 4.251311ms message: 'load-balancer-api-internal: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 6.603563ms message: 'load-balancer-api-internal: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:23:51Z" - latency: 4.047897ms message: 'load-balancer-api-internal: tcp connection to a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 7.094255ms message: 'load-balancer-api-internal: resolved host name a206f06f4797e4ff5bd2404e07328a0f-b67bba776d2b12ef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-23T14:22:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-128-225 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63027" uid: ad43729d-ceb0-490d-ba77-28ad627ce347 spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-23T13:51:51Z" message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.057018ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 2.2467ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 2.301087ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 2.164705ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 2.221219ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 2.063197ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:21:51Z" - latency: 2.612809ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:20:51Z" - latency: 2.23546ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:19:51Z" - latency: 2.182075ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:18:51Z" - latency: 2.030204ms message: 'network-check-target-ip-10-0-128-225: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:17:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-138-125 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63026" uid: efdfaa71-650a-4e21-bd33-838b81474eb2 spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-23T13:51:51Z" message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.180377ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 2.42319ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 2.170633ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 2.242227ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 2.274161ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 2.333133ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:21:51Z" - latency: 3.370026ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:20:51Z" - latency: 2.412085ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:19:51Z" - latency: 2.328524ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:18:51Z" - latency: 2.320204ms message: 'network-check-target-ip-10-0-138-125: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:17:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:50Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-ip-10-0-140-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63025" uid: 12b49016-8007-4c33-aaec-db9ca8be9aad spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-23T13:51:51Z" message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 857.116µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 888.334µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 980.555µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 988.056µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 1.026459ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 983.843µs message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:21:51Z" - latency: 5.29637ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:20:51Z" - latency: 1.001381ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:19:51Z" - latency: 1.032581ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:18:51Z" - latency: 1.446872ms message: 'network-check-target-ip-10-0-140-103: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:17:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-23T13:44:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-103-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-103.ec2.internal uid: ac758738-1c37-487e-ae67-90738f9f5b52 resourceVersion: "63028" uid: bdf28e47-c281-4e23-8bce-22ce08f662ef spec: sourcePod: network-check-source-7bc5b6bf85-zf6lz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-23T13:50:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 817.735µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:26:51Z" - latency: 1.876814ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T14:26:51Z" - latency: 859.103µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:25:51Z" - latency: 1.634917ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T14:25:51Z" - latency: 839.198µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:24:51Z" - latency: 1.935101ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T14:24:51Z" - latency: 1.16484ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:23:51Z" - latency: 1.952434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T14:23:51Z" - latency: 925.602µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-23T14:22:51Z" - latency: 1.839308ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-23T14:22:51Z" kind: List metadata: resourceVersion: ""