apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31841" uid: 63de8598-df19-4ed5-9ab9-a6904f13abf6 spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-20T14:01:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 785.759µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 1.230273ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 1.051796ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 976.45µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 1.029864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 906.414µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:31:23Z" - latency: 1.304551ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:30:23Z" - latency: 1.012923ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:29:23Z" - latency: 781.388µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:28:23Z" - latency: 1.087257ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:27:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31842" uid: 8c4bab8a-c86f-44f5-b0ff-637100b6125a spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:00:23Z" message: 'load-balancer-api-external: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.579194ms message: 'load-balancer-api-external: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 10.145265ms message: 'load-balancer-api-external: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:36:23Z" - latency: 4.91462ms message: 'load-balancer-api-external: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 8.163336ms message: 'load-balancer-api-external: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:35:23Z" - latency: 4.138822ms message: 'load-balancer-api-external: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 7.929052ms message: 'load-balancer-api-external: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:34:23Z" - latency: 4.506714ms message: 'load-balancer-api-external: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 8.422044ms message: 'load-balancer-api-external: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:33:23Z" - latency: 5.379004ms message: 'load-balancer-api-external: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 7.698215ms message: 'load-balancer-api-external: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:32:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31843" uid: 97f1a4f8-d6e8-4118-982b-9b665b20e4c1 spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-20T14:00:23Z" message: 'load-balancer-api-internal: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.620496ms message: 'load-balancer-api-internal: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 10.165448ms message: 'load-balancer-api-internal: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:36:23Z" - latency: 4.997102ms message: 'load-balancer-api-internal: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 8.184556ms message: 'load-balancer-api-internal: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:35:23Z" - latency: 6.000247ms message: 'load-balancer-api-internal: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 7.960795ms message: 'load-balancer-api-internal: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:34:23Z" - latency: 4.541178ms message: 'load-balancer-api-internal: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 8.447974ms message: 'load-balancer-api-internal: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:33:23Z" - latency: 4.80195ms message: 'load-balancer-api-internal: tcp connection to aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 7.721891ms message: 'load-balancer-api-internal: resolved host name aab31c520b1474d5b97f52847a853fc6-290993764057abef.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-20T14:32:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-network-check-target-ip-10-0-132-156 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31839" uid: 0ad7c087-2637-4fe5-9748-7a1c2faceb5a spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:01:23Z" message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 815.92µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 1.219547ms message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 893.355µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 928.349µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 882.51µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 1.134923ms message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:31:23Z" - latency: 1.007455ms message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:30:23Z" - latency: 770.839µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:29:23Z" - latency: 704.074µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:28:23Z" - latency: 755.96µs message: 'network-check-target-ip-10-0-132-156: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:27:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-network-check-target-ip-10-0-136-75 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31837" uid: a2df6e93-252a-405d-a0c3-c64203bc5430 spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:01:23Z" message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.105157ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 2.170348ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 2.290916ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 2.101191ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 2.056661ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 2.236362ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:31:23Z" - latency: 2.26373ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:30:23Z" - latency: 2.18684ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:29:23Z" - latency: 1.974135ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:28:23Z" - latency: 1.67583ms message: 'network-check-target-ip-10-0-136-75: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:27:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-network-check-target-ip-10-0-137-148 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31840" uid: 446904e2-45f9-4b49-bf1a-c16dc3337770 spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-05-20T14:01:23Z" message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.670891ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 1.805604ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 1.793358ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 1.771632ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 2.054458ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 2.013728ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:31:23Z" - latency: 1.808231ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:30:23Z" - latency: 1.960479ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:29:23Z" - latency: 1.881212ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:28:23Z" - latency: 1.648654ms message: 'network-check-target-ip-10-0-137-148: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:27:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-20T13:54:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-156-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-156.ec2.internal uid: 199bac10-be8f-42a7-b2a6-77433176ee5c resourceVersion: "31838" uid: 5bbd467a-7cae-4566-bab9-bc6d88c23b6e spec: sourcePod: network-check-source-7f44b6dd87-scrf4 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-20T14:00:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 725.514µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:36:23Z" - latency: 2.33152ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:36:23Z" - latency: 791.214µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:35:23Z" - latency: 1.812448ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:35:23Z" - latency: 1.156451ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:34:23Z" - latency: 1.743344ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:34:23Z" - latency: 896.417µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:33:23Z" - latency: 1.642071ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:33:23Z" - latency: 770.141µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-20T14:32:23Z" - latency: 1.682395ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-20T14:32:23Z" kind: List metadata: resourceVersion: ""