apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "44154" uid: 85810e76-9e0f-4499-b1b6-73b76176d3f4 spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-28T17:56:29Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 853.656µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:17:29Z" - latency: 1.130924ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:16:29Z" - latency: 1.355838ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:15:29Z" - latency: 878.668µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:14:29Z" - latency: 1.081879ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 1.025392ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 1.036702ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 1.020328ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 1.172136ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 1.040256ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:08:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "39620" uid: 69b7516c-ca59-4a3a-8063-c654f56feb79 spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:55:29Z" message: 'load-balancer-api-external: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.625334ms message: 'load-balancer-api-external: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 10.639972ms message: 'load-balancer-api-external: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:13:29Z" - latency: 5.033271ms message: 'load-balancer-api-external: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 6.155425ms message: 'load-balancer-api-external: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:12:29Z" - latency: 4.536253ms message: 'load-balancer-api-external: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 6.826179ms message: 'load-balancer-api-external: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:11:29Z" - latency: 5.328759ms message: 'load-balancer-api-external: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 6.607501ms message: 'load-balancer-api-external: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:10:29Z" - latency: 3.916705ms message: 'load-balancer-api-external: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 7.036227ms message: 'load-balancer-api-external: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:09:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "39618" uid: c4943eda-507a-40e2-93f9-3df348237dd8 spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-28T17:55:29Z" message: 'load-balancer-api-internal: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.612357ms message: 'load-balancer-api-internal: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 10.587362ms message: 'load-balancer-api-internal: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:13:29Z" - latency: 5.021714ms message: 'load-balancer-api-internal: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 6.038141ms message: 'load-balancer-api-internal: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:12:29Z" - latency: 4.576865ms message: 'load-balancer-api-internal: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 6.777546ms message: 'load-balancer-api-internal: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:11:29Z" - latency: 5.348719ms message: 'load-balancer-api-internal: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 6.492969ms message: 'load-balancer-api-internal: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:10:29Z" - latency: 3.883485ms message: 'load-balancer-api-internal: tcp connection to a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 7.134797ms message: 'load-balancer-api-internal: resolved host name a981872845e3243e0962f5ee5e18afaf-b3ccaca6ad3f4dbf.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-28T18:09:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-network-check-target-ip-10-0-132-117 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "44151" uid: 6c47037b-7f24-4a2e-be90-7d1c2892afbd spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:56:29Z" message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.526µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:17:29Z" - latency: 812.138µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:16:29Z" - latency: 1.507521ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:15:29Z" - latency: 873.133µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:14:29Z" - latency: 914.717µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 897.061µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 862.169µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 928.26µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 1.045427ms message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 860.789µs message: 'network-check-target-ip-10-0-132-117: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:08:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-network-check-target-ip-10-0-135-41 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "44153" uid: 6ff459ef-89b3-4cb2-b035-5bc2b74be301 spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:56:29Z" message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.19596ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:17:29Z" - latency: 2.091433ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:16:29Z" - latency: 2.625955ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:15:29Z" - latency: 1.986372ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:14:29Z" - latency: 2.253493ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 2.293137ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 2.429409ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 2.303552ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 2.369114ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 2.320238ms message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:08:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-network-check-target-ip-10-0-137-72 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "44152" uid: ce385393-478a-4bff-a45d-40f57bcd11d0 spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-28T17:56:29Z" message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.597876ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:17:29Z" - latency: 2.202946ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:16:29Z" - latency: 2.023166ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:15:29Z" - latency: 2.29982ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:14:29Z" - latency: 2.638351ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 2.307763ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 2.190831ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 2.315546ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 2.367167ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 2.17152ms message: 'network-check-target-ip-10-0-137-72: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:08:29Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-28T17:49:28Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-117-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-117.ec2.internal uid: d9ba327c-ef5e-4d3a-bc37-88b7877403d2 resourceVersion: "39616" uid: 91d61c50-d4d4-4507-a8a0-b3a97ec8f9aa spec: sourcePod: network-check-source-7f44b6dd87-72mnx targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-28T17:55:29Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 844.421µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:13:29Z" - latency: 1.852694ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:13:29Z" - latency: 815.107µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:12:29Z" - latency: 1.648621ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:12:29Z" - latency: 831.091µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:11:29Z" - latency: 1.913849ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:11:29Z" - latency: 1.250093ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:10:29Z" - latency: 1.724119ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:10:29Z" - latency: 917.407µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-28T18:09:29Z" - latency: 1.944898ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-28T18:09:29Z" kind: List metadata: resourceVersion: ""