apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "19454" uid: a72babb1-25f5-4683-8496-4a31bc072993 spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T23:14:26Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 913.354µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 782.263µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 827.14µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:26:26Z" - latency: 1.316142ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:25:26Z" - latency: 1.866306ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:24:26Z" - latency: 1.224536ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:23:26Z" - latency: 857.973µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:22:26Z" - latency: 1.162485ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:21:26Z" - latency: 1.205348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:20:26Z" - latency: 858.002µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:19:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "20800" uid: bbd6e168-11b2-40a7-9d67-e49edb19ce56 spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T23:13:26Z" message: 'load-balancer-api-external: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.927019ms message: 'load-balancer-api-external: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:31:26Z" - latency: 8.921837ms message: 'load-balancer-api-external: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:31:26Z" - latency: 5.231101ms message: 'load-balancer-api-external: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:30:26Z" - latency: 8.959975ms message: 'load-balancer-api-external: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:30:26Z" - latency: 4.71426ms message: 'load-balancer-api-external: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:29:26Z" - latency: 8.219554ms message: 'load-balancer-api-external: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:29:26Z" - latency: 4.753079ms message: 'load-balancer-api-external: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 7.570452ms message: 'load-balancer-api-external: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:28:26Z" - latency: 4.327521ms message: 'load-balancer-api-external: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 10.039552ms message: 'load-balancer-api-external: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:27:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "20799" uid: 353c082b-0983-4f2e-ad85-9d06567a63ca spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T23:13:26Z" message: 'load-balancer-api-internal: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.965529ms message: 'load-balancer-api-internal: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:31:26Z" - latency: 8.86851ms message: 'load-balancer-api-internal: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:31:26Z" - latency: 5.244771ms message: 'load-balancer-api-internal: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:30:26Z" - latency: 9.003341ms message: 'load-balancer-api-internal: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:30:26Z" - latency: 4.709111ms message: 'load-balancer-api-internal: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:29:26Z" - latency: 8.187321ms message: 'load-balancer-api-internal: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:29:26Z" - latency: 4.752073ms message: 'load-balancer-api-internal: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 7.647099ms message: 'load-balancer-api-internal: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:28:26Z" - latency: 4.944969ms message: 'load-balancer-api-internal: tcp connection to a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 9.947526ms message: 'load-balancer-api-internal: resolved host name a500861fe6a9542cb89185fc8e632ad9-3d6a290bd73280e0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T23:27:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-network-check-target-ip-10-0-132-11 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "19453" uid: 55b352d5-133d-406a-b315-d914528ed6ca spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T23:14:26Z" message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.68588ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 1.783527ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 1.669421ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:26:26Z" - latency: 1.818287ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:25:26Z" - latency: 1.77452ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:24:26Z" - latency: 1.710996ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:23:26Z" - latency: 1.424144ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:22:26Z" - latency: 1.5368ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:21:26Z" - latency: 1.843686ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:20:26Z" - latency: 1.76468ms message: 'network-check-target-ip-10-0-132-11: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:19:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-network-check-target-ip-10-0-136-141 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "19451" uid: 917288ea-60ee-43f7-8ab0-f9370a45cdcd spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T23:14:26Z" message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.083452ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 1.850456ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 1.847336ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:26:26Z" - latency: 1.866111ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:25:26Z" - latency: 2.594193ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:24:26Z" - latency: 1.90243ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:23:26Z" - latency: 1.914794ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:22:26Z" - latency: 1.80606ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:21:26Z" - latency: 1.925442ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:20:26Z" - latency: 1.783515ms message: 'network-check-target-ip-10-0-136-141: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:19:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-network-check-target-ip-10-0-143-104 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "19452" uid: 188d771e-9f59-4dac-bf13-7052e620dc87 spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T23:14:26Z" message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.329557ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 840.224µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 926.153µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:26:26Z" - latency: 704.056µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:25:26Z" - latency: 3.080053ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:24:26Z" - latency: 831.538µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:23:26Z" - latency: 770.083µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:22:26Z" - latency: 977.258µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:21:26Z" - latency: 1.415025ms message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:20:26Z" - latency: 815.303µs message: 'network-check-target-ip-10-0-143-104: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:19:26Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T23:07:25Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-104-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-104.ec2.internal uid: c84ce64b-342b-4969-bfdb-4bc8658fbb9e resourceVersion: "20798" uid: 5463403f-f61c-45dc-8165-eb1c45928397 spec: sourcePod: network-check-source-7f44b6dd87-vfhc7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T23:13:26Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 889.882µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:31:26Z" - latency: 1.725469ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T23:31:26Z" - latency: 726.403µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:30:26Z" - latency: 2.403588ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T23:30:26Z" - latency: 713.03µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:29:26Z" - latency: 1.671685ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T23:29:26Z" - latency: 962.709µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:28:26Z" - latency: 1.573342ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T23:28:26Z" - latency: 772.464µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T23:27:26Z" - latency: 1.980437ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T23:27:26Z" kind: List metadata: resourceVersion: ""