apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "21234" uid: ec044b44-08c5-4f3c-8823-e40c476b1e40 spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T21:51:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 966.62µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:58:19Z" - latency: 1.011055ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:57:19Z" - latency: 1.255861ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:19Z" - latency: 948.739µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:19Z" - latency: 952.173µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:19Z" - latency: 1.359025ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:19Z" - latency: 1.044071ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:19Z" - latency: 1.046586ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:51:19Z" - latency: 1.084914ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:50:19Z" - latency: 840.356µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:49:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "20329" uid: e003be05-ce67-4dd4-91bb-26eeb3d88320 spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:50:19Z" message: 'load-balancer-api-external: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 15.750684ms message: 'load-balancer-api-external: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:19Z" - latency: 6.211665ms message: 'load-balancer-api-external: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:56:19Z" - latency: 16.272192ms message: 'load-balancer-api-external: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:19Z" - latency: 6.2905ms message: 'load-balancer-api-external: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:55:19Z" - latency: 16.352864ms message: 'load-balancer-api-external: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:19Z" - latency: 5.883064ms message: 'load-balancer-api-external: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:54:19Z" - latency: 16.720588ms message: 'load-balancer-api-external: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:19Z" - latency: 6.597131ms message: 'load-balancer-api-external: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:53:19Z" - latency: 22.922986ms message: 'load-balancer-api-external: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:19Z" - latency: 5.788542ms message: 'load-balancer-api-external: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "20330" uid: ad5f8781-5dbe-4403-a17c-293fee82b139 spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T21:50:19Z" message: 'load-balancer-api-internal: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 17.49474ms message: 'load-balancer-api-internal: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:19Z" - latency: 6.262256ms message: 'load-balancer-api-internal: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:56:19Z" - latency: 17.369568ms message: 'load-balancer-api-internal: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:19Z" - latency: 6.339923ms message: 'load-balancer-api-internal: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:55:19Z" - latency: 16.377815ms message: 'load-balancer-api-internal: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:19Z" - latency: 5.810559ms message: 'load-balancer-api-internal: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:54:19Z" - latency: 17.385713ms message: 'load-balancer-api-internal: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:19Z" - latency: 6.570263ms message: 'load-balancer-api-internal: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:53:19Z" - latency: 22.895037ms message: 'load-balancer-api-internal: tcp connection to ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:19Z" - latency: 5.847607ms message: 'load-balancer-api-internal: resolved host name ac99b569c0f1d439090f5a95af9ddd76-3ef958aedc0a81a1.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T21:52:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-ip-10-0-141-123 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "21233" uid: 403d8d40-9c98-4a22-a043-9f5124fcbecb spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:19Z" message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.011411ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:58:19Z" - latency: 1.048334ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:57:19Z" - latency: 1.216552ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:19Z" - latency: 1.138966ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:19Z" - latency: 1.082299ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:19Z" - latency: 1.319403ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:19Z" - latency: 1.176085ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:19Z" - latency: 1.187994ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:51:19Z" - latency: 1.473234ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:50:19Z" - latency: 1.173913ms message: 'network-check-target-ip-10-0-141-123: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:49:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:27Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-ip-10-0-141-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "21298" uid: 62a49bec-8c63-43a6-a4d6-65d810ab7a46 spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:27Z" message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.133907ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:58:27Z" - latency: 1.046797ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:57:27Z" - latency: 1.819072ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:27Z" - latency: 2.038304ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:27Z" - latency: 1.059039ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:27Z" - latency: 2.138724ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:27Z" - latency: 2.145549ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:27Z" - latency: 1.045268ms message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:51:27Z" - latency: 902.325µs message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:50:27Z" - latency: 902.054µs message: 'network-check-target-ip-10-0-141-55: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:49:27Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:30Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-ip-10-0-143-242 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "21439" uid: c8c9d07c-068d-43e7-aa06-73da7a889983 spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T21:51:30Z" message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.012909ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:58:30Z" - latency: 1.959979ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:57:30Z" - latency: 2.040222ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:30Z" - latency: 2.197153ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:30Z" - latency: 2.088771ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:30Z" - latency: 1.93328ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:30Z" - latency: 2.3339ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:30Z" - latency: 1.914955ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:51:30Z" - latency: 2.26122ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:50:30Z" - latency: 2.141968ms message: 'network-check-target-ip-10-0-143-242: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:49:30Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T21:44:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-123-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-123.ec2.internal uid: fa082e1e-73aa-442f-b58b-6bf48e152952 resourceVersion: "20328" uid: 987dae97-b811-460b-9ce3-81b1eda4491f spec: sourcePod: network-check-source-6f78d59f99-vch52 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T21:50:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.907329ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:56:19Z" - latency: 1.768035ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:56:19Z" - latency: 879.582µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:55:19Z" - latency: 1.670496ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:55:19Z" - latency: 2.086119ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:54:19Z" - latency: 1.654016ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:54:19Z" - latency: 769.549µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:53:19Z" - latency: 1.888612ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:53:19Z" - latency: 721.587µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T21:52:19Z" - latency: 1.574046ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T21:52:19Z" kind: List metadata: resourceVersion: ""