apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "46335" uid: a1d55686-7dd4-4059-84a2-06433b31022d spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-05T15:46:55Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.298452ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 778.797µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 1.070587ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 1.183022ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:04:55Z" - latency: 1.283933ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:03:55Z" - latency: 983.378µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:02:55Z" - latency: 1.175735ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:01:55Z" - latency: 1.240563ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:00:55Z" - latency: 1.160607ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:59:55Z" - latency: 989.24µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:58:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "48401" uid: cb7a9b26-a5ec-4f14-91d6-cad75863532c spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T15:45:55Z" message: 'load-balancer-api-external: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.246401ms message: 'load-balancer-api-external: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:09:55Z" - latency: 7.486825ms message: 'load-balancer-api-external: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:09:55Z" - latency: 4.308538ms message: 'load-balancer-api-external: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:08:55Z" - latency: 9.478433ms message: 'load-balancer-api-external: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:08:55Z" - latency: 3.33568ms message: 'load-balancer-api-external: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 9.765273ms message: 'load-balancer-api-external: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:07:55Z" - latency: 4.709656ms message: 'load-balancer-api-external: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 9.40881ms message: 'load-balancer-api-external: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:06:55Z" - latency: 5.202613ms message: 'load-balancer-api-external: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 8.793994ms message: 'load-balancer-api-external: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:05:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "48400" uid: 62212757-fcdc-4cc1-aabd-e899fdc0f174 spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-05T15:45:55Z" message: 'load-balancer-api-internal: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 5.233809ms message: 'load-balancer-api-internal: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:09:55Z" - latency: 8.202843ms message: 'load-balancer-api-internal: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:09:55Z" - latency: 4.430917ms message: 'load-balancer-api-internal: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:08:55Z" - latency: 9.401607ms message: 'load-balancer-api-internal: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:08:55Z" - latency: 3.284037ms message: 'load-balancer-api-internal: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 9.664345ms message: 'load-balancer-api-internal: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:07:55Z" - latency: 3.837356ms message: 'load-balancer-api-internal: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 9.299541ms message: 'load-balancer-api-internal: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:06:55Z" - latency: 5.61632ms message: 'load-balancer-api-internal: tcp connection to ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 8.814875ms message: 'load-balancer-api-internal: resolved host name ac0ee68e99b204dc7905075c731475c3-61e3100800df9181.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-05T16:05:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-network-check-target-ip-10-0-128-124 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "46332" uid: 71d66f9c-c444-4f80-b96f-934dae38ab9c spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:46:55Z" message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.216293ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 1.337047ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 964.732µs message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 1.125849ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:04:55Z" - latency: 828.395µs message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:03:55Z" - latency: 1.123221ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:02:55Z" - latency: 1.226619ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:01:55Z" - latency: 866.164µs message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:00:55Z" - latency: 992.904µs message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:59:55Z" - latency: 1.773408ms message: 'network-check-target-ip-10-0-128-124: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:58:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-network-check-target-ip-10-0-129-173 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "46333" uid: e24a0549-12ca-42d3-884c-d8cf4013df55 spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: 10.134.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:46:55Z" message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.367354ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 2.006167ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 1.778228ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 1.970335ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:04:55Z" - latency: 2.060491ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:03:55Z" - latency: 2.086859ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:02:55Z" - latency: 1.78677ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:01:55Z" - latency: 2.029209ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:00:55Z" - latency: 2.078814ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:59:55Z" - latency: 2.063057ms message: 'network-check-target-ip-10-0-129-173: tcp connection to 10.134.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:58:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-network-check-target-ip-10-0-141-231 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "46334" uid: 6c16a0d2-bf4e-44f7-8b75-5debe94613da spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-05T15:46:55Z" message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.377255ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 1.837633ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 2.177281ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 2.061434ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:04:55Z" - latency: 2.122077ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:03:55Z" - latency: 2.257738ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:02:55Z" - latency: 2.042591ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:01:55Z" - latency: 2.391996ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:00:55Z" - latency: 2.092166ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:59:55Z" - latency: 2.132371ms message: 'network-check-target-ip-10-0-141-231: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-05T15:58:55Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-05T15:39:54Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-128-124-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-128-124.ec2.internal uid: bfe68585-88c2-474b-a582-bd87915e7c36 resourceVersion: "48399" uid: 4bf75e38-988d-4adb-ba78-faaa29ade7f7 spec: sourcePod: network-check-source-dbd9cf844-7djck targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-05T15:45:55Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 907.04µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:09:55Z" - latency: 1.902503ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:09:55Z" - latency: 961.645µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:08:55Z" - latency: 2.129778ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:08:55Z" - latency: 1.420209ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:07:55Z" - latency: 2.098432ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:07:55Z" - latency: 841.875µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:06:55Z" - latency: 1.608636ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:06:55Z" - latency: 870.064µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-05T16:05:55Z" - latency: 2.148064ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-05T16:05:55Z" kind: List metadata: resourceVersion: ""