apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:39Z"
    generation: 138
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-kubernetes-apiserver-endpoint-master-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62890"
    uid: a6cf7336-fdad-415d-bdd3-fddc2f9a6296
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 192.168.34.10:17697
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.328907ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 2.733098ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 2.43891ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 2.124201ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 3.82746ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 3.668665ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 4.006905ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 2.747779ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 3.219642ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 3.054708ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.34.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:49:32Z"
    generation: 69
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-kubernetes-apiserver-endpoint-master-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "64022"
    uid: 4fec1a66-0bcc-435c-8540-89b361d01ede
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 192.168.34.11:17697
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:56:32Z"
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.076964ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:31:32Z"
    - latency: 3.13646ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:30:32Z"
    - latency: 7.374371ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:29:32Z"
    - latency: 5.032884ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:32Z"
    - latency: 2.81187ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:32Z"
    - latency: 3.50838ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:32Z"
    - latency: 2.197232ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:32Z"
    - latency: 3.868491ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:32Z"
    - latency: 2.626185ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:32Z"
    - latency: 2.322696ms
      message: 'kubernetes-apiserver-endpoint-master-1: tcp connection to 192.168.34.11:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:39Z"
    generation: 138
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-kubernetes-apiserver-endpoint-master-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62889"
    uid: 72c9227c-f4ef-45a9-8f40-b069fad33ced
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 192.168.34.12:17697
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.114169ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 7.728921ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 4.966682ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 2.960364ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 4.686644ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 4.566071ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 3.606013ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 9.280006ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 5.670563ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 5.186288ms
      message: 'kubernetes-apiserver-endpoint-master-2: tcp connection to 192.168.34.12:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-kubernetes-apiserver-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62886"
    uid: b45f8860-d0a7-4c31-8ac2-b53d750a87e6
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 172.30.8.122:443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.082957ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 5.135897ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 3.48345ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 3.623164ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 6.709372ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 7.021601ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 9.061609ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 4.568961ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 6.137476ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 5.2025ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.8.122:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62887"
    uid: dab8fc51-8b65-4da8-b0ab-cb6f07bc2693
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.664505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 3.783168ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 3.810379ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 4.024215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 6.66008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 6.004162ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 4.022496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 2.908303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 2.910493ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 3.760328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62893"
    uid: 5b0a375b-9ea1-4f2d-9353-677aeb737661
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: api.ocp.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:52:40Z"
      message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.030167ms
      message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 9.956176ms
      message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 2.379678ms
      message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 17.757269ms
      message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 3.634744ms
      message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 11.058867ms
      message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 2.045679ms
      message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 12.968492ms
      message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 2.184703ms
      message: 'load-balancer-api-external: tcp connection to api.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 17.955844ms
      message: 'load-balancer-api-external: resolved host name api.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62894"
    uid: f73a1fab-8a83-4dd3-a2c3-81a25e6423df
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: api-int.ocp.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:52:40Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.971596ms
      message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 10.227773ms
      message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 2.623515ms
      message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 18.325175ms
      message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 2.320376ms
      message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 12.691813ms
      message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 2.380318ms
      message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 12.770896ms
      message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 2.527693ms
      message: 'load-balancer-api-internal: tcp connection to api-int.ocp.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 18.262353ms
      message: 'load-balancer-api-internal: resolved host name api-int.ocp.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-network-check-target-master-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62900"
    uid: f709fbda-43f6-4b70-b8e1-51501820c25a
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 10.130.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:41Z"
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.666517ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:41Z"
    - latency: 21.174026ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:41Z"
    - latency: 36.913907ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:41Z"
    - latency: 2.170372ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:41Z"
    - latency: 5.158728ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:41Z"
    - latency: 2.565603ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:41Z"
    - latency: 3.83449ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:41Z"
    - latency: 2.624316ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:41Z"
    - latency: 3.823749ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:41Z"
    - latency: 3.764018ms
      message: 'network-check-target-master-0: tcp connection to 10.130.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-network-check-target-master-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62898"
    uid: f8584b84-c9b5-415f-8a35-001606ef2028
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 10.129.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:41Z"
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.786899ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:41Z"
    - latency: 1.152253ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:41Z"
    - latency: 3.574382ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:41Z"
    - latency: 3.717347ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:41Z"
    - latency: 3.934373ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:41Z"
    - latency: 2.951934ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:41Z"
    - latency: 1.498593ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:41Z"
    - latency: 3.184691ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:41Z"
    - latency: 3.599093ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:41Z"
    - latency: 2.09417ms
      message: 'network-check-target-master-1: tcp connection to 10.129.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-network-check-target-master-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62896"
    uid: 4e66ef22-4271-446d-807c-33fa2ee3affa
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:41Z"
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.330594ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:41Z"
    - latency: 3.362596ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:41Z"
    - latency: 984.348µs
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:41Z"
    - latency: 3.873181ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:41Z"
    - latency: 2.610224ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:41Z"
    - latency: 3.507891ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:41Z"
    - latency: 4.043226ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:41Z"
    - latency: 2.202933ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:41Z"
    - latency: 957.567µs
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:41Z"
    - latency: 3.106539ms
      message: 'network-check-target-master-2: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62895"
    uid: 4add0dd3-eee9-41ae-aaaf-64fe22b2607e
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:52:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.145728ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 1.889234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 2.379548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 1.410901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 2.764229ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 1.782221ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 5.150437ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 1.545124ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 4.466238ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 1.72804ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-10-11T11:24:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-openshift-apiserver-endpoint-master-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62892"
    uid: 0d16a1ab-c5ef-4b24-8170-0cf67fb8aeed
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 10.130.0.28:8443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.129549ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 7.268038ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 4.358025ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 4.395676ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 5.780925ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 4.123428ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 5.303642ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 4.975783ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 6.108215ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 10.586894ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.130.0.28:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-openshift-apiserver-endpoint-master-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62885"
    uid: 386831e8-9a2f-4ac4-b665-9c55d61d67c7
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 10.129.0.82:8443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.918364ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 4.654683ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 3.324095ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 3.096228ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 8.429361ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 4.388575ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 3.757277ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 11.095797ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 3.444708ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 6.378273ms
      message: 'openshift-apiserver-endpoint-master-1: tcp connection to 10.129.0.82:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-openshift-apiserver-endpoint-master-2
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62888"
    uid: cd23bde5-b609-4300-a79b-b6d08481cbf6
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 10.128.0.93:8443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.351573ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 8.872614ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 3.395198ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 4.802978ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 5.92914ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 4.310533ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 4.092117ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 3.462399ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 6.98727ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 9.960415ms
      message: 'openshift-apiserver-endpoint-master-2: tcp connection to 10.128.0.93:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-10-11T10:46:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-1-to-openshift-apiserver-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-1
      uid: a42c3d58-398c-4d83-a471-700c0c6694c4
    resourceVersion: "62891"
    uid: c004e1f3-33be-4f8b-bf03-cdb28a609310
  spec:
    sourcePod: network-check-source-967c7bb47-djx82
    targetEndpoint: 172.30.197.247:443
  status:
    conditions:
    - lastTransitionTime: "2025-10-11T10:53:40Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.339843ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:28:40Z"
    - latency: 5.310962ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:27:40Z"
    - latency: 4.337975ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:26:40Z"
    - latency: 4.762616ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:25:40Z"
    - latency: 5.925739ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:24:40Z"
    - latency: 3.948963ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:23:40Z"
    - latency: 8.405001ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:22:40Z"
    - latency: 3.838109ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:21:40Z"
    - latency: 4.361605ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:20:40Z"
    - latency: 11.205052ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.197.247:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-10-11T11:19:40Z"
kind: List
metadata:
  resourceVersion: ""