apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "30136" uid: f559428f-d874-421b-8d67-2ae1a2881d34 spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T01:53:04Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.086211ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:00:04Z" - latency: 885.652µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:59:04Z" - latency: 842.725µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 1.404542ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 974.912µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 810.292µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 1.506958ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 1.018227ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:53:04Z" - latency: 1.158591ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:52:04Z" - latency: 1.206063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "28588" uid: b6796ee3-c5ad-4f01-b606-3b8b8198ada8 spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T01:52:04Z" message: 'load-balancer-api-external: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.699587ms message: 'load-balancer-api-external: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 8.05705ms message: 'load-balancer-api-external: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:58:04Z" - latency: 5.292428ms message: 'load-balancer-api-external: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 8.387738ms message: 'load-balancer-api-external: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:57:04Z" - latency: 5.505125ms message: 'load-balancer-api-external: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 7.377412ms message: 'load-balancer-api-external: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:56:04Z" - latency: 5.490662ms message: 'load-balancer-api-external: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 7.606239ms message: 'load-balancer-api-external: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:55:04Z" - latency: 5.46394ms message: 'load-balancer-api-external: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 8.620466ms message: 'load-balancer-api-external: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:54:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "28589" uid: 6349345d-29aa-4616-950f-e0526f17b808 spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T01:52:04Z" message: 'load-balancer-api-internal: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.744631ms message: 'load-balancer-api-internal: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 8.143743ms message: 'load-balancer-api-internal: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:58:04Z" - latency: 5.354926ms message: 'load-balancer-api-internal: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 8.355058ms message: 'load-balancer-api-internal: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:57:04Z" - latency: 4.962956ms message: 'load-balancer-api-internal: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 7.481961ms message: 'load-balancer-api-internal: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:56:04Z" - latency: 5.409869ms message: 'load-balancer-api-internal: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 7.536813ms message: 'load-balancer-api-internal: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:55:04Z" - latency: 5.674598ms message: 'load-balancer-api-internal: tcp connection to a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 8.564281ms message: 'load-balancer-api-internal: resolved host name a3aa42e41384546e281191cb33b463a4-3dd1856a46811cf0.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T01:54:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-ip-10-0-129-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "30133" uid: c1f0fb07-491b-4a5e-9a95-64aa5a0de054 spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:53:04Z" message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 963.387µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:00:04Z" - latency: 936.941µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:59:04Z" - latency: 1.56912ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 1.63432ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 1.313044ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 1.002811ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 1.218575ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 1.217112ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:53:04Z" - latency: 1.005361ms message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:52:04Z" - latency: 862.883µs message: 'network-check-target-ip-10-0-129-109: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-ip-10-0-135-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "30135" uid: 1d30b6b9-8755-463f-972f-b6e27a4301fc spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:53:04Z" message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.369275ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:00:04Z" - latency: 2.216605ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:59:04Z" - latency: 2.226182ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 2.434063ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 2.301605ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 2.370189ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 3.697464ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 2.560077ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:53:04Z" - latency: 2.500776ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:52:04Z" - latency: 2.67865ms message: 'network-check-target-ip-10-0-135-117: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-ip-10-0-136-21 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "30134" uid: 5c8ac20d-b8fb-4578-ad9c-7a60d6cbf286 spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T01:53:04Z" message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.531749ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T02:00:04Z" - latency: 2.088988ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:59:04Z" - latency: 2.346299ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 2.492677ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 2.409192ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 2.136303ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 2.818928ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 2.166098ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:53:04Z" - latency: 2.790728ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:52:04Z" - latency: 2.400435ms message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:51:04Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T01:46:03Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-129-109-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-129-109.ec2.internal uid: d5e0401f-17b7-434a-a465-3f25fe885ad7 resourceVersion: "28587" uid: eeab405d-6052-4f56-9a41-ca352cd9e1d6 spec: sourcePod: network-check-source-56d84b9f44-r2vbd targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T01:52:04Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 955.229µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:58:04Z" - latency: 2.193395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:58:04Z" - latency: 1.01803ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:57:04Z" - latency: 1.730064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:57:04Z" - latency: 900.17µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:56:04Z" - latency: 2.258646ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:56:04Z" - latency: 973.826µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:55:04Z" - latency: 2.407534ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:55:04Z" - latency: 919.496µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T01:54:04Z" - latency: 2.881143ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T01:54:04Z" kind: List metadata: resourceVersion: ""