apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "41187" uid: 62677cc3-6832-482b-a80d-3c07f958eca9 spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-08T18:21:24Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.166484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 956.096µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 932.864µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 801.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 1.144391ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:24Z" - latency: 1.083963ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:24Z" - latency: 911.873µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:24Z" - latency: 1.126579ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:24Z" - latency: 1.23791ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:41:24Z" - latency: 902.534µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "42100" uid: 14809810-8d53-455b-b659-ccb5d25785a9 spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T18:20:24Z" message: 'load-balancer-api-external: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.074412ms message: 'load-balancer-api-external: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:24Z" - latency: 6.505719ms message: 'load-balancer-api-external: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:50:24Z" - latency: 5.947836ms message: 'load-balancer-api-external: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 7.59249ms message: 'load-balancer-api-external: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:49:24Z" - latency: 5.454254ms message: 'load-balancer-api-external: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 6.790171ms message: 'load-balancer-api-external: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:48:24Z" - latency: 4.673291ms message: 'load-balancer-api-external: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 6.362034ms message: 'load-balancer-api-external: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:47:24Z" - latency: 5.338811ms message: 'load-balancer-api-external: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 12.745014ms message: 'load-balancer-api-external: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:46:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "42099" uid: 1db8f1bc-69a6-4eab-a92c-e94aa7ad4954 spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-08T18:20:24Z" message: 'load-balancer-api-internal: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.831671ms message: 'load-balancer-api-internal: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:24Z" - latency: 6.485199ms message: 'load-balancer-api-internal: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:50:24Z" - latency: 5.117378ms message: 'load-balancer-api-internal: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 7.668695ms message: 'load-balancer-api-internal: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:49:24Z" - latency: 4.624056ms message: 'load-balancer-api-internal: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 6.955146ms message: 'load-balancer-api-internal: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:48:24Z" - latency: 4.711096ms message: 'load-balancer-api-internal: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 6.328358ms message: 'load-balancer-api-internal: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:47:24Z" - latency: 5.353894ms message: 'load-balancer-api-internal: tcp connection to ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 12.814537ms message: 'load-balancer-api-internal: resolved host name ab6e26c727d824c789ba68c545872776-24bda6637586ad76.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-08T18:46:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-network-check-target-ip-10-0-131-154 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "41185" uid: 9b93acd4-3005-40c2-b142-51ca5e93b06d spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:21:24Z" message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.911503ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 1.948983ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 1.964934ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 2.086384ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 1.88402ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:24Z" - latency: 1.846616ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:24Z" - latency: 1.766136ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:24Z" - latency: 1.876546ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:24Z" - latency: 1.683118ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:41:24Z" - latency: 1.834026ms message: 'network-check-target-ip-10-0-131-154: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-network-check-target-ip-10-0-132-8 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "41184" uid: bbcfa7f0-852f-4111-bea6-3cb4bcc4e9b8 spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:21:24Z" message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 981.52µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 834.068µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 1.034201ms message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 974.323µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 1.181361ms message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:24Z" - latency: 718.565µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:24Z" - latency: 937.965µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:24Z" - latency: 975.821µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:24Z" - latency: 870.801µs message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:41:24Z" - latency: 1.078832ms message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-network-check-target-ip-10-0-136-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "41186" uid: 4bbfa6f4-a752-47a8-b915-017cfe291d0a spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-08T18:21:24Z" message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.275892ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 2.156456ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 2.282904ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 2.346991ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 2.263443ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:45:24Z" - latency: 2.147697ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:44:24Z" - latency: 2.096674ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:43:24Z" - latency: 2.335138ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:42:24Z" - latency: 2.2579ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:41:24Z" - latency: 2.268269ms message: 'network-check-target-ip-10-0-136-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:40:24Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-08T18:14:23Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-8-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-8.ec2.internal uid: d1cf8010-2b08-48cc-877e-498347788f18 resourceVersion: "42097" uid: 68e6fb2e-1253-4c6c-b177-82c9cad2f255 spec: sourcePod: network-check-source-dbd9cf844-88s76 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-08T18:20:24Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 797.879µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:50:24Z" - latency: 1.681639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:50:24Z" - latency: 1.126007ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:49:24Z" - latency: 1.713162ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:49:24Z" - latency: 866.722µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:48:24Z" - latency: 1.756034ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:48:24Z" - latency: 877.447µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:47:24Z" - latency: 1.687098ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:47:24Z" - latency: 895.027µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-08T18:46:24Z" - latency: 2.105148ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-08T18:46:24Z" kind: List metadata: resourceVersion: ""