apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    generation: 168
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "39046"
    uid: e3b9e620-0b49-40fb-86de-3de353cd3d09
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:15:05Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.590521ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 1.348147ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:21:05Z"
    - latency: 2.534348ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:20:05Z"
    - latency: 5.095558ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:19:05Z"
    - latency: 3.841554ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:18:05Z"
    - latency: 1.50829ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:17:05Z"
    - latency: 2.339582ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:16:05Z"
    - latency: 1.812908ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:15:05Z"
    - latency: 1.728428ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:14:05Z"
    - latency: 2.21338ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "36237"
    uid: 2de0bd06-fc2c-48fe-a08c-7f976cd0e04e
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: 172.30.218.231:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:15:05Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.393212ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 1.815039ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:21:05Z"
    - latency: 4.710238ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:20:05Z"
    - latency: 5.677913ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:19:05Z"
    - latency: 4.843491ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:18:05Z"
    - latency: 2.626581ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:17:05Z"
    - latency: 5.724394ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:16:05Z"
    - latency: 1.587042ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:15:05Z"
    - latency: 14.314827ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:14:05Z"
    - latency: 1.909501ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.218.231:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "36241"
    uid: 6e735d2f-4797-4a75-95cb-a567d00b0d95
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:15:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.460963ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 2.869538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:21:05Z"
    - latency: 2.335823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:20:05Z"
    - latency: 4.896322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:19:05Z"
    - latency: 6.147265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:18:05Z"
    - latency: 2.125028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:17:05Z"
    - latency: 6.134117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:16:05Z"
    - latency: 2.446107ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:15:05Z"
    - latency: 9.887048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:14:05Z"
    - latency: 1.750128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "38851"
    uid: 2589e1cd-992e-417b-9a56-5e0c43fb6f81
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:14:05Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.726036ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:26:05Z"
    - latency: 9.354082ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:26:05Z"
    - latency: 358.179µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:25:05Z"
    - latency: 10.37338ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:25:05Z"
    - latency: 259.787µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:24:05Z"
    - latency: 7.780479ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:24:05Z"
    - latency: 431.952µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:23:05Z"
    - latency: 18.432967ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:23:05Z"
    - latency: 810.712µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 29.057833ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:22:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "38850"
    uid: 1eb48d4c-a622-4514-a02c-f64a80b5896d
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:14:05Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 484.092µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:26:05Z"
    - latency: 13.016111ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:26:05Z"
    - latency: 989.456µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:25:05Z"
    - latency: 8.348495ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:25:05Z"
    - latency: 745.949µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:24:05Z"
    - latency: 6.572667ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:24:05Z"
    - latency: 1.325166ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:23:05Z"
    - latency: 16.72125ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:23:05Z"
    - latency: 7.43769ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 18.363996ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:22:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "36239"
    uid: bff17c62-2548-4e14-acbb-762462125441
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:15:05Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.283547ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 11.408878ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:21:05Z"
    - latency: 11.033457ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:20:05Z"
    - latency: 6.954338ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:19:05Z"
    - latency: 8.072068ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:18:05Z"
    - latency: 2.96369ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:17:05Z"
    - latency: 5.707645ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:16:05Z"
    - latency: 2.739404ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:15:05Z"
    - latency: 21.398239ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:14:05Z"
    - latency: 2.22651ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "38849"
    uid: 6b588ccb-e9f0-4a44-aa2e-2c30444a7e43
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:14:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.745047ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:26:05Z"
    - latency: 11.268853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:26:05Z"
    - latency: 2.21826ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:25:05Z"
    - latency: 5.427376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:25:05Z"
    - latency: 2.511318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:24:05Z"
    - latency: 2.570639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:24:05Z"
    - latency: 13.160105ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:23:05Z"
    - latency: 3.476423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:23:05Z"
    - latency: 2.011535ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 10.832222ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-18T18:22:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "36238"
    uid: f20ee322-5384-4a57-b4e1-28ac72bd7b5e
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: 10.128.0.38:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:15:05Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.477467ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 10.876733ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:21:05Z"
    - latency: 4.675506ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:20:05Z"
    - latency: 6.212928ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:19:05Z"
    - latency: 7.668647ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:18:05Z"
    - latency: 2.086436ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:17:05Z"
    - latency: 5.428947ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:16:05Z"
    - latency: 2.559939ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:15:05Z"
    - latency: 6.61946ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:14:05Z"
    - latency: 2.657332ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:13:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-18T18:08:04Z"
    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: 6acd4a61-9d80-4f54-90a7-4ba0eb46353d
    resourceVersion: "36242"
    uid: 9a81a15f-f1a3-4a88-a8d8-f2286142be1b
  spec:
    sourcePod: network-check-source-b4bf74f6-nlqpp
    targetEndpoint: 172.30.156.155:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-18T18:15:05Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.911926ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:22:05Z"
    - latency: 10.723629ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:21:05Z"
    - latency: 4.313396ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:20:05Z"
    - latency: 6.278409ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:19:05Z"
    - latency: 7.564634ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:18:05Z"
    - latency: 1.772637ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:17:05Z"
    - latency: 5.342064ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:16:05Z"
    - latency: 2.889938ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:15:05Z"
    - latency: 2.651482ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:14:05Z"
    - latency: 3.232927ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.156.155:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-18T18:13:05Z"
kind: List
metadata:
  resourceVersion: ""