apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    generation: 243
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46456"
    uid: 713a336f-a51c-4ffb-90b3-e7f5a25e3a4e
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:13:47Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.044134ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 3.196896ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 2.9548ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 2.014645ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 2.312842ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:37:47Z"
    - latency: 3.202925ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:36:47Z"
    - latency: 3.528136ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:35:47Z"
    - latency: 2.157148ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:34:47Z"
    - latency: 5.164218ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:33:47Z"
    - latency: 3.617088ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46458"
    uid: 96aadd36-aea0-4374-9777-a0112a7cf240
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: 172.30.44.146:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:13:47Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.305979ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 4.08493ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 4.636005ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 4.45994ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 5.178609ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:37:47Z"
    - latency: 3.651098ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:36:47Z"
    - latency: 3.489785ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:35:47Z"
    - latency: 2.215629ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:34:47Z"
    - latency: 2.857546ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:33:47Z"
    - latency: 3.076792ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.44.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46455"
    uid: ea71a071-7197-479a-8399-306b0ba7fd2f
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:13:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.599617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 3.674268ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 4.926612ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 3.31849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 3.497074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:37:47Z"
    - latency: 3.499594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:36:47Z"
    - latency: 3.226797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:35:47Z"
    - latency: 7.546522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:34:47Z"
    - latency: 2.479306ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:33:47Z"
    - latency: 2.431285ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46958"
    uid: 75e288d4-0777-46a9-90b6-8f1a046eb03c
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:12:47Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.013057ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:42:47Z"
    - latency: 12.182286ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:42:47Z"
    - latency: 2.182028ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 12.619398ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 782.531µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 13.084071ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 1.11164ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 15.945448ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 1.267414ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 7.640155ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46959"
    uid: 71889417-4b0c-483a-87b5-4f0890a0056c
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:12:47Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.271283ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:42:47Z"
    - latency: 13.357067ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:42:47Z"
    - latency: 2.080707ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 13.956154ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 1.440068ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 12.402873ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 958.116µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 17.575751ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 876.143µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 9.365412ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46459"
    uid: a02281f4-b553-4e48-b3f7-75931e4bbb78
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:13:47Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.961582ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 17.126539ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 2.145937ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 3.646557ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 4.524661ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:37:47Z"
    - latency: 7.085091ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:36:47Z"
    - latency: 3.69502ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:35:47Z"
    - latency: 8.752985ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:34:47Z"
    - latency: 4.130771ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:33:47Z"
    - latency: 3.513623ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46957"
    uid: 91e135d3-4a65-4ffc-9d1a-5cd03f624aaa
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:12:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.664445ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:42:47Z"
    - latency: 7.646264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:42:47Z"
    - latency: 2.248669ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 5.440535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 2.061166ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 17.724415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 5.681852ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 7.591624ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 3.455254ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 1.703855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T04:38:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46457"
    uid: 0aa6ed94-9a47-437e-a347-9a89974434f0
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: 10.128.0.38:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:13:47Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.069406ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 5.134478ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 5.297592ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 2.178199ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 4.523852ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:37:47Z"
    - latency: 7.325146ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:36:47Z"
    - latency: 2.425835ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:35:47Z"
    - latency: 7.579143ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:34:47Z"
    - latency: 2.526308ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:33:47Z"
    - latency: 7.308556ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:32:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T04:06:46Z"
    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: 8e2844ed-1bab-4ac4-ac30-ce7bff37f649
    resourceVersion: "46454"
    uid: 695436f9-cf0d-4f7c-a3f5-bddd836ab5f4
  spec:
    sourcePod: network-check-source-7c67b67d47-ghjxr
    targetEndpoint: 172.30.194.41:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T04:13:47Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.035132ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:41:47Z"
    - latency: 5.454486ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:40:47Z"
    - latency: 4.182653ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:39:47Z"
    - latency: 4.08084ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:38:47Z"
    - latency: 5.068586ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:37:47Z"
    - latency: 7.45219ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:36:47Z"
    - latency: 3.968797ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:35:47Z"
    - latency: 8.562209ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:34:47Z"
    - latency: 3.230067ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:33:47Z"
    - latency: 7.797829ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.194.41:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T04:32:47Z"
kind: List
metadata:
  resourceVersion: ""