apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    generation: 171
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51167"
    uid: 995b0e3d-0adf-4e54-af80-d23fd2fe14ab
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:18:03Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.320147ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 2.508922ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 1.776382ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 3.071869ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 34.401783ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 2.017269ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:48:03Z"
    - latency: 1.862294ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:47:03Z"
    - latency: 3.070059ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:46:03Z"
    - latency: 2.224233ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:45:03Z"
    - latency: 2.716897ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:44:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51165"
    uid: 3029dba1-9e0a-4168-b155-eb4c2baf1400
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: 172.30.124.194:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:18:03Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.845071ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 2.277585ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 2.337697ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 6.59695ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 2.200344ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 5.439847ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:48:03Z"
    - latency: 11.503372ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:47:03Z"
    - latency: 2.687937ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:46:03Z"
    - latency: 2.428739ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:45:03Z"
    - latency: 2.617144ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.194:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:44:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51163"
    uid: ac25a73c-b261-4072-b8b4-f9ed9b92c2f0
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:18:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.640736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 4.994893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 2.485081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 2.339997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 34.510425ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 3.458869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:48:03Z"
    - latency: 6.150607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:47:03Z"
    - latency: 2.314317ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:46:03Z"
    - latency: 8.083179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:45:03Z"
    - latency: 2.852881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:44:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51170"
    uid: 259c0323-a3c2-4171-96af-f3b981d2e83e
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:17:03Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 375.961µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 11.476111ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 1.006899ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 10.75287ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 819.093µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 7.798124ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 1.161813ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 15.272949ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 1.810223ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 46.392668ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51171"
    uid: 3c0355a6-d1a2-4e55-b29f-d4475c67483d
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:17:03Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.045279ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 10.022119ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 1.212184ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 10.203473ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 462.004µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 8.660429ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 1.280147ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 16.279879ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 1.303748ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 46.152541ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51164"
    uid: 9f9365d4-5442-466c-9adb-94d164ddab88
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:18:03Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.651304ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 5.426246ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 1.912076ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 4.023186ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 5.282922ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 6.448136ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:48:03Z"
    - latency: 1.781952ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:47:03Z"
    - latency: 3.242073ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:46:03Z"
    - latency: 7.712028ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:45:03Z"
    - latency: 5.456255ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:44:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51166"
    uid: 51cf92b0-4cd9-4881-8d50-0bdb19e48afb
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:17:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.178342ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 3.792259ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 1.344308ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 5.431096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 800.213µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 4.131088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 1.602206ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 10.930175ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 28.319827ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 6.311802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T12:49:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51168"
    uid: dd702c9f-0b69-42b5-8275-15f68d1206cb
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: 10.128.0.38:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:18:03Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.491103ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 1.772321ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 3.743278ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 3.870721ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 34.818085ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 4.273133ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:48:03Z"
    - latency: 2.105121ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:47:03Z"
    - latency: 3.675336ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:46:03Z"
    - latency: 1.956826ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:45:03Z"
    - latency: 1.987906ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.38:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:44:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T12:11:01Z"
    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: 51b0ed2f-7236-487a-afb3-d60cce1796f3
    resourceVersion: "51169"
    uid: d339b1e6-5b92-43dc-b362-75ec9cf34234
  spec:
    sourcePod: network-check-source-58fb6744f5-gjgxv
    targetEndpoint: 172.30.19.65:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T12:18:03Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.242032ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:53:03Z"
    - latency: 5.035875ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:52:03Z"
    - latency: 4.214911ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:51:03Z"
    - latency: 3.164761ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:50:03Z"
    - latency: 34.847116ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:49:03Z"
    - latency: 6.039565ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:48:03Z"
    - latency: 1.570465ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:47:03Z"
    - latency: 3.722078ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:46:03Z"
    - latency: 7.477932ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:45:03Z"
    - latency: 3.009156ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.19.65:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T12:44:03Z"
kind: List
metadata:
  resourceVersion: ""