apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "46131" uid: 0ab6d525-03c7-4659-b3a5-383a25019e8c spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-29T02:39:11Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.059254ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 1.119547ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 945.234µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 969.323µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:57:11Z" - latency: 1.374689ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:56:11Z" - latency: 995.307µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:55:11Z" - latency: 1.22251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:54:11Z" - latency: 1.516133ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:53:11Z" - latency: 1.207169ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:52:11Z" - latency: 1.04158ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:51:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "48616" uid: 25b1a857-68e3-4229-9946-de9f2f699075 spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T02:38:11Z" message: 'load-balancer-api-external: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.299277ms message: 'load-balancer-api-external: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:02:11Z" - latency: 6.29084ms message: 'load-balancer-api-external: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:02:11Z" - latency: 4.465927ms message: 'load-balancer-api-external: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:01:11Z" - latency: 7.239729ms message: 'load-balancer-api-external: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:01:11Z" - latency: 5.775754ms message: 'load-balancer-api-external: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 11.085073ms message: 'load-balancer-api-external: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:00:11Z" - latency: 4.369782ms message: 'load-balancer-api-external: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 7.009946ms message: 'load-balancer-api-external: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:59:11Z" - latency: 4.64677ms message: 'load-balancer-api-external: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 6.714862ms message: 'load-balancer-api-external: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:58:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "48614" uid: 2de2043f-1f76-4f3b-ab3e-b24a6a7bba4b spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-29T02:38:11Z" message: 'load-balancer-api-internal: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.288375ms message: 'load-balancer-api-internal: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:02:11Z" - latency: 6.341816ms message: 'load-balancer-api-internal: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:02:11Z" - latency: 4.34246ms message: 'load-balancer-api-internal: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:01:11Z" - latency: 7.293395ms message: 'load-balancer-api-internal: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:01:11Z" - latency: 5.690384ms message: 'load-balancer-api-internal: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 11.171588ms message: 'load-balancer-api-internal: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T03:00:11Z" - latency: 4.362335ms message: 'load-balancer-api-internal: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 7.036484ms message: 'load-balancer-api-internal: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:59:11Z" - latency: 4.297204ms message: 'load-balancer-api-internal: tcp connection to a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 6.748833ms message: 'load-balancer-api-internal: resolved host name a29b632f9aea94b088ab9408e7d68366-20037eba56da4507.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-29T02:58:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-network-check-target-ip-10-0-131-78 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "46130" uid: 7d17ab60-ab58-4b9d-bd36-29031536a99f spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-29T02:39:11Z" message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.377494ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 2.282963ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 2.326446ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 2.224415ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:57:11Z" - latency: 3.386395ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:56:11Z" - latency: 3.089358ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:55:11Z" - latency: 2.122284ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:54:11Z" - latency: 2.340007ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:53:11Z" - latency: 2.163413ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:52:11Z" - latency: 2.125943ms message: 'network-check-target-ip-10-0-131-78: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:51:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-network-check-target-ip-10-0-133-245 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "46129" uid: 685d5cda-4400-4b07-9b63-55a17a236962 spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-29T02:39:11Z" message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.694205ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 1.895964ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 1.898302ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 1.766443ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:57:11Z" - latency: 2.00462ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:56:11Z" - latency: 1.754496ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:55:11Z" - latency: 1.951193ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:54:11Z" - latency: 1.940133ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:53:11Z" - latency: 2.004705ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:52:11Z" - latency: 2.053726ms message: 'network-check-target-ip-10-0-133-245: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:51:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-network-check-target-ip-10-0-141-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "46128" uid: ce3e442f-0303-49a5-a9d0-17045d4a71b3 spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-05-29T02:39:11Z" message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 900.434µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 914.973µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 872.53µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 833.24µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:57:11Z" - latency: 747.571µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:56:11Z" - latency: 851.274µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:55:11Z" - latency: 1.044681ms message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:54:11Z" - latency: 815.755µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:53:11Z" - latency: 1.343587ms message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:52:11Z" - latency: 812.784µs message: 'network-check-target-ip-10-0-141-109: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:51:11Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-29T02:32:10Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-109-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-109.ec2.internal uid: 7d94a24f-6a67-4310-8c28-587bfb128ae5 resourceVersion: "48611" uid: 2a76a55b-bf84-477a-bdbb-7cc116a43b15 spec: sourcePod: network-check-source-7f44b6dd87-nm8fs targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-29T02:38:11Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.242µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:02:11Z" - latency: 1.676215ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:02:11Z" - latency: 984.261µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:01:11Z" - latency: 1.620653ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:01:11Z" - latency: 852.769µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T03:00:11Z" - latency: 1.806171ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T03:00:11Z" - latency: 784.197µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:59:11Z" - latency: 1.805183ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:59:11Z" - latency: 805.034µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-29T02:58:11Z" - latency: 1.686147ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-29T02:58:11Z" kind: List metadata: resourceVersion: ""