apiVersion: v1 items: - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-kubernetes-default-service-cluster-0 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "53816" uid: 585df5d0-b31e-4dae-95fa-103d45fa05d5 spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: 172.31.0.1:443 status: conditions: - lastTransitionTime: "2026-07-08T02:53: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.130327ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 1.09176ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 1.154231ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 1.257887ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 904.995µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:17:44Z" - latency: 962.509µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:16:44Z" - latency: 884.683µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:15:44Z" - latency: 864.813µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:14:44Z" - latency: 1.330434ms message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:13:44Z" - latency: 708.722µs message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-load-balancer-api-external namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "55678" uid: bec2d6dd-4690-4fb6-9ad2-30afce56a802 spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T02:52:44Z" message: 'load-balancer-api-external: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.780764ms message: 'load-balancer-api-external: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:22:44Z" - latency: 6.335688ms message: 'load-balancer-api-external: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:22:44Z" - latency: 5.111827ms message: 'load-balancer-api-external: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 7.693676ms message: 'load-balancer-api-external: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:21:44Z" - latency: 4.850718ms message: 'load-balancer-api-external: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 7.138013ms message: 'load-balancer-api-external: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:20:44Z" - latency: 4.283232ms message: 'load-balancer-api-external: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 8.393571ms message: 'load-balancer-api-external: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:19:44Z" - latency: 5.125525ms message: 'load-balancer-api-external: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 6.095711ms message: 'load-balancer-api-external: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:18:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-load-balancer-api-internal namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "55677" uid: 89dbfabd-eb2a-4f1a-af39-0b982734b267 spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 status: conditions: - lastTransitionTime: "2026-07-08T02:52:44Z" message: 'load-balancer-api-internal: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 4.813568ms message: 'load-balancer-api-internal: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:22:44Z" - latency: 6.225174ms message: 'load-balancer-api-internal: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:22:44Z" - latency: 5.139386ms message: 'load-balancer-api-internal: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 7.61506ms message: 'load-balancer-api-internal: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:21:44Z" - latency: 4.847ms message: 'load-balancer-api-internal: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 7.214041ms message: 'load-balancer-api-internal: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:20:44Z" - latency: 4.294353ms message: 'load-balancer-api-internal: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 8.436368ms message: 'load-balancer-api-internal: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:19:44Z" - latency: 5.112453ms message: 'load-balancer-api-internal: tcp connection to a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com:6443 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 6.072226ms message: 'load-balancer-api-internal: resolved host name a4536e496c57f484fb86c43d48887d39-dd8d149628a69fcd.elb.us-east-1.amazonaws.com successfully' reason: DNSResolve success: true time: "2026-07-08T03:18:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-ip-10-0-128-107 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "53813" uid: 40faa447-b44d-4304-9cb7-02a476f86ac7 spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: 10.133.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T02:53:44Z" message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.938617ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 2.07791ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 2.26699ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 2.124686ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 1.885741ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:17:44Z" - latency: 1.913204ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:16:44Z" - latency: 1.815469ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:15:44Z" - latency: 1.82443ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:14:44Z" - latency: 1.961928ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:13:44Z" - latency: 1.755134ms message: 'network-check-target-ip-10-0-128-107: tcp connection to 10.133.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-ip-10-0-129-88 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "53814" uid: 92abb3d4-8eee-4edd-a73c-3286870f805c spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: 10.134.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T02:53:44Z" message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 2.132084ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 2.100012ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 2.263197ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 2.617665ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 2.088961ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:17:44Z" - latency: 2.033927ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:16:44Z" - latency: 2.3274ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:15:44Z" - latency: 1.729089ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:14:44Z" - latency: 2.459393ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:13:44Z" - latency: 1.520171ms message: 'network-check-target-ip-10-0-129-88: tcp connection to 10.134.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-ip-10-0-132-232 namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "53815" uid: b30f6086-25ae-4aae-a512-61b0b039b672 spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: 10.132.0.5:8080 status: conditions: - lastTransitionTime: "2026-07-08T02:53:44Z" message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 934.612µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 1.159084ms message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 1.263593ms message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 1.174972ms message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 869.379µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:17:44Z" - latency: 1.183656ms message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:16:44Z" - latency: 857.573µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:15:44Z" - latency: 870.207µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:14:44Z" - latency: 861.374µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:13:44Z" - latency: 895.07µs message: 'network-check-target-ip-10-0-132-232: tcp connection to 10.132.0.5:8080 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:12:44Z" - apiVersion: controlplane.operator.openshift.io/v1alpha1 kind: PodNetworkConnectivityCheck metadata: creationTimestamp: "2026-07-08T02:46:43Z" generation: 1 labels: networking.openshift.io/managedBy: oc-connectivity-check-controller name: network-check-source-ip-10-0-132-232-to-network-check-target-service-cluster namespace: openshift-network-diagnostics ownerReferences: - apiVersion: v1 kind: Node name: ip-10-0-132-232.ec2.internal uid: 90cf3aa6-db99-4630-af6e-02fcc63482f9 resourceVersion: "55675" uid: 263871e1-6881-4ca1-99a6-2aebb4df9ca7 spec: sourcePod: network-check-source-989f8b8dc-46djp targetEndpoint: network-check-target:80 status: conditions: - lastTransitionTime: "2026-07-08T02:52:44Z" message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnectSuccess status: "True" type: Reachable successes: - latency: 1.407965ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:22:44Z" - latency: 1.93904ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:22:44Z" - latency: 1.034983ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:21:44Z" - latency: 1.888305ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:21:44Z" - latency: 891.751µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:20:44Z" - latency: 2.036309ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:20:44Z" - latency: 1.020965ms message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:19:44Z" - latency: 1.89647ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:19:44Z" - latency: 983.189µs message: 'network-check-target-service-cluster: tcp connection to network-check-target:80 succeeded' reason: TCPConnect success: true time: "2026-07-08T03:18:44Z" - latency: 1.79449ms message: 'network-check-target-service-cluster: resolved host name network-check-target successfully' reason: DNSResolve success: true time: "2026-07-08T03:18:44Z" kind: List metadata: resourceVersion: ""