apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "31013" uid: 6bcf86ac-6ad2-4118-8767-79121d69f2e0 spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T18:34:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.50797ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:41:37Z" - latency: 901.517µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:40:37Z" - latency: 1.137614ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 967.798µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 1.006682ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 1.657926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 919.285µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 971.005µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:37Z" - latency: 921.567µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:37Z" - latency: 950.823µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "29247" uid: 27ef42c8-0839-4106-b4b8-8962f9054e0d spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T18:33:37Z" message: 'load-balancer-api-external: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.542189ms message: 'load-balancer-api-external: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 7.457186ms message: 'load-balancer-api-external: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:39:37Z" - latency: 5.052665ms message: 'load-balancer-api-external: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 7.187618ms message: 'load-balancer-api-external: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:38:37Z" - latency: 6.200909ms message: 'load-balancer-api-external: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 6.918634ms message: 'load-balancer-api-external: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:37:37Z" - latency: 5.033582ms message: 'load-balancer-api-external: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 8.98784ms message: 'load-balancer-api-external: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:36:37Z" - latency: 4.119671ms message: 'load-balancer-api-external: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 7.959114ms message: 'load-balancer-api-external: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:35:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "29246" uid: 64bbcf35-a61f-4d6e-b32f-26e4d4395afd spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T18:33:37Z" message: 'load-balancer-api-internal: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.061591ms message: 'load-balancer-api-internal: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 7.420138ms message: 'load-balancer-api-internal: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:39:37Z" - latency: 5.091603ms message: 'load-balancer-api-internal: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 7.132114ms message: 'load-balancer-api-internal: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:38:37Z" - latency: 5.665557ms message: 'load-balancer-api-internal: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 6.88913ms message: 'load-balancer-api-internal: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:37:37Z" - latency: 5.042622ms message: 'load-balancer-api-internal: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 8.956242ms message: 'load-balancer-api-internal: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:36:37Z" - latency: 4.1484ms message: 'load-balancer-api-internal: tcp connection to a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 7.904158ms message: 'load-balancer-api-internal: resolved host name a050642c58c6a495c9851412aa65f3c9-b2cb64c02015c519.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T18:35:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-network-check-target-ip-10-0-132-252 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "31009" uid: 61189937-0f06-4f8a-84c6-53c08d9b14d8 spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:34:37Z" message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.063474ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:41:37Z" - latency: 2.162568ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:40:37Z" - latency: 2.066609ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 1.895784ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 2.072304ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 1.957333ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 1.993428ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 1.978622ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:37Z" - latency: 1.974107ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:37Z" - latency: 1.76397ms message: 'network-check-target-ip-10-0-132-252: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-network-check-target-ip-10-0-135-182 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "31010" uid: bb848b2d-6443-40c4-a4ff-977aad9ce781 spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:34:37Z" message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.392703ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:41:37Z" - latency: 1.914905ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:40:37Z" - latency: 2.378051ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 2.167684ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 2.28303ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 2.266211ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 2.008469ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 2.199225ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:37Z" - latency: 1.936282ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:37Z" - latency: 2.107066ms message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-network-check-target-ip-10-0-139-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "31008" uid: b018613f-7336-4b5c-bb42-7de60709b1b6 spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T18:34:37Z" message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.191154ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:41:37Z" - latency: 979.77µs message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:40:37Z" - latency: 933.183µs message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 866.363µs message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 965.294µs message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 975.806µs message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 1.154374ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 1.066927ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:34:37Z" - latency: 1.484157ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:33:37Z" - latency: 1.530044ms message: 'network-check-target-ip-10-0-139-164: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:32:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T18:27:37Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-164-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-164.ec2.internal uid: cb3b96cc-ca94-4b76-a5c3-7d0914196beb resourceVersion: "29244" uid: c21709fc-bf2d-49c3-8bf4-42e2ef1c83fc spec: sourcePod: network-check-source-dbd9cf844-4wftk targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T18:33:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 809.469µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:39:37Z" - latency: 1.699535ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:39:37Z" - latency: 1.11648ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:38:37Z" - latency: 1.662965ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:38:37Z" - latency: 956.777µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:37:37Z" - latency: 1.750758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:37:37Z" - latency: 776.693µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:36:37Z" - latency: 1.920893ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:36:37Z" - latency: 881.746µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T18:35:37Z" - latency: 2.031387ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T18:35:37Z" kind: List metadata: resourceVersion: ""