apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "111554" uid: fabe3ec4-12ed-4c2f-b5cb-71e39c76228e spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:56:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.200178ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 1.054032ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 4.365791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 919.692µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:07Z" - latency: 1.546894ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:07Z" - latency: 1.146475ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:07Z" - latency: 1.342241ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:07Z" - latency: 1.306755ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:07Z" - latency: 996.526µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:07Z" - latency: 1.199848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "113100" uid: 7ed8a318-3121-4a2a-bf3c-65a5b9c1ac9a spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:55:07Z" message: 'load-balancer-api-external: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.924679ms message: 'load-balancer-api-external: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:01:07Z" - latency: 6.393724ms message: 'load-balancer-api-external: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:01:07Z" - latency: 56.06365ms message: 'load-balancer-api-external: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:00:07Z" - latency: 6.623554ms message: 'load-balancer-api-external: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:00:07Z" - latency: 55.042784ms message: 'load-balancer-api-external: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 6.74193ms message: 'load-balancer-api-external: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:59:07Z" - latency: 53.349756ms message: 'load-balancer-api-external: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 7.567957ms message: 'load-balancer-api-external: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:58:07Z" - latency: 72.102043ms message: 'load-balancer-api-external: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 18.049543ms message: 'load-balancer-api-external: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:57:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "113099" uid: 95ee6d14-ff8d-4d0a-ae7e-ba730d5819be spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:55:07Z" message: 'load-balancer-api-internal: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 54.567272ms message: 'load-balancer-api-internal: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:01:07Z" - latency: 6.414228ms message: 'load-balancer-api-internal: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:01:07Z" - latency: 56.594379ms message: 'load-balancer-api-internal: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:00:07Z" - latency: 6.537343ms message: 'load-balancer-api-internal: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T23:00:07Z" - latency: 55.033604ms message: 'load-balancer-api-internal: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 6.812954ms message: 'load-balancer-api-internal: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:59:07Z" - latency: 66.77347ms message: 'load-balancer-api-internal: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 7.597256ms message: 'load-balancer-api-internal: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:58:07Z" - latency: 54.071877ms message: 'load-balancer-api-internal: tcp connection to a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 17.673517ms message: 'load-balancer-api-internal: resolved host name a9858833090b34fb5b824294711bfe6c-e75a63cf43fa0c23.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T22:57:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-network-check-target-ip-10-0-130-176 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "111550" uid: 1de5a5c3-31bf-47e4-87ce-10870ead6319 spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:56:07Z" message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.301662ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 2.406275ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 5.67007ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 1.91091ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:07Z" - latency: 2.06707ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:07Z" - latency: 2.166368ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:07Z" - latency: 2.382676ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:07Z" - latency: 2.183622ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:07Z" - latency: 2.357589ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:07Z" - latency: 2.22464ms message: 'network-check-target-ip-10-0-130-176: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-network-check-target-ip-10-0-131-193 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "111552" uid: 617365f1-d280-4636-a2b7-fc5378b4141f spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:56:07Z" message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.256416ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 2.075827ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 5.773906ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 2.270743ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:07Z" - latency: 2.048704ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:07Z" - latency: 1.890768ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:07Z" - latency: 2.320337ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:07Z" - latency: 2.065043ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:07Z" - latency: 2.567452ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:07Z" - latency: 2.149504ms message: 'network-check-target-ip-10-0-131-193: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-network-check-target-ip-10-0-142-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "111549" uid: 28dc7921-809b-43d9-a167-d71757d61033 spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:56:07Z" message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.361107ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 1.164287ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 4.77438ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 942.478µs message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:56:07Z" - latency: 1.008477ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:55:07Z" - latency: 1.220968ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:54:07Z" - latency: 1.070429ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:53:07Z" - latency: 1.585109ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:52:07Z" - latency: 1.016623ms message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:51:07Z" - latency: 854.538µs message: 'network-check-target-ip-10-0-142-154: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:50:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:49:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-142-154-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-142-154.us-west-1.compute.internal uid: c348f11d-5cc1-4761-8f5d-f7f3382f692c resourceVersion: "113096" uid: 05cd81b8-1c93-4895-bff9-94b095a5604d spec: sourcePod: network-check-source-6f78d59f99-ghx6v targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:55:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.006601ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:01:07Z" - latency: 2.027237ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:01:07Z" - latency: 1.06322ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T23:00:07Z" - latency: 2.075123ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T23:00:07Z" - latency: 881.585µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:59:07Z" - latency: 2.212498ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:59:07Z" - latency: 797.671µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:58:07Z" - latency: 2.497288ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:58:07Z" - latency: 1.429047ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T22:57:07Z" - latency: 10.166495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T22:57:07Z" kind: List metadata: resourceVersion: ""