apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "44714" uid: af156d32-1d71-411c-88cc-436809b715ec spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T15:20:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.237702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 777.054µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 1.142786ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 1.278319ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:38:36Z" - latency: 1.323384ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:37:36Z" - latency: 1.531558ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:36:36Z" - latency: 1.091741ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:35:36Z" - latency: 1.008917ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:34:36Z" - latency: 1.252793ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:33:36Z" - latency: 1.094257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:32:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "46724" uid: 7537c506-9327-47f5-b2a7-ce9cd40438f9 spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T15:19:36Z" message: 'load-balancer-api-external: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 7.083968ms message: 'load-balancer-api-external: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:36Z" - latency: 9.070852ms message: 'load-balancer-api-external: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:43:36Z" - latency: 4.207711ms message: 'load-balancer-api-external: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:36Z" - latency: 8.098531ms message: 'load-balancer-api-external: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:42:36Z" - latency: 7.30804ms message: 'load-balancer-api-external: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 9.432107ms message: 'load-balancer-api-external: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:41:36Z" - latency: 4.362831ms message: 'load-balancer-api-external: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 11.203213ms message: 'load-balancer-api-external: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:40:36Z" - latency: 7.421273ms message: 'load-balancer-api-external: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 11.292162ms message: 'load-balancer-api-external: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "46725" uid: 8dbbe1f9-9250-4766-9223-789e19839fc5 spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T15:19:36Z" message: 'load-balancer-api-internal: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 21.487296ms message: 'load-balancer-api-internal: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:36Z" - latency: 9.017183ms message: 'load-balancer-api-internal: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:43:36Z" - latency: 4.222971ms message: 'load-balancer-api-internal: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:36Z" - latency: 8.072679ms message: 'load-balancer-api-internal: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:42:36Z" - latency: 7.318441ms message: 'load-balancer-api-internal: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 9.330077ms message: 'load-balancer-api-internal: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:41:36Z" - latency: 5.534738ms message: 'load-balancer-api-internal: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 11.228958ms message: 'load-balancer-api-internal: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:40:36Z" - latency: 6.765797ms message: 'load-balancer-api-internal: tcp connection to ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 11.197554ms message: 'load-balancer-api-internal: resolved host name ae209e42d76ac43adb24a8c9718eb628-b73ee819bb70e19d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T15:39:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-network-check-target-ip-10-0-131-172 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "44712" uid: 5fafe02d-816c-491c-984a-248b7c6ef1d0 spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:20:36Z" message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.955µs message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 1.308893ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 907.71µs message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 1.143435ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:38:36Z" - latency: 743.277µs message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:37:36Z" - latency: 647.611µs message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:36:36Z" - latency: 1.046308ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:35:36Z" - latency: 978.035µs message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:34:36Z" - latency: 1.318495ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:33:36Z" - latency: 1.510622ms message: 'network-check-target-ip-10-0-131-172: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:32:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-network-check-target-ip-10-0-138-97 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "44713" uid: 13ed85fa-94f9-4d2d-b874-ba606d0aad84 spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:20:36Z" message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.144349ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 2.093412ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 2.029496ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 2.179302ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:38:36Z" - latency: 1.898885ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:37:36Z" - latency: 1.917675ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:36:36Z" - latency: 1.962091ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:35:36Z" - latency: 2.178085ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:34:36Z" - latency: 2.266578ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:33:36Z" - latency: 2.549607ms message: 'network-check-target-ip-10-0-138-97: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:32:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-network-check-target-ip-10-0-143-192 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "44711" uid: 26d31d8d-d528-4749-8775-ef36cce6e478 spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:20:36Z" message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.767517ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 1.949569ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 1.99161ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 1.737585ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:38:36Z" - latency: 1.768142ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:37:36Z" - latency: 1.33153ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:36:36Z" - latency: 1.667244ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:35:36Z" - latency: 1.918372ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:34:36Z" - latency: 1.930882ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:33:36Z" - latency: 2.002605ms message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:32:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:13:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-131-172-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-131-172.ec2.internal uid: 495baf98-f30d-48b9-b65a-a01f27de7fbf resourceVersion: "46723" uid: 44cc2a07-6c77-4dce-8bed-f746a36729b7 spec: sourcePod: network-check-source-dbd9cf844-hss6n targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T15:19:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.024988ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:43:36Z" - latency: 1.844794ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:43:36Z" - latency: 833.344µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:42:36Z" - latency: 1.920741ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:42:36Z" - latency: 932.967µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:41:36Z" - latency: 2.012328ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:41:36Z" - latency: 871.824µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:40:36Z" - latency: 1.984958ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:40:36Z" - latency: 892.4µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:39:36Z" - latency: 1.508248ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T15:39:36Z" kind: List metadata: resourceVersion: ""