apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "66278" uid: 639222ee-76eb-44dd-afb3-d95c70219cf8 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-07T02:32:57Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 976.46µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:21:57Z" - latency: 1.039554ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:20:57Z" - latency: 1.017856ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 835.081µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 1.275665ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 1.473484ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 997.936µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 994.676µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:14:57Z" - latency: 954.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:13:57Z" - latency: 1.815274ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "64159" uid: 857ec63d-6691-4462-8d6f-0970894deff0 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:31:57Z" message: 'load-balancer-api-external: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.779874ms message: 'load-balancer-api-external: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 6.675241ms message: 'load-balancer-api-external: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:19:57Z" - latency: 4.436503ms message: 'load-balancer-api-external: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 7.098091ms message: 'load-balancer-api-external: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:18:57Z" - latency: 5.487604ms message: 'load-balancer-api-external: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 7.64844ms message: 'load-balancer-api-external: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:17:57Z" - latency: 4.305645ms message: 'load-balancer-api-external: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 6.407853ms message: 'load-balancer-api-external: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:16:57Z" - latency: 5.108536ms message: 'load-balancer-api-external: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 6.984912ms message: 'load-balancer-api-external: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:15:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "64160" uid: 82113386-9d88-4885-90d8-223197f6a997 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-07T02:31:57Z" message: 'load-balancer-api-internal: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.057658ms message: 'load-balancer-api-internal: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 7.472833ms message: 'load-balancer-api-internal: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:19:57Z" - latency: 4.416648ms message: 'load-balancer-api-internal: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 6.986523ms message: 'load-balancer-api-internal: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:18:57Z" - latency: 5.428708ms message: 'load-balancer-api-internal: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 7.667476ms message: 'load-balancer-api-internal: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:17:57Z" - latency: 4.291181ms message: 'load-balancer-api-internal: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 6.448901ms message: 'load-balancer-api-internal: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:16:57Z" - latency: 4.899024ms message: 'load-balancer-api-internal: tcp connection to aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 6.936052ms message: 'load-balancer-api-internal: resolved host name aaa6d4dabbf134f90924ab6644b2a3ce-5f1af375808b06ca.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-07T03:15:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-ip-10-0-132-101 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "66275" uid: 7ed09f75-aadb-455a-ba17-8e1ca4f96bb8 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:32:57Z" message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 864.94µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:21:57Z" - latency: 1.431591ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:20:57Z" - latency: 1.068401ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 967.052µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 1.249535ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 1.136826ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 796.552µs message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 1.092968ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:14:57Z" - latency: 1.737403ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:13:57Z" - latency: 1.838138ms message: 'network-check-target-ip-10-0-132-101: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-ip-10-0-137-109 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "66277" uid: 1c5fe588-3d03-45ac-b70b-1f5bbd8094e3 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:32:57Z" message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.308729ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:21:57Z" - latency: 2.639873ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:20:57Z" - latency: 1.68605ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 2.342308ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 2.072996ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 2.754829ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 2.337047ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 2.267005ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:14:57Z" - latency: 2.235084ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:13:57Z" - latency: 2.583645ms message: 'network-check-target-ip-10-0-137-109: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-ip-10-0-141-229 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "66276" uid: f0c32cf1-d71f-43bc-ba81-db697ebb1776 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-07T02:32:57Z" message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.930712ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:21:57Z" - latency: 1.702809ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:20:57Z" - latency: 2.144219ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 1.798177ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 1.984272ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 1.965318ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 1.798561ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 2.066269ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:14:57Z" - latency: 2.717726ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:13:57Z" - latency: 2.201284ms message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:12:57Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-07T02:25:56Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-101-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-101.ec2.internal uid: 169033ee-3292-4a0d-a269-62a51f95fcd8 resourceVersion: "64158" uid: f343438d-c87a-4eb9-a2e1-411b441872c5 spec: sourcePod: network-check-source-989f8b8dc-wpspw targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-07T02:31:57Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 941.334µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:19:57Z" - latency: 2.286231ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:19:57Z" - latency: 1.191023ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:18:57Z" - latency: 1.756938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:18:57Z" - latency: 953.734µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:17:57Z" - latency: 1.870503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:17:57Z" - latency: 926.155µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:16:57Z" - latency: 1.94502ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:16:57Z" - latency: 1.163518ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-07T03:15:57Z" - latency: 2.050041ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-07T03:15:57Z" kind: List metadata: resourceVersion: ""