apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "36421" uid: fecab7e7-8dad-4084-aabd-5563a6f384da spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-16T16:40:19Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.089526ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:22:19Z" - latency: 1.048129ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:21:19Z" - latency: 1.442645ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:19Z" - latency: 986.274µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:19Z" - latency: 1.371238ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:19Z" - latency: 1.364252ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:19Z" - latency: 843.049µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:19Z" - latency: 1.03724ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:19Z" - latency: 962.783µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:19Z" - latency: 1.022386ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "39064" uid: 80f812be-21e8-45fb-8873-dec256529e37 spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:39:19Z" message: 'load-balancer-api-external: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.571864ms message: 'load-balancer-api-external: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:27:19Z" - latency: 8.262596ms message: 'load-balancer-api-external: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:27:19Z" - latency: 4.607886ms message: 'load-balancer-api-external: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:26:19Z" - latency: 7.93684ms message: 'load-balancer-api-external: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:26:19Z" - latency: 4.372901ms message: 'load-balancer-api-external: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:25:19Z" - latency: 7.232061ms message: 'load-balancer-api-external: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:25:19Z" - latency: 4.084967ms message: 'load-balancer-api-external: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:24:19Z" - latency: 7.641734ms message: 'load-balancer-api-external: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:24:19Z" - latency: 5.454949ms message: 'load-balancer-api-external: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:23:19Z" - latency: 7.982578ms message: 'load-balancer-api-external: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:23:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "39063" uid: 8393ae01-006c-41d2-83ec-6023bfe35392 spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-16T16:39:19Z" message: 'load-balancer-api-internal: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.628621ms message: 'load-balancer-api-internal: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:27:19Z" - latency: 8.227048ms message: 'load-balancer-api-internal: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:27:19Z" - latency: 4.573954ms message: 'load-balancer-api-internal: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:26:19Z" - latency: 7.963704ms message: 'load-balancer-api-internal: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:26:19Z" - latency: 4.410513ms message: 'load-balancer-api-internal: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:25:19Z" - latency: 7.20393ms message: 'load-balancer-api-internal: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:25:19Z" - latency: 4.108191ms message: 'load-balancer-api-internal: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:24:19Z" - latency: 7.67735ms message: 'load-balancer-api-internal: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:24:19Z" - latency: 4.602349ms message: 'load-balancer-api-internal: tcp connection to a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:23:19Z" - latency: 8.057098ms message: 'load-balancer-api-internal: resolved host name a6f839fea3efb4b78b40f19f3584922a-e0ca3e4d20d77ca1.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-16T17:23:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-network-check-target-ip-10-0-132-191 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "36420" uid: 66bfee1e-8e93-4240-8ca4-84f873c67bf7 spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:40:19Z" message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.136539ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:22:19Z" - latency: 2.146258ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:21:19Z" - latency: 2.189311ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:19Z" - latency: 2.038452ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:19Z" - latency: 2.162528ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:19Z" - latency: 2.066831ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:19Z" - latency: 2.101365ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:19Z" - latency: 2.373879ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:19Z" - latency: 2.191543ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:19Z" - latency: 2.135991ms message: 'network-check-target-ip-10-0-132-191: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-network-check-target-ip-10-0-139-12 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "36418" uid: 6a59c742-5fb6-4c9a-a297-7d28f1ec53c4 spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:40:19Z" message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.360262ms message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:22:19Z" - latency: 875.948µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:21:19Z" - latency: 1.828826ms message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:19Z" - latency: 1.146658ms message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:19Z" - latency: 798.834µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:19Z" - latency: 839.583µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:19Z" - latency: 955.761µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:19Z" - latency: 847.68µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:19Z" - latency: 910.486µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:19Z" - latency: 799.337µs message: 'network-check-target-ip-10-0-139-12: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-network-check-target-ip-10-0-140-164 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "36419" uid: 14c0c185-2188-4918-a955-e61b3c5f91f8 spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-16T16:40:19Z" message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.756603ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:22:19Z" - latency: 1.844979ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:21:19Z" - latency: 2.576337ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:20:19Z" - latency: 2.246097ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:19:19Z" - latency: 1.936781ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:18:19Z" - latency: 1.826051ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:17:19Z" - latency: 1.985548ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:16:19Z" - latency: 1.795833ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:15:19Z" - latency: 1.952553ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:14:19Z" - latency: 1.804552ms message: 'network-check-target-ip-10-0-140-164: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:13:19Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-16T16:33:18Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-12-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-12.ec2.internal uid: 2fec6e81-e297-400a-9136-e99da500639f resourceVersion: "39061" uid: cce9a974-a360-4682-845a-c8ffd8da9444 spec: sourcePod: network-check-source-7b678d77c7-zrwnz targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-16T16:39:19Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 771.002µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:27:19Z" - latency: 1.774182ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:27:19Z" - latency: 1.059195ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:26:19Z" - latency: 1.507086ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:26:19Z" - latency: 1.022786ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:25:19Z" - latency: 1.57651ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:25:19Z" - latency: 790.426µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:24:19Z" - latency: 1.593961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:24:19Z" - latency: 817.354µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-16T17:23:19Z" - latency: 1.8539ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-16T17:23:19Z" kind: List metadata: resourceVersion: ""