apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    generation: 126
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23967"
    uid: 0cb8d38f-3c27-4f8c-9276-128bb7e9fa32
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:37:16Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.579572ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:37:16Z"
    - latency: 1.360589ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 2.8242ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 1.481173ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 2.252504ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 2.13713ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 2.441879ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23913"
    uid: ac496261-02c7-42b6-8c23-849aaf0ca6e6
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: 172.30.251.225:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:37:16Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.195208ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:37:16Z"
    - latency: 5.072965ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 2.685167ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 3.242023ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 2.874802ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 1.316127ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 3.387005ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.251.225:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23910"
    uid: 66bffb8d-c9bd-4679-bbbf-2925e6cba6d5
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:37:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.628307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:37:16Z"
    - latency: 1.265056ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 2.662766ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 1.328628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 2.287465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 2.414088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 2.442068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23761"
    uid: 9d8fbd11-b541-4694-bdd1-581ddc5b137c
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:36:16Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 188.006µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 10.460089ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 377.591µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 10.50512ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 222.627µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 8.766391ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 239.787µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 10.19578ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 4.750165ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 25.47957ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23760"
    uid: 69d429a4-7c30-452d-814a-e575c3d3489b
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:36:16Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 176.535µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 9.125661ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 365.35µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 10.653034ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 210.096µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 8.527045ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 219.376µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 10.464978ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 372.48µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 16.496676ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23911"
    uid: 97e2f3fd-edb7-4e10-b6f6-e1105951acbe
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:37:16Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04566ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:37:16Z"
    - latency: 2.256774ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 3.945582ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 5.090926ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 5.485656ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 7.10251ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 3.269671ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23759"
    uid: 1fb0de2d-5792-466f-bdc0-eab155ea23f6
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:36:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.72461ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 5.382874ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 1.387539ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 2.860052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 1.532634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 5.104237ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 3.592112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 2.584363ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 3.622242ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 2.547942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T13:32:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23909"
    uid: 40911eff-ec8c-48f0-9f17-3408eb83e243
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: 10.128.0.41:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:37:16Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.554305ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:37:16Z"
    - latency: 2.10121ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 2.549332ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 2.636795ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 5.98165ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 6.645628ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 3.720244ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.41:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:31:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T13:30:14Z"
    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: 91c86903-c481-4337-816d-5d4395974319
    resourceVersion: "23908"
    uid: 63455bf2-d265-43d2-b27b-a5d98f0a4105
  spec:
    sourcePod: network-check-source-b4bf74f6-qnwtb
    targetEndpoint: 172.30.179.87:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T13:37:16Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.519733ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:37:16Z"
    - latency: 2.645206ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:36:16Z"
    - latency: 3.028896ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:35:16Z"
    - latency: 4.647583ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:34:16Z"
    - latency: 6.519045ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:33:16Z"
    - latency: 1.640786ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:32:16Z"
    - latency: 4.355961ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.179.87:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T13:31:16Z"
kind: List
metadata:
  resourceVersion: ""