apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 111
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-kubernetes-apiserver-endpoint-master-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24795"
    uid: 4f947726-e26d-4e32-a46f-a227ceeb152b
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:26:22Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.17253ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:26:22Z"
    - latency: 1.286453ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 1.750123ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 2.193285ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 1.575349ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 1.873897ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 2.104423ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:20:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-kubernetes-apiserver-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24797"
    uid: caaf525b-b115-47a3-ae28-ab2522af794e
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: 172.30.145.128:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:26:22Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.743004ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:26:22Z"
    - latency: 3.562149ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 1.728973ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 2.475643ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 1.535258ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 5.291003ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 2.048391ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.128:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:20:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24798"
    uid: a9751a67-ea67-4aa8-b5ed-1e15707116e6
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:26:22Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.414426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:26:22Z"
    - latency: 1.004015ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 4.808271ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 2.302718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 2.683537ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 2.581604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 2.100812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:20:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24647"
    uid: c00045e4-4496-4e43-a5ec-ac8b128382cb
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:25:22Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 298.547µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 13.099217ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 339.689µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 15.487217ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 297.017µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 9.109339ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 506.623µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 18.070644ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 214.006µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 15.525639ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:21:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24648"
    uid: b13415ce-1e79-47e0-a6b3-0b811874bb12
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:25:22Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 223.386µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 13.393804ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 337.149µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 14.675887ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 207.095µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 9.748245ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 132.994µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 18.608897ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 216.756µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 16.256548ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:21:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-network-check-target-master-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24796"
    uid: aab0ccc3-38f2-439b-9ec4-87522f04c0e7
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:26:22Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.60738ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:26:22Z"
    - latency: 1.355954ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 5.533129ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 2.574154ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 1.506667ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 1.119268ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 4.542474ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:20:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24646"
    uid: 063d9efb-a531-452b-87dd-ed4cd2170890
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:25:22Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085617ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 5.676252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 1.411066ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 8.642216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 1.693803ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 6.126464ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 3.508548ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 10.34564ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 4.017221ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 4.451982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T10:21:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-openshift-apiserver-endpoint-master-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24800"
    uid: 06f983ad-c722-4176-ba1e-a1f301e5a3d0
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: 10.128.0.40:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:26:22Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.543809ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:26:22Z"
    - latency: 2.827171ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 4.562254ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 1.708833ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 10.231157ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 4.136954ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 2.156024ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:20:22Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T10:19:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-master-0-to-openshift-apiserver-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: master-0
      uid: 673840ad-4cc8-4ca9-8d21-07b73732aba5
    resourceVersion: "24799"
    uid: 12894345-92d0-480e-98c6-6a4d36153dd7
  spec:
    sourcePod: network-check-source-b4bf74f6-4kpnv
    targetEndpoint: 172.30.188.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T10:26:22Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.819146ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:26:22Z"
    - latency: 1.989329ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:25:22Z"
    - latency: 2.257756ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:24:22Z"
    - latency: 4.585755ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:23:22Z"
    - latency: 9.97453ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:22:22Z"
    - latency: 8.261017ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:21:22Z"
    - latency: 1.279832ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.188.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T10:20:22Z"
kind: List
metadata:
  resourceVersion: ""