apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "110620" uid: 56fbbfbd-1d58-4b29-8b17-3ab8909b9b90 spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-11-03T17:43:47Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.173462ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:46:47Z" - latency: 1.805875ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:45:47Z" - latency: 2.028743ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:44:47Z" - latency: 1.273362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:43:47Z" - latency: 1.331158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 4.803535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 6.167953ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 1.067947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 1.441102ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 1.029774ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "107913" uid: 8ffaeec1-bad1-4fb9-a40c-408b0fd2d791 spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T17:42:47Z" message: 'load-balancer-api-external: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 59.78817ms message: 'load-balancer-api-external: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 7.583967ms message: 'load-balancer-api-external: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:42:47Z" - latency: 55.065948ms message: 'load-balancer-api-external: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 11.401779ms message: 'load-balancer-api-external: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:41:47Z" - latency: 55.919572ms message: 'load-balancer-api-external: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 11.835802ms message: 'load-balancer-api-external: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:40:47Z" - latency: 55.473477ms message: 'load-balancer-api-external: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 7.103105ms message: 'load-balancer-api-external: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:39:47Z" - latency: 55.406718ms message: 'load-balancer-api-external: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 6.858082ms message: 'load-balancer-api-external: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:38:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "107912" uid: 9158c550-4e7a-471b-a990-bcb764d7ced8 spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-11-03T17:42:47Z" message: 'load-balancer-api-internal: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.051656ms message: 'load-balancer-api-internal: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 7.620677ms message: 'load-balancer-api-internal: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:42:47Z" - latency: 55.348115ms message: 'load-balancer-api-internal: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 11.20115ms message: 'load-balancer-api-internal: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:41:47Z" - latency: 56.103566ms message: 'load-balancer-api-internal: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 11.652413ms message: 'load-balancer-api-internal: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:40:47Z" - latency: 55.421316ms message: 'load-balancer-api-internal: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 7.218385ms message: 'load-balancer-api-internal: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:39:47Z" - latency: 55.645304ms message: 'load-balancer-api-internal: tcp connection to aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 7.135684ms message: 'load-balancer-api-internal: resolved host name aa49546cbf5c9454088617b8e9f7adf8-66509c371b41a33e.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-11-03T18:38:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-network-check-target-ip-10-0-131-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "110618" uid: cae232f6-8e33-46d1-bdd0-8384523a1cd2 spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-11-03T17:43:47Z" message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.905347ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:46:47Z" - latency: 1.935236ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:45:47Z" - latency: 2.158793ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:44:47Z" - latency: 2.091259ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:43:47Z" - latency: 1.937775ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 3.211389ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 6.471414ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 1.962801ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 1.814137ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 1.883175ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-network-check-target-ip-10-0-139-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "110619" uid: 008d16bd-372d-4294-9183-db60be3a3aa5 spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-11-03T17:43:47Z" message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.423079ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:46:47Z" - latency: 2.562778ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:45:47Z" - latency: 2.779697ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:44:47Z" - latency: 2.553152ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:43:47Z" - latency: 2.579179ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 4.779626ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 5.090096ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 2.455153ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 2.068622ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 2.31884ms message: 'network-check-target-ip-10-0-139-156: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-network-check-target-ip-10-0-139-234 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "110617" uid: cd34e92a-4e67-42de-9706-06de0b7e931d spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-11-03T17:43:47Z" message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.07973ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:46:47Z" - latency: 1.127317ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:45:47Z" - latency: 2.927868ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:44:47Z" - latency: 965.742µs message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:43:47Z" - latency: 1.728567ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 5.397231ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 5.592163ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 914.405µs message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 2.401121ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 1.154744ms message: 'network-check-target-ip-10-0-139-234: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:37:47Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-11-03T17:36:46Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-234-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-234.us-west-1.compute.internal uid: 16b41938-02e8-4a8a-a5d3-c6b1782c83c1 resourceVersion: "107910" uid: f8e5fb0a-e5d4-49d5-bd8c-f5d3bba315c3 spec: sourcePod: network-check-source-6f78d59f99-sqcln targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-11-03T17:42:47Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 991.251µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:42:47Z" - latency: 1.923874ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:42:47Z" - latency: 948.153µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:41:47Z" - latency: 5.885739ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:41:47Z" - latency: 1.385273ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:40:47Z" - latency: 5.594699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:40:47Z" - latency: 1.192331ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:39:47Z" - latency: 2.834265ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:39:47Z" - latency: 899.679µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-11-03T18:38:47Z" - latency: 2.380015ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-11-03T18:38:47Z" kind: List metadata: resourceVersion: ""