apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40:50Z"
    generation: 297
    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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "73534"
    uid: 41c6e6e5-6e83-4980-82cd-5b69e749f814
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:47:51Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.107961ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 1.677952ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 3.544977ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 1.963179ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 3.116037ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 1.171029ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:59:51Z"
    - latency: 2.413909ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:58:51Z"
    - latency: 1.915727ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:57:51Z"
    - latency: 4.78462ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:56:51Z"
    - latency: 2.82933ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:55:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40:50Z"
    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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72164"
    uid: 0d98648d-9567-42e0-b59f-d9ff0d2027ef
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: 172.30.172.144:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:47:51Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.575129ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 2.294706ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 4.156163ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 2.485021ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 2.811549ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 1.700951ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:59:51Z"
    - latency: 3.689371ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:58:51Z"
    - latency: 4.612493ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:57:51Z"
    - latency: 4.374638ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:56:51Z"
    - latency: 3.487117ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.172.144:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:55:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40:50Z"
    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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72153"
    uid: 4b8d7c10-60bf-4503-9f36-3ce50c3d2436
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:47:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.836875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 1.902666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 4.588563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 3.595329ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 3.920057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 3.446815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:59:51Z"
    - latency: 4.927681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:58:51Z"
    - latency: 11.476603ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:57:51Z"
    - latency: 5.020235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:56:51Z"
    - latency: 3.58594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:55:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40: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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72160"
    uid: 1f029e5b-5521-4073-83ea-6f0e8e5dc5fb
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:46:51Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 384.019µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 10.464918ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 1.771324ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 10.225882ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 962.394µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 11.727069ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 798.34µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 6.959912ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 436.54µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 16.031204ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:00:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40: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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72159"
    uid: c8561cfa-d0ba-4a2e-a02d-7791a415a6af
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:46:51Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.881µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 9.669568ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 1.014044ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 10.818897ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 811.28µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 12.490017ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 820.181µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 7.111715ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 879.812µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 12.13668ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:00:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40: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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72151"
    uid: d5803921-ad52-4825-965b-969e8c11e52c
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:47:51Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.265881ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 1.61339ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 5.169988ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 2.555543ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 3.163258ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 2.445691ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:59:51Z"
    - latency: 4.572003ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:58:51Z"
    - latency: 3.530816ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:57:51Z"
    - latency: 5.115667ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:56:51Z"
    - latency: 3.956617ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:55:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40: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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72156"
    uid: 18f1fe72-c9b9-40ff-81d8-0c96becf46f1
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:46:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.745µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 7.167326ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 3.309342ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 6.438039ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 4.715776ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 6.112671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 1.350033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 2.533793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 1.460666ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 5.004683ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T11:00:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40: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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72152"
    uid: aa4a0bdf-f836-4cc5-893b-d2af6bedcb88
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: 10.128.0.46:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:47:51Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.411899ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 2.243475ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 4.510411ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 3.180579ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 3.410684ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 3.502837ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:59:51Z"
    - latency: 2.425679ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:58:51Z"
    - latency: 3.451995ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:57:51Z"
    - latency: 4.43491ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:56:51Z"
    - latency: 2.088771ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.46:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:55:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T09:40: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: e4052aff-9961-4131-8036-ded1e1d0911b
    resourceVersion: "72154"
    uid: bec8f772-e7ed-49c4-ba78-d7a25b95daed
  spec:
    sourcePod: network-check-source-b4bf74f6-wqvfk
    targetEndpoint: 172.30.211.203:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T09:47:51Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.571978ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:04:51Z"
    - latency: 6.53859ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:03:51Z"
    - latency: 2.83968ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:02:51Z"
    - latency: 6.49129ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:01:51Z"
    - latency: 3.599979ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T11:00:51Z"
    - latency: 2.136623ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:59:51Z"
    - latency: 1.899327ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:58:51Z"
    - latency: 11.239247ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:57:51Z"
    - latency: 4.283426ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:56:51Z"
    - latency: 2.83702ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.211.203:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T10:55:51Z"
kind: List
metadata:
  resourceVersion: ""