apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "46140" uid: 32392b29-8dc5-435b-a461-bf8e7a1b95c2 spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-02T04:55:36Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 958.662µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 953.849µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 1.10502ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 839.541µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:36Z" - latency: 1.075036ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:36Z" - latency: 835.465µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:36Z" - latency: 1.003043ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:36Z" - latency: 951.433µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:36Z" - latency: 1.461063ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:36Z" - latency: 1.03498ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "48415" uid: 91394aa4-33e3-4cd2-acce-eb72f14d9546 spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T04:54:36Z" message: 'load-balancer-api-external: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.518878ms message: 'load-balancer-api-external: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:18:36Z" - latency: 8.440486ms message: 'load-balancer-api-external: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:18:36Z" - latency: 4.735164ms message: 'load-balancer-api-external: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:17:36Z" - latency: 8.081935ms message: 'load-balancer-api-external: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:17:36Z" - latency: 3.587042ms message: 'load-balancer-api-external: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 8.201425ms message: 'load-balancer-api-external: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:16:36Z" - latency: 4.411288ms message: 'load-balancer-api-external: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 14.130294ms message: 'load-balancer-api-external: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:15:36Z" - latency: 4.212698ms message: 'load-balancer-api-external: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 8.218257ms message: 'load-balancer-api-external: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:14:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "48414" uid: 54e2ffeb-4521-4508-a225-3dc47824f048 spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-02T04:54:36Z" message: 'load-balancer-api-internal: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.301256ms message: 'load-balancer-api-internal: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:18:36Z" - latency: 8.497071ms message: 'load-balancer-api-internal: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:18:36Z" - latency: 4.702185ms message: 'load-balancer-api-internal: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:17:36Z" - latency: 8.159653ms message: 'load-balancer-api-internal: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:17:36Z" - latency: 3.549528ms message: 'load-balancer-api-internal: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 8.307092ms message: 'load-balancer-api-internal: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:16:36Z" - latency: 4.140519ms message: 'load-balancer-api-internal: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 14.229202ms message: 'load-balancer-api-internal: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:15:36Z" - latency: 4.206766ms message: 'load-balancer-api-internal: tcp connection to adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 8.36947ms message: 'load-balancer-api-internal: resolved host name adede5b7eb2f84d9a9b0ae6d3d517ce8-2fd16d78db16b650.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-02T05:14:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-129-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "46138" uid: 833900f1-e4cb-4ef5-b686-efd86f9bbbdf spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T04:55:36Z" message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.945161ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 2.242842ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 2.24164ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 1.928411ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:36Z" - latency: 2.332561ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:36Z" - latency: 2.22576ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:36Z" - latency: 2.447342ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:36Z" - latency: 2.32991ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:36Z" - latency: 1.938173ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:36Z" - latency: 2.19827ms message: 'network-check-target-ip-10-0-129-50: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-132-27 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "46137" uid: dc8af9c0-0618-4ba9-aba9-9b2715437fa0 spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-02T04:55:36Z" message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 839.188µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 1.368071ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 810.217µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 820.191µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:36Z" - latency: 846.611µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:36Z" - latency: 1.152631ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:36Z" - latency: 795.175µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:36Z" - latency: 934.598µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:36Z" - latency: 791.838µs message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:36Z" - latency: 1.078245ms message: 'network-check-target-ip-10-0-132-27: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-ip-10-0-135-23 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "46139" uid: b95dd76c-355c-4fdf-b80a-81c52ac5ece5 spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-02T04:55:36Z" message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.207391ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 2.222937ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 1.88229ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 1.693311ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:13:36Z" - latency: 2.495274ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:12:36Z" - latency: 2.052436ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:11:36Z" - latency: 1.993074ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:10:36Z" - latency: 2.050161ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:09:36Z" - latency: 2.572335ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:08:36Z" - latency: 2.145802ms message: 'network-check-target-ip-10-0-135-23: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:07:36Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-02T04:48:35Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-27-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-27.ec2.internal uid: c1a21b22-34f1-4395-af90-fe949ec74b09 resourceVersion: "48411" uid: a750f8da-e60d-42ff-8ef9-7d2f261273ce spec: sourcePod: network-check-source-56d84b9f44-qk27w targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-02T04:54:36Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 829.46µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:18:36Z" - latency: 2.147032ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:18:36Z" - latency: 792.682µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:17:36Z" - latency: 1.567604ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:17:36Z" - latency: 1.128661ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:16:36Z" - latency: 1.727246ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:16:36Z" - latency: 779.807µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:15:36Z" - latency: 1.516977ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:15:36Z" - latency: 976.174µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-02T05:14:36Z" - latency: 1.771249ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-02T05:14:36Z" kind: List metadata: resourceVersion: ""