apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "46173" uid: b58bf9a5-95ab-4032-a39c-fc805beb7526 spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-06-13T02:13:44Z" message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.09138ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 1.025922ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 1.254559ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 1.087312ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:31:44Z" - latency: 907.017µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:30:44Z" - latency: 1.058332ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:29:44Z" - latency: 948.102µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:28:44Z" - latency: 1.041109ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:27:44Z" - latency: 1.179715ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:26:44Z" - latency: 1.296472ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "48234" uid: 594ed79d-0c4b-47e4-955e-f04fd1600b42 spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T02:12:44Z" message: 'load-balancer-api-external: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.223264ms message: 'load-balancer-api-external: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:36:44Z" - latency: 6.98657ms message: 'load-balancer-api-external: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:36:44Z" - latency: 4.114135ms message: 'load-balancer-api-external: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:35:44Z" - latency: 9.690764ms message: 'load-balancer-api-external: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:35:44Z" - latency: 5.631626ms message: 'load-balancer-api-external: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 9.006968ms message: 'load-balancer-api-external: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:34:44Z" - latency: 5.176133ms message: 'load-balancer-api-external: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 7.450761ms message: 'load-balancer-api-external: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:33:44Z" - latency: 4.865695ms message: 'load-balancer-api-external: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 9.624807ms message: 'load-balancer-api-external: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:32:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "48235" uid: 5c34f8c5-73f4-471e-bf5e-3c5de0f279a7 spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-06-13T02:12:44Z" message: 'load-balancer-api-internal: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.170746ms message: 'load-balancer-api-internal: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:36:44Z" - latency: 7.043339ms message: 'load-balancer-api-internal: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:36:44Z" - latency: 3.27465ms message: 'load-balancer-api-internal: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:35:44Z" - latency: 9.72991ms message: 'load-balancer-api-internal: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:35:44Z" - latency: 5.582741ms message: 'load-balancer-api-internal: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 8.942919ms message: 'load-balancer-api-internal: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:34:44Z" - latency: 4.167937ms message: 'load-balancer-api-internal: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 7.522538ms message: 'load-balancer-api-internal: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:33:44Z" - latency: 5.177124ms message: 'load-balancer-api-internal: tcp connection to a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 9.575535ms message: 'load-balancer-api-internal: resolved host name a69510f41c0634c08890b5fd4f587a5c-bc8596ecbf39ff6d.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-06-13T02:32:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-ip-10-0-132-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "46170" uid: 547f659d-420e-44d2-9a9f-daa72bd277aa spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-13T02:13:44Z" message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.095108ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 1.448219ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 976.693µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 1.129282ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:31:44Z" - latency: 901.704µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:30:44Z" - latency: 918.696µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:29:44Z" - latency: 855.38µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:28:44Z" - latency: 1.372888ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:27:44Z" - latency: 825.574µs message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:26:44Z" - latency: 1.10274ms message: 'network-check-target-ip-10-0-132-107: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-ip-10-0-134-133 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "46172" uid: 158e0ece-a094-475e-b769-2893b80e2186 spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-06-13T02:13:44Z" message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.365234ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 2.332355ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 2.403538ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 2.142516ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:31:44Z" - latency: 1.985567ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:30:44Z" - latency: 2.334619ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:29:44Z" - latency: 2.351005ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:28:44Z" - latency: 2.246217ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:27:44Z" - latency: 2.263873ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:26:44Z" - latency: 2.218516ms message: 'network-check-target-ip-10-0-134-133: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-ip-10-0-141-22 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "46171" uid: ee2fc7de-6c34-4ec1-ac67-655ef8af9843 spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: 10.133.0.3:8080 status: conditions: - lastTransitionTime: "2026-06-13T02:13:44Z" message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.597181ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 2.33065ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 2.467235ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 2.398258ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:31:44Z" - latency: 2.004733ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:30:44Z" - latency: 2.413345ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:29:44Z" - latency: 2.351807ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:28:44Z" - latency: 2.324276ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:27:44Z" - latency: 2.714144ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:26:44Z" - latency: 2.076734ms message: 'network-check-target-ip-10-0-141-22: tcp connection to 10.133.0.3:8080 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:25:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-06-13T02:06:42Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-107-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-107.ec2.internal uid: 2205533c-c8d1-4dc0-b112-7eb293182d46 resourceVersion: "48233" uid: 6e472e0b-c00b-4954-9629-75a712f4f507 spec: sourcePod: network-check-source-6947749cfc-grbvr targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-06-13T02:12:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 767.48µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:36:44Z" - latency: 1.721931ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T02:36:44Z" - latency: 868.054µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:35:44Z" - latency: 1.73885ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T02:35:44Z" - latency: 732.095µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:34:44Z" - latency: 2.519886ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T02:34:44Z" - latency: 891.591µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:33:44Z" - latency: 1.996378ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T02:33:44Z" - latency: 950.018µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-06-13T02:32:44Z" - latency: 1.831821ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-06-13T02:32:44Z" kind: List metadata: resourceVersion: ""