apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "27818" uid: 89bcfc41-efa5-4a7f-b778-7977fb05191a spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-05-21T11:43:25Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.291352ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 986.261µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:49:25Z" - latency: 1.082325ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:48:25Z" - latency: 1.252245ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:47:25Z" - latency: 906.913µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:46:25Z" - latency: 1.031058ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:45:25Z" - latency: 1.065529ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:44:25Z" - latency: 724.064µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:43:25Z" - latency: 1.219887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:42:25Z" - latency: 853.733µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:41:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "31895" uid: 13866c78-f6ef-4430-99cc-138516e0770b spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T11:42:25Z" message: 'load-balancer-api-external: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.348367ms message: 'load-balancer-api-external: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:54:25Z" - latency: 7.028311ms message: 'load-balancer-api-external: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:54:25Z" - latency: 5.138521ms message: 'load-balancer-api-external: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:53:25Z" - latency: 7.555379ms message: 'load-balancer-api-external: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:53:25Z" - latency: 3.436324ms message: 'load-balancer-api-external: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:52:25Z" - latency: 6.898829ms message: 'load-balancer-api-external: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:52:25Z" - latency: 4.911152ms message: 'load-balancer-api-external: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:51:25Z" - latency: 6.54703ms message: 'load-balancer-api-external: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:51:25Z" - latency: 5.409307ms message: 'load-balancer-api-external: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 6.941024ms message: 'load-balancer-api-external: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:50:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "31894" uid: 3a523a4f-9f1b-4e69-a497-e12c7a8efc4d spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-05-21T11:42:25Z" message: 'load-balancer-api-internal: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.036727ms message: 'load-balancer-api-internal: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:54:25Z" - latency: 6.922124ms message: 'load-balancer-api-internal: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:54:25Z" - latency: 3.372662ms message: 'load-balancer-api-internal: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:53:25Z" - latency: 7.634563ms message: 'load-balancer-api-internal: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:53:25Z" - latency: 4.331182ms message: 'load-balancer-api-internal: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:52:25Z" - latency: 6.963165ms message: 'load-balancer-api-internal: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:52:25Z" - latency: 4.930742ms message: 'load-balancer-api-internal: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:51:25Z" - latency: 7.431936ms message: 'load-balancer-api-internal: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:51:25Z" - latency: 5.377654ms message: 'load-balancer-api-internal: tcp connection to a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 6.72772ms message: 'load-balancer-api-internal: resolved host name a148dd3d041544c53ae054e65d0f64d8-6ab7ca56d48c0657.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-05-21T11:50:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-network-check-target-ip-10-0-139-18 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "27817" uid: cdb686af-997a-4cb2-88e8-c3ff40ac22fb spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T11:43:25Z" message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.150398ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 2.065499ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:49:25Z" - latency: 2.150018ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:48:25Z" - latency: 2.481128ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:47:25Z" - latency: 2.171127ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:46:25Z" - latency: 2.286747ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:45:25Z" - latency: 2.362296ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:44:25Z" - latency: 2.208587ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:43:25Z" - latency: 2.177455ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:42:25Z" - latency: 2.212891ms message: 'network-check-target-ip-10-0-139-18: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:41:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-network-check-target-ip-10-0-139-213 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "27816" uid: 965d4906-1460-4200-8578-fd8219453cd5 spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: 10.134.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T11:43:25Z" message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.525182ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 2.280601ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:49:25Z" - latency: 2.291839ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:48:25Z" - latency: 2.319645ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:47:25Z" - latency: 2.383604ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:46:25Z" - latency: 2.613105ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:45:25Z" - latency: 2.212129ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:44:25Z" - latency: 1.593942ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:43:25Z" - latency: 2.399287ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:42:25Z" - latency: 2.290155ms message: 'network-check-target-ip-10-0-139-213: tcp connection to 10.134.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:41:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-network-check-target-ip-10-0-143-50 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "27815" uid: f54cc661-8a2b-4e51-8425-2b50c451d3e6 spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-05-21T11:43:25Z" message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 999.293µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 905.362µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:49:25Z" - latency: 915.062µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:48:25Z" - latency: 865.012µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:47:25Z" - latency: 977.205µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:46:25Z" - latency: 1.116684ms message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:45:25Z" - latency: 1.388519ms message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:44:25Z" - latency: 730.271µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:43:25Z" - latency: 939.957µs message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:42:25Z" - latency: 1.488828ms message: 'network-check-target-ip-10-0-143-50: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:41:25Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-05-21T11:36:24Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-50-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-50.ec2.internal uid: c794471f-1a4f-465e-85c8-b3e0ad7b7393 resourceVersion: "31893" uid: 826e0b1f-fa9a-4036-a954-f77aeb17ab7d spec: sourcePod: network-check-source-7f44b6dd87-bzj74 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-05-21T11:42:25Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.054416ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:54:25Z" - latency: 2.012964ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:54:25Z" - latency: 964.975µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:53:25Z" - latency: 1.727573ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:53:25Z" - latency: 963.19µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:52:25Z" - latency: 1.720575ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:52:25Z" - latency: 917.97µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:51:25Z" - latency: 2.115603ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:51:25Z" - latency: 957.712µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-05-21T11:50:25Z" - latency: 1.597944ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-05-21T11:50:25Z" kind: List metadata: resourceVersion: ""