apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "46433" uid: 8d9a3311-cf38-40ad-92a4-5935ab218f91 spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-03T03:33:13Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.053557ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 1.082122ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 848.363µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 1.259079ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:51:13Z" - latency: 1.367867ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:50:13Z" - latency: 1.367848ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:49:13Z" - latency: 877.981µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:48:13Z" - latency: 1.095476ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:47:13Z" - latency: 1.013737ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:46:13Z" - latency: 871.137µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:45:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "48510" uid: 41784b7a-43cd-43a6-83f0-8c6c0d029578 spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T03:32:13Z" message: 'load-balancer-api-external: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.103184ms message: 'load-balancer-api-external: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:56:13Z" - latency: 7.672517ms message: 'load-balancer-api-external: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:56:13Z" - latency: 4.990231ms message: 'load-balancer-api-external: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:55:13Z" - latency: 9.011747ms message: 'load-balancer-api-external: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:55:13Z" - latency: 3.451613ms message: 'load-balancer-api-external: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 8.363212ms message: 'load-balancer-api-external: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:54:13Z" - latency: 5.021999ms message: 'load-balancer-api-external: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 8.362764ms message: 'load-balancer-api-external: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:53:13Z" - latency: 6.220993ms message: 'load-balancer-api-external: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 8.455799ms message: 'load-balancer-api-external: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:52:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "48511" uid: e657d825-3d5b-41b4-adbb-00acee17162b spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-03T03:32:13Z" message: 'load-balancer-api-internal: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.045488ms message: 'load-balancer-api-internal: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:56:13Z" - latency: 7.730359ms message: 'load-balancer-api-internal: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:56:13Z" - latency: 3.821616ms message: 'load-balancer-api-internal: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:55:13Z" - latency: 8.967327ms message: 'load-balancer-api-internal: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:55:13Z" - latency: 4.549426ms message: 'load-balancer-api-internal: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 8.387653ms message: 'load-balancer-api-internal: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:54:13Z" - latency: 5.240435ms message: 'load-balancer-api-internal: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 8.264157ms message: 'load-balancer-api-internal: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:53:13Z" - latency: 6.127259ms message: 'load-balancer-api-internal: tcp connection to a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 8.405024ms message: 'load-balancer-api-internal: resolved host name a9b24e8dd587d42f3bb923a0da23c565-9dad8efe6b118f8f.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-03T03:52:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-network-check-target-ip-10-0-130-55 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "46432" uid: f5349cca-2834-4b35-a29c-3a6fc6ebee05 spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-03T03:33:13Z" message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.326448ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 2.535543ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 2.284107ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 2.066295ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:51:13Z" - latency: 2.806568ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:50:13Z" - latency: 2.09136ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:49:13Z" - latency: 2.051028ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:48:13Z" - latency: 2.239788ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:47:13Z" - latency: 2.134806ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:46:13Z" - latency: 2.571434ms message: 'network-check-target-ip-10-0-130-55: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:45:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-network-check-target-ip-10-0-132-105 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "46430" uid: c25c8e7d-2c04-43fc-90ca-6ab1d34cf4d0 spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-03T03:33:13Z" message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 775.996µs message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 1.112931ms message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 1.602942ms message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 884.146µs message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:51:13Z" - latency: 1.032051ms message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:50:13Z" - latency: 1.185517ms message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:49:13Z" - latency: 812.75µs message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:48:13Z" - latency: 1.362373ms message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:47:13Z" - latency: 858.253µs message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:46:13Z" - latency: 1.535265ms message: 'network-check-target-ip-10-0-132-105: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:45:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-network-check-target-ip-10-0-141-253 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "46431" uid: 545905a5-d28e-4b6c-86da-29124789a36f spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-03T03:33:13Z" message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.181343ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 2.206875ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 2.070134ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 2.196332ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:51:13Z" - latency: 2.103121ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:50:13Z" - latency: 2.446106ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:49:13Z" - latency: 1.878159ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:48:13Z" - latency: 2.25212ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:47:13Z" - latency: 2.277465ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:46:13Z" - latency: 2.291999ms message: 'network-check-target-ip-10-0-141-253: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:45:13Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-03T03:26:12Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-105-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-105.ec2.internal uid: 7df3ef4f-c329-4bf7-bdab-efd62e47bff0 resourceVersion: "48509" uid: 6f179ea4-a255-452f-9d78-28017fbe6a98 spec: sourcePod: network-check-source-56d84b9f44-9792g targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-03T03:32:13Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 892.074µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:56:13Z" - latency: 1.709145ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T03:56:13Z" - latency: 996.224µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:55:13Z" - latency: 1.82395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T03:55:13Z" - latency: 874.412µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:54:13Z" - latency: 1.692817ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T03:54:13Z" - latency: 806.224µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:53:13Z" - latency: 1.591188ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T03:53:13Z" - latency: 1.016064ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-03T03:52:13Z" - latency: 1.822276ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-03T03:52:13Z" kind: List metadata: resourceVersion: ""