apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    generation: 231
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "48744"
    uid: 469a7351-eca2-4bfc-87ce-467bcc622555
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:37:08Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.789491ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 2.257375ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 2.742358ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 2.46288ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 2.353227ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:01:08Z"
    - latency: 4.939361ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:00:08Z"
    - latency: 3.820599ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:59:08Z"
    - latency: 1.847893ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:58:08Z"
    - latency: 998.278µs
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:57:08Z"
    - latency: 2.272445ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:56:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "48745"
    uid: af37c919-0a44-422e-91f3-2be6c0cef489
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: 172.30.5.250:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:37:08Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.359785ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 3.523471ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 2.607075ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 7.332268ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 1.796421ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:01:08Z"
    - latency: 1.662917ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:00:08Z"
    - latency: 4.22756ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:59:08Z"
    - latency: 5.181847ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:58:08Z"
    - latency: 2.378487ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:57:08Z"
    - latency: 8.883352ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.5.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:56:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "48742"
    uid: 8b382214-998f-4e37-9cd1-35c5f4d7964c
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:37:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.032178ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 2.09259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 1.897764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 2.745619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 3.254412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:01:08Z"
    - latency: 6.809654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:00:08Z"
    - latency: 4.54108ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:59:08Z"
    - latency: 2.512872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:58:08Z"
    - latency: 1.333878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:57:08Z"
    - latency: 2.662246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:56:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "49254"
    uid: 24fee4de-6ce0-48f8-9b12-4979066b0d01
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:36:08Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.060349ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:06:08Z"
    - latency: 11.948842ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:06:08Z"
    - latency: 1.170024ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 12.21987ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 648.669µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 10.10536ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 384.941µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 13.323251ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 535.945µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 15.993855ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "49255"
    uid: b20b35a4-861b-4ddd-8d0a-553f64c969a4
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:36:08Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.638564ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:06:08Z"
    - latency: 9.554924ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:06:08Z"
    - latency: 1.528544ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 12.403135ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 316.619µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 10.464129ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 1.320508ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 11.928032ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 1.441981ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 11.718603ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:07Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "48743"
    uid: a37e23c8-1acd-4146-8577-4c0f534c0eb5
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:37:08Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.163448ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 1.992267ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 4.480748ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 2.951204ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 1.929014ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:01:08Z"
    - latency: 1.135092ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:00:08Z"
    - latency: 4.233291ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:59:08Z"
    - latency: 715.06µs
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:58:08Z"
    - latency: 3.458258ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:57:08Z"
    - latency: 10.704015ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:56:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "49253"
    uid: 756eeef0-d55e-424d-a199-8897c6a22037
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:36:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.239306ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:06:08Z"
    - latency: 3.308355ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:06:08Z"
    - latency: 2.378379ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 4.585691ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 5.208799ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 2.520022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 3.410918ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 6.062524ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 2.409318ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 7.527514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-19T04:02:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "48746"
    uid: 11fd43fb-843e-4bea-91ab-27cc1657d3ea
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: 10.128.0.39:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:37:08Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.135857ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 3.727277ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 8.170934ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 5.26697ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 3.14613ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:01:08Z"
    - latency: 1.575695ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:00:08Z"
    - latency: 1.681288ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:59:08Z"
    - latency: 1.790931ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:58:08Z"
    - latency: 1.543474ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:57:08Z"
    - latency: 10.802518ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:56:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-19T03:30:06Z"
    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: 31c9daf2-6e0b-415d-b71f-bd1b354f8d5d
    resourceVersion: "48747"
    uid: 7db4200c-a352-4ac1-9609-8f38dcd9df1b
  spec:
    sourcePod: network-check-source-58fb6744f5-mh46g
    targetEndpoint: 172.30.157.181:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-19T03:37:08Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.903391ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:05:08Z"
    - latency: 4.038406ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:04:08Z"
    - latency: 1.680608ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:03:08Z"
    - latency: 3.200532ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:02:08Z"
    - latency: 3.552381ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:01:08Z"
    - latency: 8.009568ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T04:00:08Z"
    - latency: 3.466289ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:59:08Z"
    - latency: 2.526292ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:58:08Z"
    - latency: 1.76067ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:57:08Z"
    - latency: 10.761536ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.157.181:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-19T03:56:08Z"
kind: List
metadata:
  resourceVersion: ""