apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11944" uid: 24c3b649-dc81-4171-98f0-d14a6d8fe8b9 spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-10-30T14:22:07Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.216229ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:22:07Z" - latency: 1.143764ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 1.08139ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 1.218926ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 1.327776ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 1.813512ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 1.000281ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:16:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11749" uid: 329685ce-18c6-4e5a-ae6b-b9d7cec985d1 spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T14:21:07Z" message: 'load-balancer-api-external: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.136944ms message: 'load-balancer-api-external: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 9.000413ms message: 'load-balancer-api-external: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:21:07Z" - latency: 15.771686ms message: 'load-balancer-api-external: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 13.302028ms message: 'load-balancer-api-external: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:20:07Z" - latency: 18.936594ms message: 'load-balancer-api-external: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 10.985854ms message: 'load-balancer-api-external: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:19:07Z" - latency: 18.002371ms message: 'load-balancer-api-external: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 9.87187ms message: 'load-balancer-api-external: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:18:07Z" - latency: 16.754612ms message: 'load-balancer-api-external: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 9.710842ms message: 'load-balancer-api-external: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:17:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11750" uid: 63dff72e-e082-4f23-b25c-b5a4f596618f spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-10-30T14:21:07Z" message: 'load-balancer-api-internal: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 16.802525ms message: 'load-balancer-api-internal: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 8.908255ms message: 'load-balancer-api-internal: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:21:07Z" - latency: 16.225783ms message: 'load-balancer-api-internal: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 13.196513ms message: 'load-balancer-api-internal: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:20:07Z" - latency: 74.703803ms message: 'load-balancer-api-internal: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 10.835689ms message: 'load-balancer-api-internal: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:19:07Z" - latency: 16.526487ms message: 'load-balancer-api-internal: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 9.694309ms message: 'load-balancer-api-internal: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:18:07Z" - latency: 17.733696ms message: 'load-balancer-api-internal: tcp connection to afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 9.733071ms message: 'load-balancer-api-internal: resolved host name afa5baf3a0bee43b78b27e672581eaa2-dddcd3586201bc15.elb.us-east-2.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-10-30T14:17:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-network-check-target-ip-10-0-134-81 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11942" uid: 53044bf1-a1c8-4a8f-8d7c-43d14e5f10ac spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T14:22:07Z" message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.265243ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:22:07Z" - latency: 2.339567ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 2.40407ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 2.484279ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 2.557263ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 2.684725ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 2.879995ms message: 'network-check-target-ip-10-0-134-81: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:16:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-network-check-target-ip-10-0-135-89 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11943" uid: a8ab8d82-9b58-467f-ab67-ea0da1a37cb5 spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-10-30T14:22:07Z" message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.224927ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:22:07Z" - latency: 2.118198ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 2.191217ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 2.216806ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 2.124173ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 2.429262ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 2.819341ms message: 'network-check-target-ip-10-0-135-89: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:16:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-network-check-target-ip-10-0-139-223 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11941" uid: 48795f9e-dc29-498f-b5e9-44282ec815f7 spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-10-30T14:22:07Z" message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 894.318µs message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:22:07Z" - latency: 930.468µs message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 933.55µs message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 1.427832ms message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 1.290582ms message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 870.719µs message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 1.333766ms message: 'network-check-target-ip-10-0-139-223: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:16:07Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-10-30T14:15:06Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-139-223-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-139-223.ec2.internal uid: 94277b11-43a3-4c71-b628-a918cc1656fc resourceVersion: "11748" uid: 486a20e7-f140-4af4-8c28-8cc9ba19f1be spec: sourcePod: network-check-source-6f78d59f99-zmj76 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-10-30T14:21:07Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.311µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:21:07Z" - latency: 1.80636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:21:07Z" - latency: 765.765µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:20:07Z" - latency: 1.781961ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:20:07Z" - latency: 1.062375ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:19:07Z" - latency: 1.846286ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:19:07Z" - latency: 853.851µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:18:07Z" - latency: 2.07758ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:18:07Z" - latency: 1.048794ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-10-30T14:17:07Z" - latency: 2.333179ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-10-30T14:17:07Z" kind: List metadata: resourceVersion: ""