apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    generation: 252
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46186"
    uid: 98d03d01-9749-48cd-a5cc-938bd2c47fc2
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:01:16Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.272584ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 3.94236ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 3.668463ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 2.439819ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 5.188366ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:25:16Z"
    - latency: 1.265976ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:24:16Z"
    - latency: 2.334166ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:23:16Z"
    - latency: 1.957025ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:22:16Z"
    - latency: 2.696526ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:21:16Z"
    - latency: 3.330854ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46187"
    uid: 968f5f5d-3a08-45cf-9b3a-77e87cf41b7d
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: 172.30.124.43:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:01:16Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.897671ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 3.804397ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 4.315321ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 4.590288ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 5.274029ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:25:16Z"
    - latency: 1.539774ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:24:16Z"
    - latency: 1.956846ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:23:16Z"
    - latency: 2.509601ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:22:16Z"
    - latency: 8.247003ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:21:16Z"
    - latency: 10.193468ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.124.43:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46191"
    uid: 7124fd28-a817-4043-945a-cb22b283cdc3
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:01:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.680238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 3.58508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 2.657334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 1.640406ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 5.00072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:25:16Z"
    - latency: 2.850021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:24:16Z"
    - latency: 2.366237ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:23:16Z"
    - latency: 2.083079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:22:16Z"
    - latency: 3.946821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:21:16Z"
    - latency: 3.445257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46620"
    uid: cbc834ae-5920-4ef8-942a-25b05252a48e
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:00:16Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.465µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:30:16Z"
    - latency: 7.428899ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:30:16Z"
    - latency: 1.023999ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 25.195947ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 215.006µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 15.269489ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 1.05446ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 11.428221ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 591.797µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 11.466822ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:26:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46621"
    uid: f4881a06-61d1-4eb5-bff4-eedc93f24a5f
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:00:16Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 409.862µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:30:16Z"
    - latency: 13.256612ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:30:16Z"
    - latency: 1.666357ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 24.722084ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 1.184033ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 14.404955ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 1.137582ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 11.575435ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 659.189µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 11.199914ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:26:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46188"
    uid: 4b4d53c7-7082-4d02-8d16-4fa6afae3dae
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:01:16Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.431381ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 3.789256ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 4.935749ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 3.706084ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 11.312968ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:25:16Z"
    - latency: 3.079357ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:24:16Z"
    - latency: 2.525402ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:23:16Z"
    - latency: 2.776778ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:22:16Z"
    - latency: 5.079473ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:21:16Z"
    - latency: 11.065062ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46619"
    uid: e9518680-e837-46f7-803b-29a999692160
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:00:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.164479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:30:16Z"
    - latency: 4.130036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:30:16Z"
    - latency: 11.897353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 5.603637ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 4.131976ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 8.251162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 1.364349ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 6.377649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 1.200684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 6.713029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T01:26:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46190"
    uid: 977aaf18-c367-4599-a5e9-7c4a7e1b08fc
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: 10.128.0.34:8443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:01:16Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.917766ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 3.469147ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 3.419236ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 2.469959ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 4.739763ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:25:16Z"
    - latency: 1.916504ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:24:16Z"
    - latency: 3.5474ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:23:16Z"
    - latency: 1.316467ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:22:16Z"
    - latency: 5.184456ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:21:16Z"
    - latency: 10.869527ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.34:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T00:54:15Z"
    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: d6ccd4da-b981-4c8c-9664-0abff09f66b8
    resourceVersion: "46189"
    uid: 993d4397-88d0-4d4b-84c5-a745002b9fce
  spec:
    sourcePod: network-check-source-6964bb78b7-qzwwq
    targetEndpoint: 172.30.76.239:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T01:01:16Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.70216ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:29:16Z"
    - latency: 2.455709ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:28:16Z"
    - latency: 2.280024ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:27:16Z"
    - latency: 3.157779ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:26:16Z"
    - latency: 4.894707ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:25:16Z"
    - latency: 2.883772ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:24:16Z"
    - latency: 7.480551ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:23:16Z"
    - latency: 6.523394ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:22:16Z"
    - latency: 8.577172ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:21:16Z"
    - latency: 11.718141ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.76.239:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T01:20:16Z"
kind: List
metadata:
  resourceVersion: ""