apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "22346" uid: 1f6027f8-2c79-408d-8af7-1e87f28168da spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-01T17:09:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.058302ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:55Z" - latency: 1.010651ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:55Z" - latency: 995.249µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:55Z" - latency: 1.09909ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 1.526298ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 1.108465ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 1.184291ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 1.165752ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 1.257728ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:55Z" - latency: 1.123038ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "20888" uid: 8157376f-2119-4171-842c-04253e862580 spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:08:55Z" message: 'load-balancer-api-external: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.072519ms message: 'load-balancer-api-external: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 10.561365ms message: 'load-balancer-api-external: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:20:55Z" - latency: 5.846465ms message: 'load-balancer-api-external: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 9.476349ms message: 'load-balancer-api-external: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:19:55Z" - latency: 5.349204ms message: 'load-balancer-api-external: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 8.286084ms message: 'load-balancer-api-external: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:18:55Z" - latency: 5.473115ms message: 'load-balancer-api-external: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 7.11855ms message: 'load-balancer-api-external: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:17:55Z" - latency: 5.457792ms message: 'load-balancer-api-external: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 9.459434ms message: 'load-balancer-api-external: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:16:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "20887" uid: 6bb2dff6-ed8e-4fb3-8936-fae8e5d390e7 spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-01T17:08:55Z" message: 'load-balancer-api-internal: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.105331ms message: 'load-balancer-api-internal: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 10.502412ms message: 'load-balancer-api-internal: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:20:55Z" - latency: 5.011365ms message: 'load-balancer-api-internal: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 9.579322ms message: 'load-balancer-api-internal: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:19:55Z" - latency: 5.399004ms message: 'load-balancer-api-internal: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 8.483333ms message: 'load-balancer-api-internal: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:18:55Z" - latency: 5.544602ms message: 'load-balancer-api-internal: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 7.228403ms message: 'load-balancer-api-internal: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:17:55Z" - latency: 6.856257ms message: 'load-balancer-api-internal: tcp connection to af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 9.389344ms message: 'load-balancer-api-internal: resolved host name af855e8258a744982b6251e821cb9e32-6f61c9814facb9fa.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-01T17:16:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-network-check-target-ip-10-0-138-241 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "22343" uid: 36f84ede-85c5-4058-8171-b186a48df1be spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:09:55Z" message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.051291ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:55Z" - latency: 1.340473ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:55Z" - latency: 1.371716ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:55Z" - latency: 1.015202ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 1.945259ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 923.982µs message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 1.370816ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 1.499199ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 1.079741ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:55Z" - latency: 1.044127ms message: 'network-check-target-ip-10-0-138-241: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-network-check-target-ip-10-0-140-96 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "22345" uid: b57f3b5c-ccb2-4dfe-b16a-cbd9f7429b51 spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:09:55Z" message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.245893ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:55Z" - latency: 2.227826ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:55Z" - latency: 2.431378ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:55Z" - latency: 2.391522ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 2.209938ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 2.230557ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 2.195765ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 2.119829ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 1.976754ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:55Z" - latency: 2.218087ms message: 'network-check-target-ip-10-0-140-96: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-network-check-target-ip-10-0-141-111 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "22344" uid: 03c2e276-b950-40b7-81b7-5558491973ee spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-07-01T17:09:55Z" message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.113899ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:23:55Z" - latency: 2.114717ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:22:55Z" - latency: 2.127082ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:21:55Z" - latency: 1.997835ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 2.328402ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 2.025735ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 2.064884ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 2.004955ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 2.100495ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:15:55Z" - latency: 1.998249ms message: 'network-check-target-ip-10-0-141-111: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:14:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-01T17:02:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-138-241-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-138-241.ec2.internal uid: 4a3f1b4a-1e08-4a41-9abc-6d53c1ee3961 resourceVersion: "20886" uid: db05be7d-44e1-491a-b661-52420e86967e spec: sourcePod: network-check-source-56499946bc-bf599 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-01T17:08:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.144421ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:20:55Z" - latency: 1.926756ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:20:55Z" - latency: 960.097µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:19:55Z" - latency: 1.883291ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:19:55Z" - latency: 913.899µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:18:55Z" - latency: 1.811456ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:18:55Z" - latency: 1.274081ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:17:55Z" - latency: 1.695767ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:17:55Z" - latency: 1.096383ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-01T17:16:55Z" - latency: 1.853127ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-01T17:16:55Z" kind: List metadata: resourceVersion: ""