apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    generation: 168
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "39598"
    uid: 93bf7130-2521-470c-a39b-8344ce8ea84e
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:10:36Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.051308ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 1.697268ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:16:36Z"
    - latency: 1.297957ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:15:36Z"
    - latency: 2.115291ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:14:36Z"
    - latency: 1.193004ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:13:36Z"
    - latency: 2.175041ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:12:36Z"
    - latency: 5.562257ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:11:36Z"
    - latency: 1.291316ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:10:36Z"
    - latency: 937.747µs
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:09:36Z"
    - latency: 2.406888ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "38122"
    uid: 53bcd574-7691-47bc-8305-aac2dcdf487f
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: 172.30.140.91:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:10:36Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.581033ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 3.229562ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:16:36Z"
    - latency: 2.934364ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:15:36Z"
    - latency: 2.783749ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:14:36Z"
    - latency: 2.382657ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:13:36Z"
    - latency: 1.006968ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:12:36Z"
    - latency: 6.347019ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:11:36Z"
    - latency: 3.729345ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:10:36Z"
    - latency: 1.103411ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:09:36Z"
    - latency: 4.29152ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.140.91:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "38120"
    uid: 06f0bdc1-0f0e-47bd-a58e-cca4e53947e2
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:10:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.572224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 3.273384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:16:36Z"
    - latency: 2.45241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:15:36Z"
    - latency: 2.959555ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:14:36Z"
    - latency: 2.202052ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:13:36Z"
    - latency: 1.738179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:12:36Z"
    - latency: 6.070221ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:11:36Z"
    - latency: 1.285076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:10:36Z"
    - latency: 1.634046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:09:36Z"
    - latency: 4.189767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "40166"
    uid: ffcbff45-837a-41ae-8444-947168ea39ad
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:09:36Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 509.434µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:21:36Z"
    - latency: 14.900906ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:21:36Z"
    - latency: 916.097µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:20:36Z"
    - latency: 10.983684ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:20:36Z"
    - latency: 760.332µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:19:36Z"
    - latency: 8.288297ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:19:36Z"
    - latency: 580.666µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:18:36Z"
    - latency: 7.902677ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:18:36Z"
    - latency: 1.296687ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 14.31919ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:17:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "40167"
    uid: 8c39f8a0-fa18-45b8-959f-b4472b16dbaa
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:09:36Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.254406ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:21:36Z"
    - latency: 13.560928ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:21:36Z"
    - latency: 1.511273ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:20:36Z"
    - latency: 10.038798ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:20:36Z"
    - latency: 646.528µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:19:36Z"
    - latency: 8.094861ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:19:36Z"
    - latency: 663.399µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:18:36Z"
    - latency: 11.318064ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:18:36Z"
    - latency: 763.702µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 14.794614ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:17:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "38117"
    uid: 301db1d8-093c-485d-b293-a35b6f39ce6b
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:10:36Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.560433ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 4.256411ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:16:36Z"
    - latency: 5.353303ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:15:36Z"
    - latency: 5.011354ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:14:36Z"
    - latency: 3.778657ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:13:36Z"
    - latency: 4.627541ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:12:36Z"
    - latency: 10.540998ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:11:36Z"
    - latency: 4.570329ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:10:36Z"
    - latency: 9.816237ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:09:36Z"
    - latency: 8.183169ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "40165"
    uid: 942818ff-27cf-4954-be1b-2ba04fea0f3d
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:09:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.638897ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:21:36Z"
    - latency: 3.858751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:21:36Z"
    - latency: 1.940326ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:20:36Z"
    - latency: 4.598621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:20:36Z"
    - latency: 1.38776ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:19:36Z"
    - latency: 5.987181ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:19:36Z"
    - latency: 2.237254ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:18:36Z"
    - latency: 1.537274ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:18:36Z"
    - latency: 1.921445ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 8.776051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-13T11:17:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "38118"
    uid: e1052306-0e30-4e64-b941-be9b2ac3d6ea
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: 10.128.0.40:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:10:36Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.728519ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 3.765488ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:16:36Z"
    - latency: 1.521093ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:15:36Z"
    - latency: 4.970542ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:14:36Z"
    - latency: 4.330362ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:13:36Z"
    - latency: 8.807459ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:12:36Z"
    - latency: 9.696634ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:11:36Z"
    - latency: 4.172687ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:10:36Z"
    - latency: 1.464411ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:09:36Z"
    - latency: 7.381157ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.40:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:08:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-13T11:03:35Z"
    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: cb006092-fd40-4d71-84fb-f3ba8c313f97
    resourceVersion: "38121"
    uid: 46ef1efc-01e7-4358-bd3f-606f86eb005f
  spec:
    sourcePod: network-check-source-7c67b67d47-jbx9v
    targetEndpoint: 172.30.135.185:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-13T11:10:36Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.111256ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:17:36Z"
    - latency: 3.739647ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:16:36Z"
    - latency: 2.375178ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:15:36Z"
    - latency: 6.28332ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:14:36Z"
    - latency: 4.012053ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:13:36Z"
    - latency: 3.309353ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:12:36Z"
    - latency: 9.317573ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:11:36Z"
    - latency: 4.109556ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:10:36Z"
    - latency: 1.680558ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:09:36Z"
    - latency: 7.16989ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.135.185:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-13T11:08:36Z"
kind: List
metadata:
  resourceVersion: ""