apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "37840" uid: 00d39a00-155e-4aab-b935-1893e963b051 spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-04-22T17:46:37Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 781.814µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:42:37Z" - latency: 1.123123ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:41:37Z" - latency: 962.08µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:40:37Z" - latency: 1.004653ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 1.210251ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 1.042065ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 809.719µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 1.129941ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 1.116345ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:34:37Z" - latency: 918.653µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "36619" uid: 53ff81d2-c335-4f22-84b2-52e2d209d2fb spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T17:45:37Z" message: 'load-balancer-api-external: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.228815ms message: 'load-balancer-api-external: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 6.602114ms message: 'load-balancer-api-external: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:39:37Z" - latency: 4.379962ms message: 'load-balancer-api-external: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 7.143858ms message: 'load-balancer-api-external: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:38:37Z" - latency: 4.847728ms message: 'load-balancer-api-external: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 8.016394ms message: 'load-balancer-api-external: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:37:37Z" - latency: 4.672785ms message: 'load-balancer-api-external: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 7.877333ms message: 'load-balancer-api-external: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:36:37Z" - latency: 4.886742ms message: 'load-balancer-api-external: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 8.133195ms message: 'load-balancer-api-external: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:35:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "36618" uid: 7cab6757-dfe6-4b14-9a70-01c562850d4e spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-04-22T17:45:37Z" message: 'load-balancer-api-internal: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.827176ms message: 'load-balancer-api-internal: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 6.573671ms message: 'load-balancer-api-internal: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:39:37Z" - latency: 5.275982ms message: 'load-balancer-api-internal: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 7.217715ms message: 'load-balancer-api-internal: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:38:37Z" - latency: 4.827009ms message: 'load-balancer-api-internal: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 7.991336ms message: 'load-balancer-api-internal: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:37:37Z" - latency: 4.637094ms message: 'load-balancer-api-internal: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 7.926245ms message: 'load-balancer-api-internal: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:36:37Z" - latency: 4.688793ms message: 'load-balancer-api-internal: tcp connection to a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 8.155462ms message: 'load-balancer-api-internal: resolved host name a19817953bb2f4218b67c61442f5c0d4-71ffac5d2d8d3f3d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-04-22T18:35:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-132-165 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "37838" uid: 20f46c36-6807-49ba-83a2-f7b546a60bf2 spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T17:46:37Z" message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.087969ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:42:37Z" - latency: 2.22033ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:41:37Z" - latency: 1.943735ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:40:37Z" - latency: 2.257969ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 2.198466ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 2.221362ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 2.413105ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 2.114853ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 2.403734ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:34:37Z" - latency: 2.626393ms message: 'network-check-target-ip-10-0-132-165: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-138-57 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "37839" uid: 1919ed98-436f-4a13-8e79-416466d38155 spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-04-22T17:46:37Z" message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.299167ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:42:37Z" - latency: 2.191636ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:41:37Z" - latency: 2.343237ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:40:37Z" - latency: 2.43491ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 2.361465ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 2.52565ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 2.173038ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 2.216097ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 1.93609ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:34:37Z" - latency: 2.149584ms message: 'network-check-target-ip-10-0-138-57: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-ip-10-0-143-10 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "37837" uid: df31da55-6fc0-401c-953d-e8cf5ca79da7 spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-04-22T17:46:37Z" message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 718.795µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:42:37Z" - latency: 777.739µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:41:37Z" - latency: 1.350949ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:40:37Z" - latency: 1.128646ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 943.626µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 1.305694ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 747.651µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 808.618µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 1.113098ms message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:34:37Z" - latency: 930.088µs message: 'network-check-target-ip-10-0-143-10: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:33:37Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-04-22T17:39:36Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-143-10-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-143-10.ec2.internal uid: 4d4b955d-18cb-493d-916a-753e3f341103 resourceVersion: "36617" uid: 976db53c-4f03-4ad4-b6eb-6a14835fbe36 spec: sourcePod: network-check-source-8894fc9bd-t54f6 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-04-22T17:45:37Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 910.439µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:39:37Z" - latency: 1.678723ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:39:37Z" - latency: 1.166439ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:38:37Z" - latency: 1.630243ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:38:37Z" - latency: 859.297µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:37:37Z" - latency: 1.700672ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:37:37Z" - latency: 960.387µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:36:37Z" - latency: 1.575059ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:36:37Z" - latency: 1.011386ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-04-22T18:35:37Z" - latency: 1.633578ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-04-22T18:35:37Z" kind: List metadata: resourceVersion: ""