apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:49Z"
    generation: 111
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "34529"
    uid: 55aad07a-4329-4ae3-85e3-073c9a369dcd
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:43:51Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.992197ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:50:51Z"
    - latency: 3.63695ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:49:51Z"
    - latency: 1.317226ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 3.136855ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 2.276094ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 4.287921ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 1.48092ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 2.035635ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:43:51Z"
    - latency: 2.633446ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:42:51Z"
    - latency: 1.825983ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:49Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "34531"
    uid: 78ee560f-4b59-4012-b606-7ae4a121eac0
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: 172.30.168.83:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:43:51Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.506961ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:50:51Z"
    - latency: 2.697704ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:49:51Z"
    - latency: 1.45534ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 5.811514ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 2.304414ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 4.187028ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 3.034253ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 2.761615ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:43:51Z"
    - latency: 1.500133ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:42:51Z"
    - latency: 1.804442ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.168.83:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:49Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "34530"
    uid: 8e39a070-26e9-43dc-811a-26b7c41ddb9a
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:43:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.47163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:50:51Z"
    - latency: 2.314393ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:49:51Z"
    - latency: 1.583273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 2.451233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 2.659913ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 4.166738ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 2.862408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 1.932532ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:43:51Z"
    - latency: 1.696438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:42:51Z"
    - latency: 3.060638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:50Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "32814"
    uid: 43fac733-2559-45d8-a380-28071dbe8a0b
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:42:51Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.646625ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 11.764092ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 219.664µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 11.409383ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 687.906µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 13.026045ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 316.528µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 13.411784ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 1.133371ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 9.826818ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:50Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "32813"
    uid: 01bf33cf-a91c-4f49-be1f-4d3ec9545869
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:42:51Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 688.359µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 12.017099ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 732.593µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 10.415035ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 853.42µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 12.246467ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 2.55381ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 11.091249ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 1.885361ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 9.345374ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:50Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "34534"
    uid: 685d4806-33fb-484b-ba88-719da752146a
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:43:51Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.419299ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:50:51Z"
    - latency: 2.843988ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:49:51Z"
    - latency: 6.625902ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 6.822331ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 2.469898ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 4.422263ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 6.291421ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 3.582587ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:43:51Z"
    - latency: 1.644367ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:42:51Z"
    - latency: 4.232271ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:50Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "32812"
    uid: 2c9709dd-8e72-456e-bed1-7d8bd14de799
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:42:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.025µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 6.717934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 4.556341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 2.84929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 2.608031ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 3.471101ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 1.145316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 8.006448ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 1.825839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 6.450806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T12:44:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:50Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "34533"
    uid: a9a0f3e4-af2e-4340-bcad-3a9f5c236b90
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: 10.128.0.42:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:43:51Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.560377ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:50:51Z"
    - latency: 4.563435ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:49:51Z"
    - latency: 6.781345ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 6.950154ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 3.002341ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 4.118737ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 2.732644ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 4.945295ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:43:51Z"
    - latency: 3.017977ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:42:51Z"
    - latency: 4.667554ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:41:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T12:36:50Z"
    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: e2370ef4-aa49-40ce-994d-bc2226459c83
    resourceVersion: "34532"
    uid: 520e9969-d9f8-4bbe-89f4-17e7cd067136
  spec:
    sourcePod: network-check-source-7c67b67d47-7bdwc
    targetEndpoint: 172.30.3.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T12:43:51Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.624479ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:50:51Z"
    - latency: 1.407729ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:49:51Z"
    - latency: 6.837137ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:48:51Z"
    - latency: 6.891793ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:47:51Z"
    - latency: 3.141263ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:46:51Z"
    - latency: 4.118896ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:45:51Z"
    - latency: 2.698744ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:44:51Z"
    - latency: 5.045247ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:43:51Z"
    - latency: 1.172303ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:42:51Z"
    - latency: 4.677284ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.3.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T12:41:51Z"
kind: List
metadata:
  resourceVersion: ""