apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32023" uid: e02302f8-f625-425c-9cef-9f4a2ee27d5f spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-24T22:41:38Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 920.102µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 918.783µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 1.10264ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 838.824µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 856.923µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 974.003µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:11:38Z" - latency: 1.197104ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:10:38Z" - latency: 944.241µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:09:38Z" - latency: 1.022439ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:08:38Z" - latency: 1.111947ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:07:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32024" uid: ebb06cf4-6271-43c1-af6b-ddde6940cb48 spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T22:40:38Z" message: 'load-balancer-api-external: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.497177ms message: 'load-balancer-api-external: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 6.924117ms message: 'load-balancer-api-external: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:16:38Z" - latency: 4.852544ms message: 'load-balancer-api-external: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 5.902694ms message: 'load-balancer-api-external: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:15:38Z" - latency: 5.000764ms message: 'load-balancer-api-external: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 6.302407ms message: 'load-balancer-api-external: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:14:38Z" - latency: 4.203294ms message: 'load-balancer-api-external: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 5.897782ms message: 'load-balancer-api-external: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:13:38Z" - latency: 5.628719ms message: 'load-balancer-api-external: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 6.585092ms message: 'load-balancer-api-external: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:12:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32025" uid: fe53b935-0d84-43be-92bb-b76ebcbed294 spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-24T22:40:38Z" message: 'load-balancer-api-internal: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.365831ms message: 'load-balancer-api-internal: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 6.907607ms message: 'load-balancer-api-internal: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:16:38Z" - latency: 4.878371ms message: 'load-balancer-api-internal: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 5.951751ms message: 'load-balancer-api-internal: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:15:38Z" - latency: 5.009751ms message: 'load-balancer-api-internal: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 6.284653ms message: 'load-balancer-api-internal: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:14:38Z" - latency: 4.212472ms message: 'load-balancer-api-internal: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 5.972311ms message: 'load-balancer-api-internal: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:13:38Z" - latency: 5.323811ms message: 'load-balancer-api-internal: tcp connection to a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 6.502684ms message: 'load-balancer-api-internal: resolved host name a50e4a1ef286442ccb6594dd5e8c1886-e3f0ef91db26bea9.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-24T23:12:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-132-138 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32019" uid: 39935321-b0bc-43af-a34c-abb73a70cb11 spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:41:38Z" message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 876.136µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 1.381035ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 800.325µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 736.294µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 1.164895ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 875.285µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:11:38Z" - latency: 896.515µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:10:38Z" - latency: 1.267051ms message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:09:38Z" - latency: 768.225µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:08:38Z" - latency: 811.811µs message: 'network-check-target-ip-10-0-132-138: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:07:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-133-161 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32020" uid: a60848b3-a6a1-4263-a8b6-2b084542cbf2 spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:41:38Z" message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.706901ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 1.847085ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 1.841475ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 1.815061ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 1.745778ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 1.7559ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:11:38Z" - latency: 1.523457ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:10:38Z" - latency: 1.931853ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:09:38Z" - latency: 1.906876ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:08:38Z" - latency: 1.971217ms message: 'network-check-target-ip-10-0-133-161: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:07:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-ip-10-0-142-202 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32021" uid: c0d1745a-b596-4652-a3bf-ac7509cc729e spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-24T22:41:38Z" message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.051849ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 2.192337ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 2.16168ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 2.182038ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 2.272314ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 2.081393ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:11:38Z" - latency: 2.161281ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:10:38Z" - latency: 2.168515ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:09:38Z" - latency: 2.016259ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:08:38Z" - latency: 1.921485ms message: 'network-check-target-ip-10-0-142-202: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:07:38Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-24T22:34:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-138-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-138.ec2.internal uid: aca564cd-1257-4314-9cb4-f30f6bdb2fd0 resourceVersion: "32022" uid: 822450e8-ede7-4015-84da-d99b692ace0f spec: sourcePod: network-check-source-8894fc9bd-fc9xv targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-24T22:40:38Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.152191ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:16:38Z" - latency: 2.019661ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T23:16:38Z" - latency: 1.108294ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:15:38Z" - latency: 1.445862ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T23:15:38Z" - latency: 1.041888ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:14:38Z" - latency: 1.655273ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T23:14:38Z" - latency: 815.836µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:13:38Z" - latency: 1.717246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T23:13:38Z" - latency: 751.236µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-24T23:12:38Z" - latency: 1.769772ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-24T23:12:38Z" kind: List metadata: resourceVersion: ""