apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    generation: 348
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "75308"
    uid: 73adc2c6-319b-46b8-ac36-b3a980f6d5fd
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:29:18Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.369044ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:53:18Z"
    - latency: 3.431818ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 2.746915ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 1.491037ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 2.685543ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 5.427829ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 2.24219ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:47:18Z"
    - latency: 884.747µs
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:46:18Z"
    - latency: 2.813908ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:45:18Z"
    - latency: 5.254234ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:44:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "75309"
    uid: 86d38ad7-0420-4e79-8620-befbdde6f227
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: 172.30.170.94:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:29:18Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.473289ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:53:18Z"
    - latency: 3.573552ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 3.314034ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 1.375063ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 2.517988ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 2.457927ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 1.987373ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:47:18Z"
    - latency: 845.326µs
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:46:18Z"
    - latency: 2.396295ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:45:18Z"
    - latency: 4.219892ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.170.94:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:44:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "75306"
    uid: 54dad9db-77e5-4e85-8c3b-78b5f804a603
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:29:18Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.8817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:53:18Z"
    - latency: 3.639834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 2.931652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 2.703164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 2.86905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 2.57976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 1.919539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:47:18Z"
    - latency: 1.589129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:46:18Z"
    - latency: 4.881104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:45:18Z"
    - latency: 1.686034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:44:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "74794"
    uid: aaafed7b-2b95-41fc-b326-664b5ac3c26c
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:28:18Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019691ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 29.287056ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 1.243818ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 12.798791ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 769.784µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 8.741043ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 1.335622ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 10.646122ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 1.26961ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 12.700047ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "74795"
    uid: 560b796d-ffbe-4068-b09c-d9c9ad9a8733
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:28:18Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.333851ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 29.40286ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 1.360202ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 13.229884ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 662.781µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 9.260949ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 1.244549ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 10.941992ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 325.501µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 14.516214ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "75304"
    uid: 4579e967-115e-4ba1-a327-8bc005050834
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:29:18Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.420229ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:53:18Z"
    - latency: 3.81638ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 3.976495ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 1.414864ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 1.616031ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 5.591414ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 2.651863ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:47:18Z"
    - latency: 1.524608ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:46:18Z"
    - latency: 2.578691ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:45:18Z"
    - latency: 6.221943ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:44:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "74792"
    uid: 99c1d5de-59b6-4019-a33d-a946185626cf
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:28:18Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.87864ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 4.798419ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 1.815006ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 3.053966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 763.334µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 3.144518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 2.008302ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 2.689144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 3.008024ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 5.531473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-19T13:48:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "75305"
    uid: faca313e-071e-49c7-a6b0-3c6166e0c949
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: 10.128.0.44:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:29:18Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.53498ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:53:18Z"
    - latency: 3.288883ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 4.375247ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 2.57384ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 1.455455ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 1.987112ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 1.368542ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:47:18Z"
    - latency: 3.053445ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:46:18Z"
    - latency: 1.481847ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:45:18Z"
    - latency: 1.714513ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.44:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:44:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-19T12:22:17Z"
    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: 538ea3c1-a257-4167-908a-2357320442cc
    resourceVersion: "75307"
    uid: 965857b4-c2b7-4c29-ba18-f0328bd33d30
  spec:
    sourcePod: network-check-source-b4bf74f6-6dmt7
    targetEndpoint: 172.30.220.146:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-19T12:29:18Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.816287ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:53:18Z"
    - latency: 3.675665ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:52:18Z"
    - latency: 4.218862ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:51:18Z"
    - latency: 2.581361ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:50:18Z"
    - latency: 2.819748ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:49:18Z"
    - latency: 2.450497ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:48:18Z"
    - latency: 1.485737ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:47:18Z"
    - latency: 1.466335ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:46:18Z"
    - latency: 2.061716ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:45:18Z"
    - latency: 2.051534ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.220.146:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-19T13:44:18Z"
kind: List
metadata:
  resourceVersion: ""