apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63908" uid: 6af8b18a-dff9-4fac-b410-24cd1bd1e850 spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-22T01:54:23Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.292685ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 1.187504ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 1.157252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 1.23339ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 1.164599ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 1.692535ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:23Z" - latency: 825.933µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:23Z" - latency: 908.38µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:23Z" - latency: 968.873µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:23Z" - latency: 1.066435ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63910" uid: 5af4f1ea-4876-4e15-b922-ffe593a0f3e3 spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:53:23Z" message: 'load-balancer-api-external: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.76903ms message: 'load-balancer-api-external: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 7.479383ms message: 'load-balancer-api-external: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:29:23Z" - latency: 6.003156ms message: 'load-balancer-api-external: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 7.905311ms message: 'load-balancer-api-external: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:28:23Z" - latency: 4.165432ms message: 'load-balancer-api-external: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 7.181671ms message: 'load-balancer-api-external: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:27:23Z" - latency: 4.89652ms message: 'load-balancer-api-external: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 7.074703ms message: 'load-balancer-api-external: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:26:23Z" - latency: 4.357628ms message: 'load-balancer-api-external: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 7.194138ms message: 'load-balancer-api-external: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:25:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63909" uid: be2e43d0-842e-4b94-ad16-9da51b97a998 spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-22T01:53:23Z" message: 'load-balancer-api-internal: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.741013ms message: 'load-balancer-api-internal: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 7.504312ms message: 'load-balancer-api-internal: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:29:23Z" - latency: 4.782997ms message: 'load-balancer-api-internal: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 7.94501ms message: 'load-balancer-api-internal: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:28:23Z" - latency: 4.943195ms message: 'load-balancer-api-internal: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 7.206902ms message: 'load-balancer-api-internal: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:27:23Z" - latency: 5.67872ms message: 'load-balancer-api-internal: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 7.087458ms message: 'load-balancer-api-internal: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:26:23Z" - latency: 4.371725ms message: 'load-balancer-api-internal: tcp connection to ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 7.211591ms message: 'load-balancer-api-internal: resolved host name ae829fff24d2d4d779ad5fd7613fffb2-5d3725efa87489dd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-22T02:25:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-ip-10-0-130-189 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63906" uid: 3640e9a7-6431-42c8-8c3b-63962e8a496a spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:54:23Z" message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.095625ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 2.361153ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 2.291585ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 2.230819ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 2.110878ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 2.291954ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:23Z" - latency: 1.954755ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:23Z" - latency: 2.125037ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:23Z" - latency: 2.367112ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:23Z" - latency: 2.196787ms message: 'network-check-target-ip-10-0-130-189: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-ip-10-0-133-122 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63905" uid: 4264381e-5c2d-4be6-a9d8-2f0c864331dc spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:54:23Z" message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.789111ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 2.054906ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 1.982394ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 2.099804ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 1.844374ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 2.069494ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:23Z" - latency: 1.850661ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:23Z" - latency: 1.86422ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:23Z" - latency: 2.060788ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:23Z" - latency: 1.929082ms message: 'network-check-target-ip-10-0-133-122: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-ip-10-0-141-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63904" uid: 3f58483d-a443-4b0b-a3c9-43ac9af89acb spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-07-22T01:54:23Z" message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.480695ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 871.108µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 923.999µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 1.171393ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 1.000842ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 1.073791ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:24:23Z" - latency: 903.702µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:23:23Z" - latency: 1.321563ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:22:23Z" - latency: 949.143µs message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:21:23Z" - latency: 1.340178ms message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:20:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-22T01:47:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-141-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-141-12.ec2.internal uid: 3ef4ce26-9179-4c2c-beec-2ee5e9cdad8d resourceVersion: "63907" uid: d62f3c31-0d1f-4fc5-9729-2532b298877a spec: sourcePod: network-check-source-7bc5b6bf85-c8phr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-22T01:53:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 996.866µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:29:23Z" - latency: 1.986598ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:29:23Z" - latency: 895.596µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:28:23Z" - latency: 2.152995ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:28:23Z" - latency: 979.094µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:27:23Z" - latency: 1.882862ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:27:23Z" - latency: 945.461µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:26:23Z" - latency: 2.128449ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:26:23Z" - latency: 1.115209ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-22T02:25:23Z" - latency: 1.691439ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-22T02:25:23Z" kind: List metadata: resourceVersion: ""