apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "53429" uid: 08bde2c9-97b6-431d-a8d6-92bf4d53cc68 spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T18:55:53Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 936.731µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:23:53Z" - latency: 1.094205ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:22:53Z" - latency: 1.233796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:21:53Z" - latency: 1.00142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:20:53Z" - latency: 1.211833ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:53Z" - latency: 1.257053ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 861.29µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 1.029844ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 1.016847ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 818.899µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "48640" uid: f3010ebc-0608-4ed7-935c-fb73f441d7c7 spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:54:53Z" message: 'load-balancer-api-external: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.86781ms message: 'load-balancer-api-external: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 7.271087ms message: 'load-balancer-api-external: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:18:53Z" - latency: 5.606898ms message: 'load-balancer-api-external: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 10.255215ms message: 'load-balancer-api-external: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:17:53Z" - latency: 6.403058ms message: 'load-balancer-api-external: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 8.986272ms message: 'load-balancer-api-external: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:16:53Z" - latency: 4.101552ms message: 'load-balancer-api-external: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 8.442358ms message: 'load-balancer-api-external: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:15:53Z" - latency: 6.928449ms message: 'load-balancer-api-external: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - latency: 7.759261ms message: 'load-balancer-api-external: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:14:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "48641" uid: 5daa0600-9808-4660-9fbb-bb850c1654bc spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T18:54:53Z" message: 'load-balancer-api-internal: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.455413ms message: 'load-balancer-api-internal: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 7.23365ms message: 'load-balancer-api-internal: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:18:53Z" - latency: 5.970391ms message: 'load-balancer-api-internal: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 10.218688ms message: 'load-balancer-api-internal: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:17:53Z" - latency: 6.349132ms message: 'load-balancer-api-internal: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 9.002585ms message: 'load-balancer-api-internal: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:16:53Z" - latency: 4.086401ms message: 'load-balancer-api-internal: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 8.340881ms message: 'load-balancer-api-internal: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:15:53Z" - latency: 4.444608ms message: 'load-balancer-api-internal: tcp connection to a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - latency: 7.815351ms message: 'load-balancer-api-internal: resolved host name a52eae3d5edf04636af69a5823b39e0a-7258eb61d706af8e.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T19:14:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-network-check-target-ip-10-0-130-48 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "53427" uid: 4cb2bb62-146b-47a7-a917-7804a481b4b0 spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:55:53Z" message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.757659ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:23:53Z" - latency: 2.324263ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:22:53Z" - latency: 2.760168ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:21:53Z" - latency: 2.920405ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:20:53Z" - latency: 2.494962ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:53Z" - latency: 2.396127ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 2.458895ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 2.567852ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 2.648628ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 2.796603ms message: 'network-check-target-ip-10-0-130-48: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-network-check-target-ip-10-0-135-240 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "53428" uid: 86d8f4cd-159a-4af1-a9f5-bc6ff3989721 spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:55:53Z" message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.407698ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:23:53Z" - latency: 2.62068ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:22:53Z" - latency: 2.054975ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:21:53Z" - latency: 2.887323ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:20:53Z" - latency: 1.772929ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:53Z" - latency: 2.4207ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 2.372722ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 2.176008ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 2.390677ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 2.077074ms message: 'network-check-target-ip-10-0-135-240: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-network-check-target-ip-10-0-143-239 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "53426" uid: 1f9ec29a-a82b-45c0-8492-22a3dd34154c spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-08T18:55:53Z" message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.172265ms message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:23:53Z" - latency: 878.252µs message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:22:53Z" - latency: 1.256352ms message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:21:53Z" - latency: 1.257629ms message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:20:53Z" - latency: 860.668µs message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:19:53Z" - latency: 1.461053ms message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 1.479033ms message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 923.068µs message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 1.176468ms message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 800.91µs message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T18:48:52Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-239-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-239.ec2.internal uid: 1c46b27e-b7a0-442d-9d0a-f167939705d3 resourceVersion: "48639" uid: 4fcc3d1e-80e9-4835-b591-d09c33f982b8 spec: sourcePod: network-check-source-989f8b8dc-zbn2x targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T18:54:53Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 944.857µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:18:53Z" - latency: 1.662064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:18:53Z" - latency: 724.766µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:17:53Z" - latency: 2.247712ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:17:53Z" - latency: 859.635µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:16:53Z" - latency: 1.831884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:16:53Z" - latency: 911.758µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:15:53Z" - latency: 1.78776ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:15:53Z" - latency: 738.18µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T19:14:53Z" - latency: 1.535439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T19:14:53Z" kind: List metadata: resourceVersion: ""