apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    generation: 252
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "51064"
    uid: 52f949b8-6c93-40ec-af05-9f11ca546b75
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:03:34Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.142269ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:52:34Z"
    - latency: 2.561693ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:51:34Z"
    - latency: 3.587588ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 1.794633ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 2.715397ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 4.868609ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 2.300816ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 1.996489ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:45:34Z"
    - latency: 1.957814ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:44:34Z"
    - latency: 2.938556ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:43:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "51067"
    uid: 71f9769f-59e8-4722-8d15-8d84aed5634e
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: 172.30.160.99:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:03:34Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.494131ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:52:34Z"
    - latency: 2.519912ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:51:34Z"
    - latency: 2.067261ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 5.154455ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 3.205608ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 5.032663ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 2.312505ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 1.943538ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:45:34Z"
    - latency: 1.874931ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:44:34Z"
    - latency: 3.772845ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.160.99:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:43:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "51065"
    uid: 3890152f-d749-41d5-98fb-51c225d9393d
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:03:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.525142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:52:34Z"
    - latency: 2.911901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:51:34Z"
    - latency: 3.419514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 2.203933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 2.994983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 1.354613ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 4.078819ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 1.781673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:45:34Z"
    - latency: 2.422504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:44:34Z"
    - latency: 1.948243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:43:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "50330"
    uid: 8e8ac505-2eca-491a-ab1c-a3b0c77da6d8
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:02:34Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 293.378µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 18.670336ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 698.687µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 10.830954ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 1.021824ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 10.139038ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 1.340183ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 17.066338ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 622.515µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 10.253909ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "50329"
    uid: bf62aa6f-1038-403a-bcbb-00e148956528
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:02:34Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.436475ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 10.056466ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 1.121218ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 10.330262ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 1.062605ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 10.080446ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 3.806633ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 12.162968ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 374.629µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 11.652654ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "51068"
    uid: 7a9a8ad5-990e-45f1-86c3-7eb5db0ebf4b
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:03:34Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.121747ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:52:34Z"
    - latency: 4.993713ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:51:34Z"
    - latency: 2.749857ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 2.195663ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 3.174318ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 4.752197ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 2.320467ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 2.649944ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:45:34Z"
    - latency: 2.441704ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:44:34Z"
    - latency: 6.618609ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:43:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "50328"
    uid: 0d27c09c-7fb9-4ca2-a41a-e6edce584a43
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:02:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.560238ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 2.881161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 1.758622ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 6.906499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 1.893967ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 6.608832ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 1.902566ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 5.649959ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 807.619µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 3.821204ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-05T11:46:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "51063"
    uid: 56e6d472-1968-4054-b5a4-65b47b4be3fa
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: 10.128.0.34:8443
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:03:34Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.877588ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:52:34Z"
    - latency: 5.518145ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:51:34Z"
    - latency: 2.818759ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 3.530045ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 3.403263ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 4.88641ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 1.294702ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 2.84615ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:45:34Z"
    - latency: 3.951838ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:44:34Z"
    - latency: 2.391434ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:43:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-05T10:56:33Z"
    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: ea73023b-75de-4456-80a9-4718aa8e39ac
    resourceVersion: "51066"
    uid: 12f43528-e359-4dac-8f2d-68e1c4788a01
  spec:
    sourcePod: network-check-source-85d8db45d4-c2mhw
    targetEndpoint: 172.30.145.214:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-05T11:03:34Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.690844ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:52:34Z"
    - latency: 5.209108ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:51:34Z"
    - latency: 2.919821ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:50:34Z"
    - latency: 4.054639ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:49:34Z"
    - latency: 3.492156ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:48:34Z"
    - latency: 4.765717ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:47:34Z"
    - latency: 1.777693ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:46:34Z"
    - latency: 3.069025ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:45:34Z"
    - latency: 4.175223ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:44:34Z"
    - latency: 2.22113ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.145.214:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-05T11:43:34Z"
kind: List
metadata:
  resourceVersion: ""