apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:51Z"
    generation: 165
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "38644"
    uid: 6f295597-1654-4815-b645-3a2f11383845
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:06:52Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.704163ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 109.588891ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:12:52Z"
    - latency: 6.007751ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:11:53Z"
    - latency: 1.550362ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:10:52Z"
    - latency: 6.531886ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:09:52Z"
    - latency: 13.635556ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:08:52Z"
    - latency: 2.53585ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:07:52Z"
    - latency: 1.370238ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:06:52Z"
    - latency: 1.199012ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:05:52Z"
    - latency: 44.427885ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:04:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:51Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "36070"
    uid: 9deb7b19-ed3d-4d41-b1b1-ec471ef60871
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: 172.30.124.185:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:06:52Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.797585ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 107.451514ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:12:52Z"
    - latency: 254.709811ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:11:53Z"
    - latency: 2.426356ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:10:52Z"
    - latency: 3.445703ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:09:52Z"
    - latency: 12.991829ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:08:52Z"
    - latency: 2.305504ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:07:52Z"
    - latency: 4.506284ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:06:52Z"
    - latency: 4.039162ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:05:52Z"
    - latency: 48.318824ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:04:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:51Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "36069"
    uid: 159b3747-0a3a-46fb-b52d-6ea7cc01e9d7
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:06:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.245628ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 106.595922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:12:52Z"
    - latency: 255.569965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:11:53Z"
    - latency: 1.48853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:10:52Z"
    - latency: 6.69602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:09:52Z"
    - latency: 13.447011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:08:52Z"
    - latency: 2.352515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:07:52Z"
    - latency: 3.421844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:06:52Z"
    - latency: 3.780924ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:05:52Z"
    - latency: 43.585703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:04:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:52Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "39194"
    uid: 794eddd1-b41c-4c42-a275-42bc01b1c592
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:05:52Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 618.336µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:17:52Z"
    - latency: 12.570509ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:17:52Z"
    - latency: 939.426µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:16:53Z"
    - latency: 204.223981ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:16:52Z"
    - latency: 604.777µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:15:52Z"
    - latency: 10.683277ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:15:52Z"
    - latency: 736.511µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:14:52Z"
    - latency: 7.136982ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:14:52Z"
    - latency: 162.334µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 11.590202ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:13:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:52Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "39193"
    uid: da73615b-b82e-4e9f-b988-3d7c49889131
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:05:52Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 776.952µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:17:52Z"
    - latency: 9.923857ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:17:52Z"
    - latency: 296.238µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:16:53Z"
    - latency: 205.595218ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:16:52Z"
    - latency: 773.901µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:15:52Z"
    - latency: 10.451941ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:15:52Z"
    - latency: 3.395492ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:14:52Z"
    - latency: 7.305507ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:14:52Z"
    - latency: 743.331µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 11.000166ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:13:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:52Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "36068"
    uid: bde9fa07-cd68-4dac-aff6-112c539fab23
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:06:52Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.337077ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 129.826197ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:12:52Z"
    - latency: 534.068505ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:11:52Z"
    - latency: 1.980984ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:10:52Z"
    - latency: 7.831659ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:09:52Z"
    - latency: 3.023291ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:08:52Z"
    - latency: 2.475529ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:07:52Z"
    - latency: 1.148632ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:06:52Z"
    - latency: 1.683916ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:05:52Z"
    - latency: 48.130569ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:04:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:52Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "39192"
    uid: 2455629f-5b92-45aa-8cf1-d0bbda3c6cf2
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:05:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.402772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:17:52Z"
    - latency: 2.931149ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:17:52Z"
    - latency: 1.8744ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:16:53Z"
    - latency: 200.371007ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:16:52Z"
    - latency: 1.020448ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:15:52Z"
    - latency: 4.666976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:15:52Z"
    - latency: 2.936509ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:14:52Z"
    - latency: 3.911106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:14:52Z"
    - latency: 2.516158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 6.308809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T13:13:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:52Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "36066"
    uid: b7224d57-6c28-4188-abc3-ac858d79d26b
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: 10.128.0.42:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:06:52Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.226521ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 132.102899ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:12:52Z"
    - latency: 263.21477ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:11:53Z"
    - latency: 5.134249ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:10:52Z"
    - latency: 6.803472ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:09:52Z"
    - latency: 14.736916ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:08:52Z"
    - latency: 2.365436ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:07:52Z"
    - latency: 2.574861ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:06:52Z"
    - latency: 3.805996ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:05:52Z"
    - latency: 9.583305ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:04:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T12:59:51Z"
    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: c456d6c3-a916-4f05-9928-7e43433a4d22
    resourceVersion: "36067"
    uid: f76f69bf-cd3d-4e48-8f48-f7b5c2dbcc46
  spec:
    sourcePod: network-check-source-7c67b67d47-5bb88
    targetEndpoint: 172.30.38.72:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T13:06:52Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.392878ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:13:52Z"
    - latency: 130.439323ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:12:52Z"
    - latency: 537.657583ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:11:52Z"
    - latency: 2.277011ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:10:52Z"
    - latency: 4.461669ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:09:52Z"
    - latency: 2.825086ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:08:52Z"
    - latency: 2.456148ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:07:52Z"
    - latency: 5.269175ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:06:52Z"
    - latency: 4.007361ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:05:52Z"
    - latency: 47.820811ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.38.72:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T13:04:52Z"
kind: List
metadata:
  resourceVersion: ""