apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "44540" uid: ee28815b-b71a-4b19-a5c0-eda1f80a17c1 spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-15T07:58: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.205337ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 1.15565ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 1.187866ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 1.127426ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:16:23Z" - latency: 934.53µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:15:23Z" - latency: 1.066171ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:14:23Z" - latency: 1.003348ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:13:23Z" - latency: 709.947µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:12:23Z" - latency: 1.132367ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:11:23Z" - latency: 1.112863ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:10:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "47073" uid: 4c19d363-f7c0-422f-b4bf-47ff8af78d4a spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T07:57:23Z" message: 'load-balancer-api-external: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.186696ms message: 'load-balancer-api-external: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:21:23Z" - latency: 9.388385ms message: 'load-balancer-api-external: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:21:23Z" - latency: 4.909051ms message: 'load-balancer-api-external: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:20:23Z" - latency: 8.244604ms message: 'load-balancer-api-external: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:20:23Z" - latency: 3.944083ms message: 'load-balancer-api-external: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 8.500857ms message: 'load-balancer-api-external: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:19:23Z" - latency: 4.603603ms message: 'load-balancer-api-external: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 7.6576ms message: 'load-balancer-api-external: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:18:23Z" - latency: 4.412721ms message: 'load-balancer-api-external: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 8.166115ms message: 'load-balancer-api-external: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:17:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "47074" uid: 7b69f9fd-1307-4e16-85c3-0ef0007f5165 spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-15T07:57:23Z" message: 'load-balancer-api-internal: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 6.5507ms message: 'load-balancer-api-internal: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:21:23Z" - latency: 9.36052ms message: 'load-balancer-api-internal: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:21:23Z" - latency: 5.849851ms message: 'load-balancer-api-internal: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:20:23Z" - latency: 8.209146ms message: 'load-balancer-api-internal: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:20:23Z" - latency: 4.012965ms message: 'load-balancer-api-internal: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 8.531029ms message: 'load-balancer-api-internal: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:19:23Z" - latency: 4.584911ms message: 'load-balancer-api-internal: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 7.626635ms message: 'load-balancer-api-internal: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:18:23Z" - latency: 3.892259ms message: 'load-balancer-api-internal: tcp connection to a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 8.12917ms message: 'load-balancer-api-internal: resolved host name a7e2632b5b47a4bf08fd48b1844bdc42-b03b3f5974719099.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-15T08:17:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-network-check-target-ip-10-0-137-217 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "44541" uid: 9e15eb61-2d10-46e8-ba20-1ad0422a791c spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T07:58:23Z" message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 14.596761ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 2.22892ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 1.959547ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 2.170403ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:16:23Z" - latency: 1.8668ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:15:23Z" - latency: 2.157644ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:14:23Z" - latency: 2.29356ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:13:23Z" - latency: 2.045088ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:12:23Z" - latency: 2.046882ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:11:23Z" - latency: 2.005074ms message: 'network-check-target-ip-10-0-137-217: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:10:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-network-check-target-ip-10-0-139-233 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "44538" uid: 94ca548c-6c54-453d-a5b8-6098d3a16399 spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: 10.132.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-15T07:58:23Z" message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 760.539µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 793.937µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 901.765µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 781.829µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:16:23Z" - latency: 800.836µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:15:23Z" - latency: 860.409µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:14:23Z" - latency: 1.260008ms message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:13:23Z" - latency: 1.223465ms message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:12:23Z" - latency: 773.374µs message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:11:23Z" - latency: 1.319945ms message: 'network-check-target-ip-10-0-139-233: tcp connection to 10.132.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:10:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-network-check-target-ip-10-0-143-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "44539" uid: d281efea-4b09-47fa-b269-9193eaad61c2 spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-15T07:58:23Z" message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.017462ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 1.781276ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 1.670505ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 1.703238ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:16:23Z" - latency: 1.845988ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:15:23Z" - latency: 1.774439ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:14:23Z" - latency: 2.095711ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:13:23Z" - latency: 1.536877ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:12:23Z" - latency: 1.939035ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:11:23Z" - latency: 1.975847ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:10:23Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-15T07:51:22Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-233-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-233.ec2.internal uid: 47b50ae8-6587-43a2-b7b2-6bd051b3a2ab resourceVersion: "47072" uid: ae0cfe00-2e3d-4f93-b591-97975415973e spec: sourcePod: network-check-source-6947749cfc-47vbr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-15T07:57:23Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 855.06µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:21:23Z" - latency: 2.274718ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T08:21:23Z" - latency: 858.057µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:20:23Z" - latency: 1.868055ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T08:20:23Z" - latency: 1.131795ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:19:23Z" - latency: 1.812697ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T08:19:23Z" - latency: 951.728µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:18:23Z" - latency: 1.944792ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T08:18:23Z" - latency: 721.282µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-15T08:17:23Z" - latency: 1.991494ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-15T08:17:23Z" kind: List metadata: resourceVersion: ""