apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "121306" uid: 0cf2fc4c-3df4-4abc-be75-498085952272 spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T18:00:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.650108ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:55Z" - latency: 1.419272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 4.495473ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 2.069739ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 1.144092ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 1.023624ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 925.535µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:36:55Z" - latency: 1.061362ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:35:55Z" - latency: 1.392179ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:34:55Z" - latency: 12.222689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "119588" uid: 07d508eb-4ba2-4ebf-9cef-c0917595b9ae spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T17:59:55Z" message: 'load-balancer-api-external: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.025162ms message: 'load-balancer-api-external: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 7.436723ms message: 'load-balancer-api-external: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:41:55Z" - latency: 18.993354ms message: 'load-balancer-api-external: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 38.756477ms message: 'load-balancer-api-external: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:40:55Z" - latency: 16.044184ms message: 'load-balancer-api-external: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 7.226165ms message: 'load-balancer-api-external: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:39:55Z" - latency: 18.328728ms message: 'load-balancer-api-external: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 9.155791ms message: 'load-balancer-api-external: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:38:55Z" - latency: 15.016592ms message: 'load-balancer-api-external: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 8.026426ms message: 'load-balancer-api-external: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:37:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "119587" uid: ecb9bcd9-752c-4a09-b741-82986ff88968 spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T17:59:55Z" message: 'load-balancer-api-internal: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 19.070993ms message: 'load-balancer-api-internal: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 7.346522ms message: 'load-balancer-api-internal: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:41:55Z" - latency: 24.664529ms message: 'load-balancer-api-internal: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 38.412565ms message: 'load-balancer-api-internal: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:40:55Z" - latency: 16.985381ms message: 'load-balancer-api-internal: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 7.165215ms message: 'load-balancer-api-internal: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:39:55Z" - latency: 17.980211ms message: 'load-balancer-api-internal: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 9.135723ms message: 'load-balancer-api-internal: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:38:55Z" - latency: 14.627366ms message: 'load-balancer-api-internal: tcp connection to abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 8.080891ms message: 'load-balancer-api-internal: resolved host name abc2cf8bc225b427fb144199fe91b720-31e182ef057dd652.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T18:37:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-network-check-target-ip-10-0-128-236 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "121302" uid: f12e20bb-6882-4fda-a17f-8179005f00f6 spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:00:55Z" message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.44µs message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:55Z" - latency: 979.827µs message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 10.157434ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 1.767333ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 1.305015ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 1.078175ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 941.094µs message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:36:55Z" - latency: 2.050015ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:35:55Z" - latency: 1.225002ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:34:55Z" - latency: 10.869814ms message: 'network-check-target-ip-10-0-128-236: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-network-check-target-ip-10-0-130-250 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "121303" uid: cbeaf72d-ef93-41fb-9cec-3ed133f97f93 spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:00:55Z" message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.842516ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:55Z" - latency: 2.168145ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 8.305957ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 2.734854ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 4.021396ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 1.942712ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 2.154907ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:36:55Z" - latency: 2.585694ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:35:55Z" - latency: 2.498703ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:34:55Z" - latency: 16.459954ms message: 'network-check-target-ip-10-0-130-250: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-network-check-target-ip-10-0-130-84 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "121304" uid: 47cb8706-a726-47bb-a850-da9617159d82 spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T18:00:55Z" message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.562452ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:42:55Z" - latency: 2.620134ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 11.765012ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 2.798381ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 2.996833ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 2.748513ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 2.174363ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:36:55Z" - latency: 2.440447ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:35:55Z" - latency: 3.95245ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:34:55Z" - latency: 12.129705ms message: 'network-check-target-ip-10-0-130-84: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:33:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T17:53:55Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-236-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-236.ec2.internal uid: c74f8ba9-1741-4d7e-a8fa-9937a853aca0 resourceVersion: "119585" uid: 6ae5493d-7d5e-4c10-96ab-67d35b383b8b spec: sourcePod: network-check-source-6f78d59f99-w725f targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T17:59:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.456519ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:41:55Z" - latency: 2.100273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:41:55Z" - latency: 2.169757ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:40:55Z" - latency: 14.422073ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:40:55Z" - latency: 985.621µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:39:55Z" - latency: 2.095026ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:39:55Z" - latency: 2.708377ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:38:55Z" - latency: 3.559665ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:38:55Z" - latency: 1.105021ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T18:37:55Z" - latency: 2.418987ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T18:37:55Z" kind: List metadata: resourceVersion: ""