apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    generation: 237
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47665"
    uid: 951894bd-5bba-451c-9610-64a8681c4ccc
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:32:54Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.714868ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 10.619606ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 2.945019ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 1.948182ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 5.565358ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 3.914075ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:02:54Z"
    - latency: 1.598793ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:01:54Z"
    - latency: 1.794909ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:00:54Z"
    - latency: 1.564422ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:59:54Z"
    - latency: 6.080803ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:58:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47670"
    uid: f340fdfc-952b-478e-9378-99c38ccb23ba
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: 172.30.7.211:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:32:54Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.420196ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 10.544545ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 2.667642ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 3.080522ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 5.422865ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 5.841925ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:02:54Z"
    - latency: 2.458265ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:01:54Z"
    - latency: 8.024614ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:00:54Z"
    - latency: 2.732613ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:59:54Z"
    - latency: 6.388452ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.7.211:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:58:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47669"
    uid: af329316-ff3e-401c-beb3-a83b306a70e1
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:32:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.413058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 12.421395ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 2.519299ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 4.48351ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 1.358457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 5.062194ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:02:54Z"
    - latency: 3.087602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:01:54Z"
    - latency: 8.152427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:00:54Z"
    - latency: 1.931112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:59:54Z"
    - latency: 1.737796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:58:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47672"
    uid: 091688e0-2806-4aac-9a59-48280cfb97d9
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:31:54Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.708016ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 15.520509ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 1.350386ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 10.700079ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 1.769738ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 17.03094ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 1.763807ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 16.994571ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 359.37µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 16.583661ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:03:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47673"
    uid: a554996a-4ce4-4a5c-a9d2-3cece1523bfb
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:31:54Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.747667ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 17.45619ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 384.391µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 14.708837ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 1.917922ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 17.176943ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 448.672µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 23.365252ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 1.469759ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 14.627988ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:03:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47666"
    uid: b7a85fec-fa41-478d-b2a5-8d366604b07b
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:32:54Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.78943ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 3.33536ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 4.249935ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 2.094896ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 10.352745ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 3.755131ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:02:54Z"
    - latency: 2.349083ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:01:54Z"
    - latency: 12.036041ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:00:54Z"
    - latency: 1.567413ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:59:54Z"
    - latency: 6.045312ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:58:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47667"
    uid: 428929ec-0d1a-47e0-a9c1-9f671b174bc7
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:31:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.231831ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 3.35286ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 7.322158ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 6.238308ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 1.779487ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 10.966486ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 4.214482ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 9.128532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 4.682655ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 5.779234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T23:03:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47671"
    uid: d3d3918d-3065-4254-ac61-28775c09d689
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: 10.128.0.31:8443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:32:54Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.44411ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 3.671499ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 5.966401ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 8.597479ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 5.136596ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 4.087539ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:02:54Z"
    - latency: 4.279334ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:01:54Z"
    - latency: 8.062185ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:00:54Z"
    - latency: 4.521901ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:59:54Z"
    - latency: 6.655988ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.31:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:58:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T22:25:53Z"
    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: 730d6115-08f3-4ffe-b3c5-a4e6fa7e6675
    resourceVersion: "47668"
    uid: 9b8feb4c-ebe5-4a72-ad18-decb5de53e4c
  spec:
    sourcePod: network-check-source-85d8db45d4-5gbc4
    targetEndpoint: 172.30.105.81:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T22:32:54Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.653022ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:07:54Z"
    - latency: 5.761665ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:06:54Z"
    - latency: 5.864948ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:05:54Z"
    - latency: 8.641499ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:04:54Z"
    - latency: 5.739462ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:03:54Z"
    - latency: 3.481502ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:02:54Z"
    - latency: 5.088125ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:01:54Z"
    - latency: 10.409238ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T23:00:54Z"
    - latency: 5.532977ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:59:54Z"
    - latency: 1.720026ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.105.81:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T22:58:54Z"
kind: List
metadata:
  resourceVersion: ""