apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    generation: 192
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "40394"
    uid: e2228347-eebb-4a98-aae3-1e980c3c0a94
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:48:14Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.531748ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:55:14Z"
    - latency: 1.164368ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:54:14Z"
    - latency: 1.122417ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 2.27087ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 2.84614ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 2.286057ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 2.781619ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 4.205356ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:48:14Z"
    - latency: 3.826828ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:47:14Z"
    - latency: 2.48043ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "38602"
    uid: a28150bc-a0bc-4fd6-a1a0-2a6d1cc1d0dd
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: 172.30.166.241:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:48:14Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.535347ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:55:14Z"
    - latency: 2.653125ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:54:14Z"
    - latency: 1.492627ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 2.252619ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 12.6119ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 2.461072ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 2.202934ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 4.482053ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:48:14Z"
    - latency: 9.72299ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:47:14Z"
    - latency: 2.845328ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.166.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "38600"
    uid: ac13b9cd-febb-47b5-bde1-cbb1c6cdc362
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:48:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 8.498935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:55:14Z"
    - latency: 2.815338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:54:14Z"
    - latency: 1.341283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 2.197739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 2.588345ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 2.379158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 3.26431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 4.295028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:48:14Z"
    - latency: 3.188295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:47:14Z"
    - latency: 1.91693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "37049"
    uid: 95654172-d7bf-4faf-96de-f61441b8fc9b
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:47:14Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.132µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 14.390521ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 831.224µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 18.874239ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 984.437µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 38.249266ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 905.801µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 18.008588ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 601.326µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 9.414184ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:49:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "37048"
    uid: 198f08b2-0a52-4ba0-8a06-20ad4f72af7b
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:47:14Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 484.722µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 14.587005ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 1.013417ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 19.663013ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 1.322083ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 38.091554ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 935.753µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 17.601017ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 552.295µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 9.215248ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:49:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:13Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "38597"
    uid: 55f74a48-d8c2-4f32-b442-08f520c6be9d
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:48:14Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.289601ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:55:14Z"
    - latency: 6.57071ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:54:14Z"
    - latency: 8.1912ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 3.127064ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 13.19435ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 5.706462ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 8.360437ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 2.354027ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:48:14Z"
    - latency: 6.32698ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:47:14Z"
    - latency: 3.138624ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "37047"
    uid: f8b065e6-840f-4931-9626-1c3af55ac7ba
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:47:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.892689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 3.556677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 1.782091ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 10.676437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 11.869658ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 13.25064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 4.638194ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 5.442195ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 3.237ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 3.722133ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T14:49:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "38599"
    uid: 22bfc841-444f-4525-9c83-e59cd944924d
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: 10.128.0.42:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:48:14Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.632441ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:55:14Z"
    - latency: 2.421939ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:54:14Z"
    - latency: 3.473265ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 3.48515ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 13.443344ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 5.801044ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 2.443571ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 2.066601ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:48:14Z"
    - latency: 5.739988ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:47:14Z"
    - latency: 3.265268ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:46:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T14:41:12Z"
    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: a90b6cfe-c6a8-43ed-91fe-3b77c6c75fb3
    resourceVersion: "38598"
    uid: a73bab1a-fa69-4aaa-8a66-129db95b1d87
  spec:
    sourcePod: network-check-source-7c67b67d47-wdt59
    targetEndpoint: 172.30.248.29:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T14:48:14Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.46226ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:55:14Z"
    - latency: 2.04807ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:54:14Z"
    - latency: 3.477795ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:53:14Z"
    - latency: 3.214145ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:52:14Z"
    - latency: 13.511296ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:51:14Z"
    - latency: 9.960097ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:50:14Z"
    - latency: 4.632925ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:49:14Z"
    - latency: 4.196756ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:48:14Z"
    - latency: 5.755058ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:47:14Z"
    - latency: 3.768957ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.248.29:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T14:46:14Z"
kind: List
metadata:
  resourceVersion: ""