apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "69656" uid: bacd3142-60a7-4357-bd59-be40d074117c spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-09-15T20:18:21Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.862518ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 1.235441ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 967.03µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 1.496762ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 926.564µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:42:21Z" - latency: 1.062689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:41:21Z" - latency: 1.259792ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:40:21Z" - latency: 974.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:39:21Z" - latency: 1.270823ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:38:21Z" - latency: 1.604081ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "70429" uid: fc2debc4-9c09-4577-a1bb-d962b6b07806 spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T20:17:21Z" message: 'load-balancer-api-external: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.877402ms message: 'load-balancer-api-external: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:47:21Z" - latency: 6.868016ms message: 'load-balancer-api-external: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:47:21Z" - latency: 5.337546ms message: 'load-balancer-api-external: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 6.541705ms message: 'load-balancer-api-external: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:46:21Z" - latency: 4.142227ms message: 'load-balancer-api-external: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 6.442226ms message: 'load-balancer-api-external: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:45:21Z" - latency: 5.091566ms message: 'load-balancer-api-external: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 8.451859ms message: 'load-balancer-api-external: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:44:21Z" - latency: 3.669897ms message: 'load-balancer-api-external: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 7.622028ms message: 'load-balancer-api-external: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "70428" uid: 1e19187a-3c81-48e3-8c94-54bbf0c09b48 spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-09-15T20:17:21Z" message: 'load-balancer-api-internal: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.64865ms message: 'load-balancer-api-internal: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:47:21Z" - latency: 6.894006ms message: 'load-balancer-api-internal: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:47:21Z" - latency: 5.341792ms message: 'load-balancer-api-internal: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 6.470667ms message: 'load-balancer-api-internal: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:46:21Z" - latency: 4.215166ms message: 'load-balancer-api-internal: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 6.356847ms message: 'load-balancer-api-internal: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:45:21Z" - latency: 5.075947ms message: 'load-balancer-api-internal: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 8.372541ms message: 'load-balancer-api-internal: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:44:21Z" - latency: 3.662598ms message: 'load-balancer-api-internal: tcp connection to a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 7.645861ms message: 'load-balancer-api-internal: resolved host name a8125fb5c3c194b9ab33c5dea0fbf2d0-9367eb7d13b10a22.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-09-15T20:43:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-network-check-target-ip-10-0-134-155 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "69653" uid: 5bf40014-6a03-4d4f-90c0-0446e0a09fb5 spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T20:18:21Z" message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.022514ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 1.949295ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 1.888454ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 1.95439ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 1.765731ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:42:21Z" - latency: 1.850413ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:41:21Z" - latency: 1.881947ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:40:21Z" - latency: 1.737087ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:39:21Z" - latency: 1.906249ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:38:21Z" - latency: 2.157206ms message: 'network-check-target-ip-10-0-134-155: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-network-check-target-ip-10-0-137-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "69654" uid: 05f083dc-e008-42f3-a047-28ee7c02039c spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-09-15T20:18:21Z" message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.351165ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 2.113397ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 2.017981ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 2.081057ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 2.389049ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:42:21Z" - latency: 2.466901ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:41:21Z" - latency: 2.482781ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:40:21Z" - latency: 2.289836ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:39:21Z" - latency: 2.210436ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:38:21Z" - latency: 2.190981ms message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-network-check-target-ip-10-0-140-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "69652" uid: aa3bf663-6fce-4987-9ee5-044243a83c51 spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-09-15T20:18:21Z" message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.030487ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 882.404µs message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 1.05003ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 1.895481ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 1.252196ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:42:21Z" - latency: 1.196091ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:41:21Z" - latency: 985.204µs message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:40:21Z" - latency: 1.48074ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:39:21Z" - latency: 1.00927ms message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:38:21Z" - latency: 964.499µs message: 'network-check-target-ip-10-0-140-72: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:37:21Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-09-15T20:11:20Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-72-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-72.ec2.internal uid: 9af691fc-db4e-4b67-826f-31dba7bc0287 resourceVersion: "70425" uid: c1a9312a-6f29-4686-9add-a25fae20bd5c spec: sourcePod: network-check-source-6f8b768455-x5v6t targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-09-15T20:17:21Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 872.817µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:47:21Z" - latency: 1.926538ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T20:47:21Z" - latency: 1.119717ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:46:21Z" - latency: 2.107531ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T20:46:21Z" - latency: 1.056089ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:45:21Z" - latency: 2.031682ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T20:45:21Z" - latency: 972.475µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:44:21Z" - latency: 2.283227ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T20:44:21Z" - latency: 1.09103ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-09-15T20:43:21Z" - latency: 2.130195ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-09-15T20:43:21Z" kind: List metadata: resourceVersion: ""