apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    generation: 261
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54882"
    uid: 5e2d8bfb-5cd9-44fa-8f1e-1d037f75c020
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:35:33Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.008781ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:17:33Z"
    - latency: 3.211672ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 3.48035ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 1.708744ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 1.98229ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 3.475829ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 2.714009ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:11:33Z"
    - latency: 7.676507ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:10:33Z"
    - latency: 3.171911ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:09:33Z"
    - latency: 5.168012ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54885"
    uid: 9e59dc59-73bf-4fa8-8628-2fb8be8a89b1
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: 172.30.133.113:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:35:33Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.95301ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:17:33Z"
    - latency: 6.64661ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 3.582592ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 6.104847ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 2.311179ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 4.068384ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 2.220907ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:11:33Z"
    - latency: 5.768558ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:10:33Z"
    - latency: 2.059982ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:09:33Z"
    - latency: 4.101975ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.113:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54884"
    uid: 0b612254-8ba8-4d3b-b72c-68f69bb8557b
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:35:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.006627ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:17:33Z"
    - latency: 5.216544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 5.017719ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 1.402976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 2.298849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 4.453164ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 2.433992ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:11:33Z"
    - latency: 8.23604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:10:33Z"
    - latency: 2.561316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:09:33Z"
    - latency: 5.283965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54377"
    uid: 774f79d7-bf8e-428f-86fa-10651b8c66cb
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:34:33Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.035176ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 13.362472ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 2.685049ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 9.311309ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 1.58329ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 15.406815ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 1.53872ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 7.004349ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 1.368485ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 9.623786ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:12:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54378"
    uid: eaf1b76e-8b96-4d1a-a3b7-d2747ec953c2
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:34:33Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 437.851µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 20.830673ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 272.177µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 13.702551ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 1.345574ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 13.521806ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 352.519µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 9.633506ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 541.784µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 13.371342ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:12:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:32Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54881"
    uid: 7d061ae6-7b71-48d2-ba17-3f30d2b44b20
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:35:33Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.139752ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:17:33Z"
    - latency: 2.526354ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 4.883465ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 6.180709ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 3.245753ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 5.736777ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 1.530169ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:11:33Z"
    - latency: 6.680391ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:10:33Z"
    - latency: 5.789268ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:09:33Z"
    - latency: 6.775214ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54376"
    uid: d71ed202-685b-41f5-ab53-6803c4c07eb9
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:34:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.393266ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 15.083226ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 2.877644ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 5.968993ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 3.224903ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 6.713682ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 704.048µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 2.090514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 2.597697ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 2.290119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T03:12:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54883"
    uid: 8016e713-9dc9-4a5a-9ea2-83cb9d444d98
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: 10.128.0.53:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:35:33Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.686768ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:17:33Z"
    - latency: 2.161426ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 3.427267ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 1.728234ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 2.404612ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 3.52324ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 1.145969ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:11:33Z"
    - latency: 11.300059ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:10:33Z"
    - latency: 2.637337ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:09:33Z"
    - latency: 4.244229ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.53:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:08:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T02:28:31Z"
    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: c26f8467-b1c8-4080-ab76-7bbfaa57ed70
    resourceVersion: "54886"
    uid: 2da86723-a01f-4618-9658-818d62e7c400
  spec:
    sourcePod: network-check-source-7d8f4c8c66-kcnkd
    targetEndpoint: 172.30.227.241:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T02:35:33Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.344518ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:17:33Z"
    - latency: 4.905706ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:16:33Z"
    - latency: 6.24609ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:15:33Z"
    - latency: 3.068988ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:14:33Z"
    - latency: 2.403721ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:13:33Z"
    - latency: 3.412748ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:12:33Z"
    - latency: 4.040083ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:11:33Z"
    - latency: 13.932656ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:10:33Z"
    - latency: 6.203778ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:09:33Z"
    - latency: 5.317236ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.227.241:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T03:08:33Z"
kind: List
metadata:
  resourceVersion: ""