apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    generation: 228
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "53544"
    uid: f90176be-7047-4897-a3dc-9bdb6dc58ebd
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:46:58Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.86169ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 2.767174ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 2.636451ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 1.795938ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 1.46926ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 2.311452ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:16:58Z"
    - latency: 1.906191ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:15:58Z"
    - latency: 2.366963ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:14:58Z"
    - latency: 4.865561ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:13:58Z"
    - latency: 1.749656ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50824"
    uid: 7edc3985-a0ea-4db6-8621-0967e6f47a30
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: 172.30.145.230:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:46:58Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.058875ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 2.722323ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 1.649714ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 6.370421ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 3.73761ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 7.100371ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:16:58Z"
    - latency: 1.656075ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:15:58Z"
    - latency: 1.427598ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:14:58Z"
    - latency: 2.118557ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:13:58Z"
    - latency: 3.054682ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.145.230:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50820"
    uid: 62a79ef6-6b97-4635-8298-f389a98c087c
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:46:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.552539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 3.425322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 2.9723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 2.438176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 1.889101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 4.138801ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:16:58Z"
    - latency: 1.429798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:15:58Z"
    - latency: 3.327299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:14:58Z"
    - latency: 5.634601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:13:58Z"
    - latency: 1.686995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50826"
    uid: e90d0394-36e3-4bdc-b4ed-66992f7b56ad
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:45:58Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 342.24µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 8.652372ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 531.444µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 5.775015ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 876.614µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 5.95303ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 743.89µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 7.581474ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 259.147µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 7.339707ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:17:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50825"
    uid: 05c42b28-82e0-4314-9341-e5bfd702f11c
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:45:58Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.234µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 7.797209ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 207.586µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 6.741171ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 687.299µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 6.005881ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 962.446µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 7.403149ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 1.10168ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 6.185686ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:17:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50819"
    uid: cff539ce-2112-4ba9-9200-76adaf57abac
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:46:58Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.350477ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 3.779472ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 2.715823ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 3.797572ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 2.304102ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 2.109796ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:16:58Z"
    - latency: 3.485053ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:15:58Z"
    - latency: 3.423502ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:14:58Z"
    - latency: 1.834129ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:13:58Z"
    - latency: 1.730396ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50818"
    uid: 27a0b629-5235-483c-9abb-974af5e963b5
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:45:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.502101ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 4.633844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 2.494927ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 2.668232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 1.272574ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 2.732374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 3.252938ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 4.178462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 3.145715ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 4.646344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T15:17:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50822"
    uid: f122c70b-bdc1-4479-8115-4aa25eba2cd4
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: 10.128.0.38:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:46:58Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.196085ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 4.394638ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 2.878627ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 1.452029ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 2.389764ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 3.470514ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:16:58Z"
    - latency: 2.390984ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:15:58Z"
    - latency: 1.11359ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:14:58Z"
    - latency: 903.604µs
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:13:58Z"
    - latency: 2.272381ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:12:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T14:39:57Z"
    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: 740d3eac-e552-4d41-9ef9-4425e047b84e
    resourceVersion: "50821"
    uid: ba0635d0-fe2a-475b-ba81-15d5b7e13f01
  spec:
    sourcePod: network-check-source-58fb6744f5-848dv
    targetEndpoint: 172.30.183.57:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T14:46:58Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.956349ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:21:58Z"
    - latency: 3.453263ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:20:58Z"
    - latency: 3.042242ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:19:58Z"
    - latency: 7.293216ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:18:58Z"
    - latency: 2.718703ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:17:58Z"
    - latency: 3.777072ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:16:58Z"
    - latency: 3.243977ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:15:58Z"
    - latency: 1.315015ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:14:58Z"
    - latency: 1.957353ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:13:58Z"
    - latency: 1.705496ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.183.57:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T15:12:58Z"
kind: List
metadata:
  resourceVersion: ""