apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46355" uid: ea210d0a-31bc-4064-ae06-49b30b67c39a spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T15:41:32Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.432817ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 1.260208ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 1.106143ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 1.051068ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 1.170137ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 951.394µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:11:32Z" - latency: 1.036542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:10:32Z" - latency: 904.632µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:09:32Z" - latency: 767.301µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:08:32Z" - latency: 894.747µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:07:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46357" uid: 1d6b4836-bce5-4373-ad53-8a7f1b356586 spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T15:40:32Z" message: 'load-balancer-api-external: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.452319ms message: 'load-balancer-api-external: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 8.392164ms message: 'load-balancer-api-external: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:16:32Z" - latency: 5.003044ms message: 'load-balancer-api-external: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 8.062107ms message: 'load-balancer-api-external: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:15:32Z" - latency: 5.062042ms message: 'load-balancer-api-external: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 6.738005ms message: 'load-balancer-api-external: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:14:32Z" - latency: 4.285102ms message: 'load-balancer-api-external: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 7.718031ms message: 'load-balancer-api-external: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:13:32Z" - latency: 5.096247ms message: 'load-balancer-api-external: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 8.84197ms message: 'load-balancer-api-external: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:12:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46356" uid: d753888c-9bd6-48a1-af8c-0617dcc97c9c spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T15:40:32Z" message: 'load-balancer-api-internal: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.454266ms message: 'load-balancer-api-internal: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 8.421117ms message: 'load-balancer-api-internal: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:16:32Z" - latency: 5.029947ms message: 'load-balancer-api-internal: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 8.372945ms message: 'load-balancer-api-internal: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:15:32Z" - latency: 4.165584ms message: 'load-balancer-api-internal: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 6.799904ms message: 'load-balancer-api-internal: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:14:32Z" - latency: 4.725749ms message: 'load-balancer-api-internal: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 7.807596ms message: 'load-balancer-api-internal: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:13:32Z" - latency: 5.058781ms message: 'load-balancer-api-internal: tcp connection to a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 8.869166ms message: 'load-balancer-api-internal: resolved host name a4b5cb0776afe441d9d7a74ce7eadaf5-35879f5de47f5132.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T16:12:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-network-check-target-ip-10-0-130-227 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46353" uid: 9edbf8aa-2973-49b9-ba30-8c5a8faef9a7 spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T15:41:32Z" message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.787936ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 2.448165ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 2.557996ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 2.403229ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 2.256527ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 2.431155ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:11:32Z" - latency: 2.148616ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:10:32Z" - latency: 3.305868ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:09:32Z" - latency: 2.656064ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:08:32Z" - latency: 2.308093ms message: 'network-check-target-ip-10-0-130-227: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:07:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-network-check-target-ip-10-0-138-16 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46351" uid: c1986f7f-b1cb-44ab-9447-21878a438d96 spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T15:41:32Z" message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.627255ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 927.396µs message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 951.657µs message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 864.77µs message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 1.194997ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 1.324362ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:11:32Z" - latency: 832.672µs message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:10:32Z" - latency: 1.132298ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:09:32Z" - latency: 1.274596ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:08:32Z" - latency: 1.119453ms message: 'network-check-target-ip-10-0-138-16: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:07:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-network-check-target-ip-10-0-141-222 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46354" uid: 54b2c1f2-9739-4d17-855e-5a6380e73ad7 spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T15:41:32Z" message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.50386ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 2.263481ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 2.015619ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 2.159229ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 2.210291ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 2.483507ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:11:32Z" - latency: 2.082681ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:10:32Z" - latency: 2.024591ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:09:32Z" - latency: 2.167114ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:08:32Z" - latency: 2.282922ms message: 'network-check-target-ip-10-0-141-222: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:07:32Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T15:34:31Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-16-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-16.ec2.internal uid: 7141560f-20cf-4ab2-a5f6-594902522e55 resourceVersion: "46352" uid: b04efead-bc7b-40ff-a3a8-ce6cd7e63916 spec: sourcePod: network-check-source-7f44b6dd87-vp9sn targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T15:40:32Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 943.366µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:16:32Z" - latency: 2.018032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T16:16:32Z" - latency: 1.116334ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:15:32Z" - latency: 1.933251ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T16:15:32Z" - latency: 1.07385ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:14:32Z" - latency: 1.775699ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T16:14:32Z" - latency: 889.15µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:13:32Z" - latency: 1.654474ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T16:13:32Z" - latency: 943.22µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T16:12:32Z" - latency: 1.72182ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T16:12:32Z" kind: List metadata: resourceVersion: ""