apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "38126" uid: 6ee0d56a-550f-4967-ab50-b71208411c04 spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-27T21:17:40Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 807.325µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 963.4µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 1.079883ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 1.064363ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:35:40Z" - latency: 1.089343ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:34:40Z" - latency: 1.28778ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:33:40Z" - latency: 1.000301ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:32:40Z" - latency: 1.088573ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:31:40Z" - latency: 1.064267ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:30:40Z" - latency: 1.020819ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:29:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "40235" uid: 160af9b8-dc1b-4e9f-9e79-6101a2a4404d spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T21:16:40Z" message: 'load-balancer-api-external: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.802975ms message: 'load-balancer-api-external: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:40:40Z" - latency: 7.737571ms message: 'load-balancer-api-external: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:40:40Z" - latency: 4.511058ms message: 'load-balancer-api-external: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:39:40Z" - latency: 8.017608ms message: 'load-balancer-api-external: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:39:40Z" - latency: 3.704403ms message: 'load-balancer-api-external: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 7.663243ms message: 'load-balancer-api-external: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:38:40Z" - latency: 4.953137ms message: 'load-balancer-api-external: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 8.275852ms message: 'load-balancer-api-external: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:37:40Z" - latency: 5.483815ms message: 'load-balancer-api-external: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 7.14605ms message: 'load-balancer-api-external: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:36:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "40236" uid: 6e301815-ec99-410e-b24e-b4480f380979 spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-27T21:16:40Z" message: 'load-balancer-api-internal: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.777555ms message: 'load-balancer-api-internal: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:40:40Z" - latency: 7.684741ms message: 'load-balancer-api-internal: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:40:40Z" - latency: 3.340475ms message: 'load-balancer-api-internal: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:39:40Z" - latency: 8.096508ms message: 'load-balancer-api-internal: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:39:40Z" - latency: 4.39243ms message: 'load-balancer-api-internal: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 7.637083ms message: 'load-balancer-api-internal: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:38:40Z" - latency: 4.934406ms message: 'load-balancer-api-internal: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 8.353172ms message: 'load-balancer-api-internal: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:37:40Z" - latency: 3.206796ms message: 'load-balancer-api-internal: tcp connection to ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 7.115904ms message: 'load-balancer-api-internal: resolved host name ab75db8b66982432b9b5f92faf3180cd-36c1109f37919ea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-27T21:36:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-network-check-target-ip-10-0-128-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "38123" uid: 70de5493-547e-4152-96fa-d0055eaa2665 spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:17:40Z" message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.225306ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 2.112336ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 2.301518ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 2.117539ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:35:40Z" - latency: 2.492639ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:34:40Z" - latency: 2.270966ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:33:40Z" - latency: 2.215583ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:32:40Z" - latency: 2.202842ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:31:40Z" - latency: 2.41795ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:30:40Z" - latency: 2.214771ms message: 'network-check-target-ip-10-0-128-93: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:29:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-network-check-target-ip-10-0-130-116 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "38124" uid: 2a4b437a-3cd4-4521-bef2-75a33a1dae05 spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:17:40Z" message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.078ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 1.072736ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 828.459µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 838.168µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:35:40Z" - latency: 896.886µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:34:40Z" - latency: 791.842µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:33:40Z" - latency: 812.395µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:32:40Z" - latency: 871.72µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:31:40Z" - latency: 840.771µs message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:30:40Z" - latency: 1.344981ms message: 'network-check-target-ip-10-0-130-116: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:29:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-network-check-target-ip-10-0-136-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "38125" uid: a5fe8e9b-8f78-41b7-b004-4cb10f48d8c8 spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-27T21:17:40Z" message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.480846ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 2.062353ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 2.298501ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 2.338607ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:35:40Z" - latency: 2.21428ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:34:40Z" - latency: 2.176421ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:33:40Z" - latency: 1.83282ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:32:40Z" - latency: 2.177562ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:31:40Z" - latency: 2.234278ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:30:40Z" - latency: 2.364106ms message: 'network-check-target-ip-10-0-136-186: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:29:40Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-27T21:10:39Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-130-116-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-130-116.ec2.internal uid: 0b423e78-0e94-48b8-b234-e0602a0eadc2 resourceVersion: "40234" uid: 4c6ebe5b-1851-4c10-8510-e57488e2dfaf spec: sourcePod: network-check-source-7f44b6dd87-z7ztr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-27T21:16:40Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.146948ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:40:40Z" - latency: 1.633913ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:40:40Z" - latency: 895.193µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:39:40Z" - latency: 1.713413ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:39:40Z" - latency: 722.297µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:38:40Z" - latency: 2.027708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:38:40Z" - latency: 1.048499ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:37:40Z" - latency: 1.747216ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:37:40Z" - latency: 895.981µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-27T21:36:40Z" - latency: 1.582952ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-27T21:36:40Z" kind: List metadata: resourceVersion: ""