apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17927" uid: 120ce4d7-56cb-454f-b379-8abb0e0129f8 spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T16:47:51Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.032673ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:54:51Z" - latency: 938.169µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:53:51Z" - latency: 948.234µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 1.402012ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 908.621µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 914.706µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 965.035µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 959.819µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:47:51Z" - latency: 1.051603ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:46:51Z" - latency: 1.011381ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:45:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17269" uid: b9a8b09a-9422-4dde-84cf-1467f7b1243b spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T16:46:51Z" message: 'load-balancer-api-external: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.437021ms message: 'load-balancer-api-external: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 8.511864ms message: 'load-balancer-api-external: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:52:51Z" - latency: 5.961606ms message: 'load-balancer-api-external: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 11.005521ms message: 'load-balancer-api-external: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:51:51Z" - latency: 7.172119ms message: 'load-balancer-api-external: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 6.680709ms message: 'load-balancer-api-external: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:50:51Z" - latency: 4.586353ms message: 'load-balancer-api-external: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 7.135535ms message: 'load-balancer-api-external: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:49:51Z" - latency: 4.458248ms message: 'load-balancer-api-external: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 7.288524ms message: 'load-balancer-api-external: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17270" uid: bea935c4-b9b0-4460-8fe8-d1be71f509ad spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T16:46:51Z" message: 'load-balancer-api-internal: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.384747ms message: 'load-balancer-api-internal: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 8.612743ms message: 'load-balancer-api-internal: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:52:51Z" - latency: 6.588723ms message: 'load-balancer-api-internal: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 10.960584ms message: 'load-balancer-api-internal: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:51:51Z" - latency: 4.948255ms message: 'load-balancer-api-internal: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 6.635153ms message: 'load-balancer-api-internal: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:50:51Z" - latency: 4.964287ms message: 'load-balancer-api-internal: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 7.080061ms message: 'load-balancer-api-internal: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:49:51Z" - latency: 5.207021ms message: 'load-balancer-api-internal: tcp connection to a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 7.259434ms message: 'load-balancer-api-internal: resolved host name a92b58de5a6e94d48990c97785ce044b-b8275c4570d73c1b.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:48:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-130-218 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17926" uid: df3b2226-e73f-4d2a-9111-1d42c2388166 spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T16:47:51Z" message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.883318ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:54:51Z" - latency: 2.335317ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:53:51Z" - latency: 2.24354ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 2.3148ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 2.299156ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 1.818891ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 2.602548ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 2.291352ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:47:51Z" - latency: 2.47454ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:46:51Z" - latency: 2.709497ms message: 'network-check-target-ip-10-0-130-218: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:45:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-134-160 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17925" uid: 92933baa-6108-497e-8717-1531182c9f77 spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-05T16:47:51Z" message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.507712ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:54:51Z" - latency: 2.35443ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:53:51Z" - latency: 2.446122ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 2.291409ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 2.333449ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 2.435917ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 2.262306ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 2.36159ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:47:51Z" - latency: 2.096509ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:46:51Z" - latency: 2.544786ms message: 'network-check-target-ip-10-0-134-160: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:45:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-143-99 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17924" uid: 35a19210-5f28-48bd-b658-a73cda3dab80 spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T16:47:51Z" message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 956.779µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:54:51Z" - latency: 1.232313ms message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:53:51Z" - latency: 867.122µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 1.158176ms message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 860.905µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 891.199µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 921.1µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 1.345985ms message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:47:51Z" - latency: 831.729µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:46:51Z" - latency: 920.909µs message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:45:51Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T16:40:49Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-99-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-99.ec2.internal uid: b1a1b71b-5a1b-4e0e-87b3-b2dfb018f10b resourceVersion: "17268" uid: 3e4fb099-2ce6-4e8b-8bcc-ad7ea4b3300c spec: sourcePod: network-check-source-dbd9cf844-8mw7r targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T16:46:51Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.040916ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:52:51Z" - latency: 1.667017ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:52:51Z" - latency: 1.117594ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:51:51Z" - latency: 1.938639ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:51:51Z" - latency: 1.043832ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:50:51Z" - latency: 1.817752ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:50:51Z" - latency: 1.150633ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:49:51Z" - latency: 1.786575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:49:51Z" - latency: 923.046µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:48:51Z" - latency: 1.916938ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:48:51Z" kind: List metadata: resourceVersion: ""