apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    generation: 135
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "38383"
    uid: 606978ab-8354-4a6f-b9bb-05ea5e0a3f18
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:15:29Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.394885ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 1.403175ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:21:29Z"
    - latency: 2.459421ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:20:29Z"
    - latency: 1.798925ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:19:29Z"
    - latency: 2.111182ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:18:29Z"
    - latency: 5.402695ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:17:29Z"
    - latency: 2.671126ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:16:29Z"
    - latency: 909.193µs
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:15:29Z"
    - latency: 5.059836ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:14:29Z"
    - latency: 3.326413ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "38385"
    uid: 76ad2456-da7e-455d-8e53-9ac45c4f4bb1
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: 172.30.173.168:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:15:29Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.38571ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 4.199004ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:21:29Z"
    - latency: 4.391489ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:20:29Z"
    - latency: 2.548644ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:19:29Z"
    - latency: 6.645336ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:18:29Z"
    - latency: 1.315442ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:17:29Z"
    - latency: 1.573769ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:16:29Z"
    - latency: 2.073412ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:15:29Z"
    - latency: 9.961659ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:14:29Z"
    - latency: 4.83598ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.173.168:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "38387"
    uid: c302445e-d0ce-4b30-abc1-5536f3fa463a
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:15:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.027325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 4.554733ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:21:29Z"
    - latency: 2.529022ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:20:29Z"
    - latency: 3.238161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:19:29Z"
    - latency: 7.442376ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:18:29Z"
    - latency: 6.178384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:17:29Z"
    - latency: 1.672982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:16:29Z"
    - latency: 1.847586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:15:29Z"
    - latency: 10.141803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:14:29Z"
    - latency: 3.005805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "40456"
    uid: 91622418-ad60-4320-9d73-110161f1e615
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:14:29Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 442.851µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:26:29Z"
    - latency: 14.304036ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:26:29Z"
    - latency: 339.718µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:25:29Z"
    - latency: 12.995984ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:25:29Z"
    - latency: 4.327088ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:24:29Z"
    - latency: 17.6874ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:24:29Z"
    - latency: 892.672µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:23:29Z"
    - latency: 9.720552ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:23:29Z"
    - latency: 1.104678ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 11.999508ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "40455"
    uid: 303068b5-20c3-4d75-b7cc-ce69b51cfed4
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:14:29Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.504757ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:26:29Z"
    - latency: 10.711757ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:26:29Z"
    - latency: 932.993µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:25:29Z"
    - latency: 12.238304ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:25:29Z"
    - latency: 3.144808ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:24:29Z"
    - latency: 18.925151ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:24:29Z"
    - latency: 1.045396ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:23:29Z"
    - latency: 9.487845ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:23:29Z"
    - latency: 1.119738ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 11.826804ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "38382"
    uid: e12368bb-c79d-462e-859a-cf189f719762
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:15:29Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.913342ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 2.085712ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:21:29Z"
    - latency: 3.21027ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:20:29Z"
    - latency: 2.171914ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:19:29Z"
    - latency: 8.281527ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:18:29Z"
    - latency: 7.945438ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:17:29Z"
    - latency: 3.693392ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:16:29Z"
    - latency: 1.359534ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:15:29Z"
    - latency: 10.924273ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:14:29Z"
    - latency: 2.985344ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "40454"
    uid: c836f2df-bd74-4bf3-a8dc-5cca00e4c0a2
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:14:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.058506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:26:29Z"
    - latency: 3.361473ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:26:29Z"
    - latency: 1.399535ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:25:29Z"
    - latency: 3.855506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:25:29Z"
    - latency: 1.268402ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:24:29Z"
    - latency: 8.357538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:24:29Z"
    - latency: 1.375854ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:23:29Z"
    - latency: 6.090022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:23:29Z"
    - latency: 3.98969ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 2.82297ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-20T15:22:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "38386"
    uid: ab592ff9-55cb-4c85-9b8b-573bacb4e444
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: 10.128.0.37:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:15:29Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.991054ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 1.577629ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:21:29Z"
    - latency: 2.650456ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:20:29Z"
    - latency: 3.272642ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:19:29Z"
    - latency: 8.8132ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:18:29Z"
    - latency: 6.725398ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:17:29Z"
    - latency: 2.421451ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:16:29Z"
    - latency: 2.523363ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:15:29Z"
    - latency: 5.521648ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:14:29Z"
    - latency: 5.516998ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-20T15:08:28Z"
    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: efc6ffa4-4c60-499b-9f65-a43b01ea37a0
    resourceVersion: "38384"
    uid: 1ad7973f-0e2b-48f0-98b8-0bce7fecffc7
  spec:
    sourcePod: network-check-source-58fb6744f5-nth67
    targetEndpoint: 172.30.170.110:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-20T15:15:29Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.408419ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:22:29Z"
    - latency: 6.714256ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:21:29Z"
    - latency: 2.498462ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:20:29Z"
    - latency: 2.840141ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:19:29Z"
    - latency: 8.613585ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:18:29Z"
    - latency: 8.060641ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:17:29Z"
    - latency: 2.214266ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:16:29Z"
    - latency: 2.047171ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:15:29Z"
    - latency: 10.41805ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:14:29Z"
    - latency: 6.678417ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.170.110:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-20T15:13:29Z"
kind: List
metadata:
  resourceVersion: ""