apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "51799" uid: fd2a1749-600f-4e03-bb11-96c089857f0a spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-12T18:56:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.132433ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:24:44Z" - latency: 1.085529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:23:44Z" - latency: 782.48µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:22:44Z" - latency: 820.349µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:21:44Z" - latency: 1.095113ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:44Z" - latency: 1.011466ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 965.389µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 954.821µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 1.085864ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 847.341µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "46404" uid: 8963b9ba-e01c-4ab2-91f7-3c8c44554a79 spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:55:44Z" message: 'load-balancer-api-external: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.782835ms message: 'load-balancer-api-external: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 7.038057ms message: 'load-balancer-api-external: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:19:44Z" - latency: 4.928101ms message: 'load-balancer-api-external: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 7.584004ms message: 'load-balancer-api-external: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:18:44Z" - latency: 4.811321ms message: 'load-balancer-api-external: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 7.759491ms message: 'load-balancer-api-external: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:17:44Z" - latency: 4.055827ms message: 'load-balancer-api-external: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 7.034632ms message: 'load-balancer-api-external: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:16:44Z" - latency: 4.309942ms message: 'load-balancer-api-external: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - latency: 8.25725ms message: 'load-balancer-api-external: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:15:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "46403" uid: 44237e7a-be79-4ef4-bda1-338897a9452e spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-12T18:55:44Z" message: 'load-balancer-api-internal: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.549645ms message: 'load-balancer-api-internal: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 6.980125ms message: 'load-balancer-api-internal: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:19:44Z" - latency: 4.623216ms message: 'load-balancer-api-internal: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 7.606134ms message: 'load-balancer-api-internal: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:18:44Z" - latency: 4.801877ms message: 'load-balancer-api-internal: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 7.851169ms message: 'load-balancer-api-internal: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:17:44Z" - latency: 4.895594ms message: 'load-balancer-api-internal: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 6.935547ms message: 'load-balancer-api-internal: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:16:44Z" - latency: 3.9768ms message: 'load-balancer-api-internal: tcp connection to ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - latency: 8.309786ms message: 'load-balancer-api-internal: resolved host name ae6ae3947f38f42528fd705ae23b2f86-8ce5ea903ae30923.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-12T19:15:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-network-check-target-ip-10-0-129-145 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "51797" uid: 404ce7f8-6d4b-4bb9-824a-cbee89fc196b spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:56:44Z" message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.38295ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:24:44Z" - latency: 2.183777ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:23:44Z" - latency: 2.816536ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:22:44Z" - latency: 1.927948ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:21:44Z" - latency: 2.120254ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:44Z" - latency: 2.276324ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 2.386804ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 2.272622ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 2.234779ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 2.09314ms message: 'network-check-target-ip-10-0-129-145: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-network-check-target-ip-10-0-132-212 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "51796" uid: 89153424-8152-4730-a365-b5f7e9934f6e spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:56:44Z" message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 766.985µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:24:44Z" - latency: 926.8µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:23:44Z" - latency: 747.847µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:22:44Z" - latency: 816.206µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:21:44Z" - latency: 777.007µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:44Z" - latency: 798.805µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 718.843µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 1.375666ms message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 860.35µs message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 1.085562ms message: 'network-check-target-ip-10-0-132-212: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-network-check-target-ip-10-0-132-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "51798" uid: d9d7efc0-064e-42e3-a6cc-9dd3b9247c3a spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-12T18:56:44Z" message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.36795ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:24:44Z" - latency: 2.259955ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:23:44Z" - latency: 2.13868ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:22:44Z" - latency: 2.042651ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:21:44Z" - latency: 2.293ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:20:44Z" - latency: 2.212506ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 2.425591ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 2.394155ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 2.344618ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 2.238414ms message: 'network-check-target-ip-10-0-132-81: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-12T18:49:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-212-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-212.ec2.internal uid: 5dd9cc36-e2d8-4a91-95ac-d30e4184785b resourceVersion: "46401" uid: a589193d-81f5-4f65-8c35-a97f3edce845 spec: sourcePod: network-check-source-6947749cfc-xtks7 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-12T18:55:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 776.314µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:19:44Z" - latency: 1.59309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:19:44Z" - latency: 756.757µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:18:44Z" - latency: 2.640479ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:18:44Z" - latency: 1.002088ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:17:44Z" - latency: 1.769683ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:17:44Z" - latency: 797.593µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:16:44Z" - latency: 1.73751ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:16:44Z" - latency: 1.081036ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-12T19:15:44Z" - latency: 1.666323ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-12T19:15:44Z" kind: List metadata: resourceVersion: ""