apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "39062" uid: 0ae48786-da83-45bd-8dda-9b003f9150c4 spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T20:23:22Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 770.485µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:44:22Z" - latency: 900.943µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:43:22Z" - latency: 966.199µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:42:22Z" - latency: 1.385042ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:41:22Z" - latency: 780.522µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 1.17386ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 953.421µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 1.102421ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 959.693µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 1.304965ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:35:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "36134" uid: 95a442db-f6ce-41c0-88c1-ab235a8c171c spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:22:22Z" message: 'load-balancer-api-external: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.244744ms message: 'load-balancer-api-external: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 6.620723ms message: 'load-balancer-api-external: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:40:22Z" - latency: 5.509312ms message: 'load-balancer-api-external: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 6.982161ms message: 'load-balancer-api-external: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:39:22Z" - latency: 4.846842ms message: 'load-balancer-api-external: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 6.787226ms message: 'load-balancer-api-external: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:38:22Z" - latency: 4.180892ms message: 'load-balancer-api-external: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 7.337563ms message: 'load-balancer-api-external: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:37:22Z" - latency: 6.089029ms message: 'load-balancer-api-external: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 7.421024ms message: 'load-balancer-api-external: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:36:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "36133" uid: d08541cc-33d6-48ef-8963-5fe917f87575 spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T20:22:22Z" message: 'load-balancer-api-internal: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.430765ms message: 'load-balancer-api-internal: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 6.575753ms message: 'load-balancer-api-internal: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:40:22Z" - latency: 3.931484ms message: 'load-balancer-api-internal: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 6.936399ms message: 'load-balancer-api-internal: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:39:22Z" - latency: 4.20848ms message: 'load-balancer-api-internal: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 6.677385ms message: 'load-balancer-api-internal: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:38:22Z" - latency: 4.292826ms message: 'load-balancer-api-internal: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 7.284116ms message: 'load-balancer-api-internal: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:37:22Z" - latency: 6.167978ms message: 'load-balancer-api-internal: tcp connection to ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 7.37209ms message: 'load-balancer-api-internal: resolved host name ae1cb2b4aec9545e98054ef9f5b7a24e-b302cc2d46487325.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T20:36:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-network-check-target-ip-10-0-131-31 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "39060" uid: 86859eb6-c04b-4752-b2e8-e2d42211b488 spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:23:22Z" message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.195473ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:44:22Z" - latency: 1.925158ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:43:22Z" - latency: 2.162401ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:42:22Z" - latency: 2.155816ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:41:22Z" - latency: 2.360017ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 2.031109ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 2.48951ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 2.38406ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 2.313562ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 2.644749ms message: 'network-check-target-ip-10-0-131-31: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:35:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-network-check-target-ip-10-0-138-62 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "39059" uid: 5c6e545e-8c81-4285-840e-cde88153f9ba spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:23:22Z" message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.657945ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:44:22Z" - latency: 1.264241ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:43:22Z" - latency: 1.236534ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:42:22Z" - latency: 884.234µs message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:41:22Z" - latency: 1.268242ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 845.984µs message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 1.476028ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 1.092556ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 1.246369ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 1.372632ms message: 'network-check-target-ip-10-0-138-62: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:35:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-network-check-target-ip-10-0-141-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "39061" uid: 19caf406-dd2e-42db-b417-5fdfd7fcd670 spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-16T20:23:22Z" message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245662ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:44:22Z" - latency: 1.877384ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:43:22Z" - latency: 1.850066ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:42:22Z" - latency: 1.995089ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:41:22Z" - latency: 1.808671ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 2.144206ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 2.243411ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 2.433709ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 2.273296ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 2.062865ms message: 'network-check-target-ip-10-0-141-145: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:35:22Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T20:16:21Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-62-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-62.ec2.internal uid: e7cc1236-84ec-4d80-8c51-c5315e282ebf resourceVersion: "36131" uid: e76cad28-56b7-407e-9dcb-0ae68ecaa5a9 spec: sourcePod: network-check-source-8894fc9bd-vv4gp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T20:22:22Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.099165ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:40:22Z" - latency: 1.796462ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:40:22Z" - latency: 1.220464ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:39:22Z" - latency: 1.758495ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:39:22Z" - latency: 1.253634ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:38:22Z" - latency: 1.715267ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:38:22Z" - latency: 818.379µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:37:22Z" - latency: 1.887256ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:37:22Z" - latency: 846.257µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T20:36:22Z" - latency: 1.664395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T20:36:22Z" kind: List metadata: resourceVersion: ""