apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "36000" uid: efc795b0-66e8-401c-830a-7815dbf82e11 spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-06T17:20:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191132ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 727.577µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 907.483µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 899.451µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:38:44Z" - latency: 803.95µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:37:44Z" - latency: 1.195952ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:36:44Z" - latency: 1.024091ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:35:44Z" - latency: 985.372µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:34:44Z" - latency: 1.354534ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:33:44Z" - latency: 1.115272ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:32:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "37628" uid: 0d33bb06-1aa5-4659-9767-f4a31ec91853 spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-06T17:19:44Z" message: 'load-balancer-api-external: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.567789ms message: 'load-balancer-api-external: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:43:44Z" - latency: 8.850354ms message: 'load-balancer-api-external: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:43:44Z" - latency: 4.54658ms message: 'load-balancer-api-external: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:42:44Z" - latency: 10.044636ms message: 'load-balancer-api-external: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:42:44Z" - latency: 4.758125ms message: 'load-balancer-api-external: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 8.697822ms message: 'load-balancer-api-external: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:41:44Z" - latency: 4.344232ms message: 'load-balancer-api-external: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 7.353981ms message: 'load-balancer-api-external: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:40:44Z" - latency: 4.830896ms message: 'load-balancer-api-external: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 8.105529ms message: 'load-balancer-api-external: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:39:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "37627" uid: 62ac94e6-b358-4326-9f96-a1eb7641539e spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-06T17:19:44Z" message: 'load-balancer-api-internal: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.564847ms message: 'load-balancer-api-internal: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:43:44Z" - latency: 8.733253ms message: 'load-balancer-api-internal: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:43:44Z" - latency: 4.556135ms message: 'load-balancer-api-internal: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:42:44Z" - latency: 10.118284ms message: 'load-balancer-api-internal: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:42:44Z" - latency: 4.341835ms message: 'load-balancer-api-internal: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 8.605283ms message: 'load-balancer-api-internal: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:41:44Z" - latency: 5.244359ms message: 'load-balancer-api-internal: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 7.452775ms message: 'load-balancer-api-internal: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:40:44Z" - latency: 4.81663ms message: 'load-balancer-api-internal: tcp connection to a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 8.144888ms message: 'load-balancer-api-internal: resolved host name a96b3f0f9779b4151b148c4389b70b92-f7901a42bd2303c3.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-06T17:39:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-network-check-target-ip-10-0-130-186 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "35998" uid: 529f651d-c096-4586-bb1b-de2d1ef9427e spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-06T17:20:44Z" message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.41654ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 2.073682ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 2.054824ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 2.178338ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:38:44Z" - latency: 2.438322ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:37:44Z" - latency: 2.822441ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:36:44Z" - latency: 2.34589ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:35:44Z" - latency: 2.405382ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:34:44Z" - latency: 3.152704ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:33:44Z" - latency: 2.433761ms message: 'network-check-target-ip-10-0-130-186: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:32:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-network-check-target-ip-10-0-131-115 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "35997" uid: e29d802f-e850-49a4-bf23-0c215bdfee9c spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-06T17:20:44Z" message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133984ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 1.719325ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 1.920781ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 2.219295ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:38:44Z" - latency: 2.301198ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:37:44Z" - latency: 2.444178ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:36:44Z" - latency: 2.332716ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:35:44Z" - latency: 2.019629ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:34:44Z" - latency: 2.062399ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:33:44Z" - latency: 2.258651ms message: 'network-check-target-ip-10-0-131-115: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:32:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-network-check-target-ip-10-0-135-110 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "35999" uid: 9c4a25a2-f978-42e2-bed5-1d3ddab2b4b8 spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-06T17:20:44Z" message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 886.119µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 878.721µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 785.825µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 910.158µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:38:44Z" - latency: 905.028µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:37:44Z" - latency: 813.521µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:36:44Z" - latency: 925.309µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:35:44Z" - latency: 908.922µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:34:44Z" - latency: 810.942µs message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:33:44Z" - latency: 1.180285ms message: 'network-check-target-ip-10-0-135-110: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:32:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-06T17:13:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-135-110-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-135-110.ec2.internal uid: b5240c7d-ee18-4653-9de2-c94a4c789d37 resourceVersion: "37626" uid: 0a3baa69-29af-4b8a-bcea-bd4cfa4a5a9c spec: sourcePod: network-check-source-6859b67c86-lz2h5 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-06T17:19:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.08969ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:43:44Z" - latency: 1.926863ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-06T17:43:44Z" - latency: 956.707µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:42:44Z" - latency: 1.987727ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-06T17:42:44Z" - latency: 1.225448ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:41:44Z" - latency: 1.978577ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-06T17:41:44Z" - latency: 759.789µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:40:44Z" - latency: 1.456471ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-06T17:40:44Z" - latency: 910.764µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-06T17:39:44Z" - latency: 1.513284ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-06T17:39:44Z" kind: List metadata: resourceVersion: ""