apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "44521" uid: ef4c6973-e505-4dec-8894-aa07b0a8f014 spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-14T15:25:08Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.061826ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 1.099165ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 896.371µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 930.152µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:08Z" - latency: 916.581µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:08Z" - latency: 1.286647ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:08Z" - latency: 931.524µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:08Z" - latency: 1.061338ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:08Z" - latency: 956.71µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:08Z" - latency: 1.013004ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "46538" uid: 72b7bf98-eb7d-4a07-9e9c-e6f7d3cb46d6 spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T15:24:08Z" message: 'load-balancer-api-external: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.348104ms message: 'load-balancer-api-external: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:08Z" - latency: 6.76787ms message: 'load-balancer-api-external: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:48:08Z" - latency: 3.597357ms message: 'load-balancer-api-external: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:08Z" - latency: 7.320394ms message: 'load-balancer-api-external: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:47:08Z" - latency: 3.958849ms message: 'load-balancer-api-external: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 7.269003ms message: 'load-balancer-api-external: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:46:08Z" - latency: 3.844932ms message: 'load-balancer-api-external: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 6.932933ms message: 'load-balancer-api-external: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:45:08Z" - latency: 5.587046ms message: 'load-balancer-api-external: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 7.572651ms message: 'load-balancer-api-external: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:44:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "46537" uid: 37cd957b-9986-4961-bb44-34d7c98210fc spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-14T15:24:08Z" message: 'load-balancer-api-internal: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.291779ms message: 'load-balancer-api-internal: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:08Z" - latency: 6.870191ms message: 'load-balancer-api-internal: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:48:08Z" - latency: 4.579543ms message: 'load-balancer-api-internal: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:08Z" - latency: 7.260714ms message: 'load-balancer-api-internal: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:47:08Z" - latency: 4.598088ms message: 'load-balancer-api-internal: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 7.367995ms message: 'load-balancer-api-internal: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:46:08Z" - latency: 4.854347ms message: 'load-balancer-api-internal: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 6.884091ms message: 'load-balancer-api-internal: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:45:08Z" - latency: 4.111984ms message: 'load-balancer-api-internal: tcp connection to af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 7.522967ms message: 'load-balancer-api-internal: resolved host name af774cd894c4a4d46ae7c50e5adb3068-ae3bc3881abbc7d6.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-14T15:44:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-132-152 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "44518" uid: e99a9be9-a995-47f9-8d71-032dab4ec998 spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: 10.133.0.4:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:25:08Z" message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 939.524µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 905.809µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 935.825µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 814.893µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:08Z" - latency: 896.392µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:08Z" - latency: 918.994µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:08Z" - latency: 893.917µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:08Z" - latency: 876.578µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:08Z" - latency: 848.797µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:08Z" - latency: 972.241µs message: 'network-check-target-ip-10-0-132-152: tcp connection to 10.133.0.4:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-141-194 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "44520" uid: 9632d6d2-e989-4e7a-95c7-fee524617108 spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:25:08Z" message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.316214ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 2.338639ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 2.357979ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 2.364075ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:08Z" - latency: 2.18862ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:08Z" - latency: 2.339058ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:08Z" - latency: 2.214888ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:08Z" - latency: 1.999101ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:08Z" - latency: 2.419826ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:08Z" - latency: 2.646562ms message: 'network-check-target-ip-10-0-141-194: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-network-check-target-ip-10-0-143-158 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "44519" uid: 6e14a8a7-8d13-41cb-aa64-51be38087441 spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: 10.132.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-14T15:25:08Z" message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.430106ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 2.043996ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 2.212346ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 1.914508ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:43:08Z" - latency: 1.954572ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:42:08Z" - latency: 2.679659ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:41:08Z" - latency: 2.374208ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:40:08Z" - latency: 2.415045ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:39:08Z" - latency: 2.231908ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:38:08Z" - latency: 2.196714ms message: 'network-check-target-ip-10-0-143-158: tcp connection to 10.132.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:37:08Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-14T15:18:07Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-152-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-152.ec2.internal uid: 8e37200b-c7f8-4bce-93d1-e108ed802980 resourceVersion: "46536" uid: 6b989b94-d7c5-4679-a1f5-4d0ccae370f7 spec: sourcePod: network-check-source-6947749cfc-bscx8 targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-14T15:24:08Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.091822ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:48:08Z" - latency: 1.928112ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:48:08Z" - latency: 818.946µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:47:08Z" - latency: 2.306809ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:47:08Z" - latency: 1.266108ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:46:08Z" - latency: 2.069884ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:46:08Z" - latency: 840.94µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:45:08Z" - latency: 1.720533ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:45:08Z" - latency: 745.185µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-14T15:44:08Z" - latency: 1.799708ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-14T15:44:08Z" kind: List metadata: resourceVersion: ""