apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "43565" uid: 4fc72120-a658-45ee-bc9d-d5ee3f5f5085 spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-20T15:05:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.060959ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 1.063721ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 864.587µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 959.555µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:23:04Z" - latency: 1.036704ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:22:04Z" - latency: 918.419µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:21:04Z" - latency: 1.614075ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:20:04Z" - latency: 828.123µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:19:04Z" - latency: 893.818µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:18:04Z" - latency: 1.120002ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "45738" uid: 530d5b07-0c72-48a3-bf67-f9f27ffad124 spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T15:04:04Z" message: 'load-balancer-api-external: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.909294ms message: 'load-balancer-api-external: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:04Z" - latency: 18.207907ms message: 'load-balancer-api-external: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:28:04Z" - latency: 3.932525ms message: 'load-balancer-api-external: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:04Z" - latency: 8.431716ms message: 'load-balancer-api-external: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:27:04Z" - latency: 5.071243ms message: 'load-balancer-api-external: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 7.44179ms message: 'load-balancer-api-external: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:26:04Z" - latency: 4.14469ms message: 'load-balancer-api-external: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 10.006995ms message: 'load-balancer-api-external: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:25:04Z" - latency: 4.007506ms message: 'load-balancer-api-external: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 9.793503ms message: 'load-balancer-api-external: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:24:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "45737" uid: 5000ad32-df8e-4b3b-947e-a262c58d8d2c spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-20T15:04:04Z" message: 'load-balancer-api-internal: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 3.01432ms message: 'load-balancer-api-internal: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:04Z" - latency: 19.390595ms message: 'load-balancer-api-internal: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:28:04Z" - latency: 3.392784ms message: 'load-balancer-api-internal: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:04Z" - latency: 8.497014ms message: 'load-balancer-api-internal: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:27:04Z" - latency: 3.309676ms message: 'load-balancer-api-internal: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 7.382914ms message: 'load-balancer-api-internal: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:26:04Z" - latency: 3.423491ms message: 'load-balancer-api-internal: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 10.103381ms message: 'load-balancer-api-internal: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:25:04Z" - latency: 4.015618ms message: 'load-balancer-api-internal: tcp connection to afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 9.859872ms message: 'load-balancer-api-internal: resolved host name afbb6d12d071b4558aca059a62c93d09-95185423be8a31ad.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-20T15:24:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-network-check-target-ip-10-0-129-82 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "43564" uid: bbd81238-ef0f-46eb-854d-a85d4c19f70a spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T15:05:04Z" message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207987ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 2.370989ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 2.535322ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 2.180986ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:23:04Z" - latency: 2.240321ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:22:04Z" - latency: 2.128103ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:21:04Z" - latency: 2.342815ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:20:04Z" - latency: 2.011063ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:19:04Z" - latency: 2.185345ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:18:04Z" - latency: 2.558824ms message: 'network-check-target-ip-10-0-129-82: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-network-check-target-ip-10-0-140-93 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "43562" uid: f8bbca33-54ef-4a4d-a426-79d0a7bd7d08 spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-20T15:05:04Z" message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 806.304µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 1.002242ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 759.422µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 938.003µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:23:04Z" - latency: 1.297985ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:22:04Z" - latency: 928.69µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:21:04Z" - latency: 715.536µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:20:04Z" - latency: 938.87µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:19:04Z" - latency: 806.409µs message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:18:04Z" - latency: 1.190831ms message: 'network-check-target-ip-10-0-140-93: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-network-check-target-ip-10-0-142-255 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "43563" uid: 13955068-3382-4cba-bee3-8afd9d10919d spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-20T15:05:04Z" message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.206982ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 2.24629ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 2.512537ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 1.687789ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:23:04Z" - latency: 2.269361ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:22:04Z" - latency: 2.137829ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:21:04Z" - latency: 2.256412ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:20:04Z" - latency: 2.12871ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:19:04Z" - latency: 2.108443ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:18:04Z" - latency: 2.195998ms message: 'network-check-target-ip-10-0-142-255: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:17:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-20T14:58:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-140-93-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-140-93.ec2.internal uid: efb3ff41-3553-45ef-b471-56e057f1df08 resourceVersion: "45736" uid: e4fabc42-b0db-4618-9700-cd0ed2221bab spec: sourcePod: network-check-source-8894fc9bd-fmqbm targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-20T15:04:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 830.447µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:28:04Z" - latency: 2.313722ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:28:04Z" - latency: 1.148684ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:27:04Z" - latency: 1.504351ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:27:04Z" - latency: 759.655µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:26:04Z" - latency: 1.720191ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:26:04Z" - latency: 773.73µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:25:04Z" - latency: 1.782434ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:25:04Z" - latency: 1.254715ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-20T15:24:04Z" - latency: 1.642905ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-20T15:24:04Z" kind: List metadata: resourceVersion: ""