apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "102320" uid: e99ecb38-68c7-43d1-8ffc-f8760d0055c4 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-02T15:05:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 867.551µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 1.247689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 1.046262ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:59:10Z" - latency: 1.728687ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:58:10Z" - latency: 1.360327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:57:10Z" - latency: 1.454001ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:56:10Z" - latency: 4.637209ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:55:10Z" - latency: 1.892759ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:54:10Z" - latency: 1.352957ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:53:10Z" - latency: 1.253862ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:52:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "105460" uid: b095656f-e161-4414-bfdf-81a92ef505d5 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T15:04:11Z" message: 'load-balancer-api-external: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.807143ms message: 'load-balancer-api-external: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:04:11Z" - latency: 54.709865ms message: 'load-balancer-api-external: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:04:10Z" - latency: 3.386636926s message: 'load-balancer-api-external: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:03:10Z" - latency: 6.976389ms message: 'load-balancer-api-external: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:03:10Z" - latency: 53.573271ms message: 'load-balancer-api-external: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:02:10Z" - latency: 5.876259ms message: 'load-balancer-api-external: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:02:10Z" - latency: 53.775377ms message: 'load-balancer-api-external: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 7.261762ms message: 'load-balancer-api-external: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:01:10Z" - latency: 54.764439ms message: 'load-balancer-api-external: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 6.568654ms message: 'load-balancer-api-external: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:00:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "105459" uid: 57e01da1-31c9-40ac-858c-9de48c36dc26 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-02T15:04:11Z" message: 'load-balancer-api-internal: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 56.377154ms message: 'load-balancer-api-internal: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:04:11Z" - latency: 54.191879ms message: 'load-balancer-api-internal: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:04:10Z" - latency: 3.386625671s message: 'load-balancer-api-internal: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:03:10Z" - latency: 6.88511ms message: 'load-balancer-api-internal: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:03:10Z" - latency: 53.610818ms message: 'load-balancer-api-internal: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:02:10Z" - latency: 5.851634ms message: 'load-balancer-api-internal: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:02:10Z" - latency: 53.829271ms message: 'load-balancer-api-internal: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 7.225631ms message: 'load-balancer-api-internal: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:01:10Z" - latency: 54.698093ms message: 'load-balancer-api-internal: tcp connection to a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 6.593016ms message: 'load-balancer-api-internal: resolved host name a65af20ceb8e0453d8b17c9c993c7f5c-df77204d0ad5c075.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-02T16:00:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-132-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "102317" uid: a0fe4c41-01bf-4779-8fd8-246e74a93fb0 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T15:05:10Z" message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.042135ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 1.05949ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 969.145µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:59:10Z" - latency: 960.412µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:58:10Z" - latency: 1.448442ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:57:10Z" - latency: 1.549224ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:56:10Z" - latency: 10.244009ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:55:10Z" - latency: 1.029246ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:54:10Z" - latency: 1.314605ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:53:10Z" - latency: 1.044011ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:52:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-135-103 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "102318" uid: 89ceeddf-f619-48e6-b356-977bce362e56 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-02T15:05:10Z" message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.110682ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 2.773434ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 2.872166ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:59:10Z" - latency: 2.757002ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:58:10Z" - latency: 2.415762ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:57:10Z" - latency: 2.496683ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:56:10Z" - latency: 6.814923ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:55:10Z" - latency: 2.500333ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:54:10Z" - latency: 2.616869ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:53:10Z" - latency: 2.012138ms message: 'network-check-target-ip-10-0-135-103: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:52:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-139-197 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "102319" uid: 2e44e77a-5ceb-4bf6-9d57-7d3ce6f7e1d7 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-02T15:05:10Z" message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.644539ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 2.510715ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 2.614417ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:59:10Z" - latency: 2.326486ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:58:10Z" - latency: 2.978187ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:57:10Z" - latency: 2.56942ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:56:10Z" - latency: 6.086514ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:55:10Z" - latency: 2.547326ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:54:10Z" - latency: 2.717524ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:53:10Z" - latency: 2.667504ms message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-02T15:52:10Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-02T14:58:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.us-west-1.compute.internal uid: 923460f4-c10b-4d62-9c26-51a04c3008ef resourceVersion: "105458" uid: f13d9c4e-d0c5-450b-b982-91b36da69690 spec: sourcePod: network-check-source-6f78d59f99-cnq6q targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-02T15:04:10Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 13.454727ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:04:10Z" - latency: 22.746265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T16:04:10Z" - latency: 922.597µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:03:10Z" - latency: 1.793458ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T16:03:10Z" - latency: 910.363µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:02:10Z" - latency: 1.727144ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T16:02:10Z" - latency: 1.030954ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:01:10Z" - latency: 2.107162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T16:01:10Z" - latency: 1.098849ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-02T16:00:10Z" - latency: 1.824137ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-02T16:00:10Z" kind: List metadata: resourceVersion: ""