apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15:06Z"
    generation: 288
    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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68124"
    uid: 7a0f745a-cd5b-4050-a26d-f38f88bb515d
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:22:07Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.572299ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 2.078996ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 1.755096ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 2.468017ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 2.267111ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 1.988552ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:34:07Z"
    - latency: 1.428224ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:33:07Z"
    - latency: 1.649772ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:32:07Z"
    - latency: 3.84206ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:31:07Z"
    - latency: 3.854511ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68127"
    uid: 86def102-e5b9-40dc-a32a-4f0fae901d46
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: 172.30.169.2:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:22:07Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.505549ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 2.458467ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 1.425465ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 2.276441ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 3.989004ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 2.918751ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:34:07Z"
    - latency: 2.704965ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:33:07Z"
    - latency: 2.029864ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:32:07Z"
    - latency: 2.732796ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:31:07Z"
    - latency: 5.73946ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.169.2:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68125"
    uid: cdb4402b-3446-4beb-98e8-d04510b70854
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:22:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.438535ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 1.684252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 2.363544ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 2.296591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 2.122336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 1.862048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:34:07Z"
    - latency: 1.236729ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:33:07Z"
    - latency: 2.614652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:32:07Z"
    - latency: 1.140446ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:31:07Z"
    - latency: 3.894882ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68132"
    uid: c4b487e3-e790-4913-a82f-f0dec429cbfe
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:21:07Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.560021ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 13.956737ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 991.731µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 12.262564ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 774.184µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 7.33728ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 696.393µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 9.001172ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 580.679µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 9.445445ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:35:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68133"
    uid: de73c26b-bdd8-44e9-82fa-d89b562a2610
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:21:07Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 290.349µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 17.416385ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 1.55946ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 11.577173ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 927.94µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 7.698641ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 828.146µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 9.075425ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 1.743215ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 9.981032ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:35:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15:06Z"
    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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68131"
    uid: 4b2bf405-5dd1-4d57-a57e-a1a6d1dae55d
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:22:07Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.967472ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 3.607634ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 1.905199ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 2.433937ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 4.454619ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 5.161372ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:34:07Z"
    - latency: 2.094066ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:33:07Z"
    - latency: 2.606452ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:32:07Z"
    - latency: 2.912981ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:31:07Z"
    - latency: 5.690999ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68129"
    uid: 41d51eb1-268a-4ef0-8aa6-2ecbc2f180fb
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:21:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.958033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 3.19552ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 2.042973ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 2.381544ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 1.005492ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 4.972305ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 1.220109ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 2.770487ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 896.228µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 6.811763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-03T23:35:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68128"
    uid: 47cb4609-8584-4360-a382-32078dfba3d0
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: 10.128.0.33:8443
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:22:07Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.5191ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 1.798167ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 2.971053ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 3.210771ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 3.633684ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 4.585663ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:34:07Z"
    - latency: 2.999954ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:33:07Z"
    - latency: 2.208509ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:32:07Z"
    - latency: 2.490348ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:31:07Z"
    - latency: 3.273002ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.33:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:30:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-03T22:15: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: 4b803739-f301-4b6d-80bd-2ffa2100c90b
    resourceVersion: "68130"
    uid: 018b0e1a-a0f7-4b57-bce4-80e5d4e7d815
  spec:
    sourcePod: network-check-source-6964bb78b7-lntt5
    targetEndpoint: 172.30.213.13:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-03T22:22:07Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.994524ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:39:07Z"
    - latency: 3.559462ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:38:07Z"
    - latency: 2.080485ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:37:07Z"
    - latency: 3.700487ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:36:07Z"
    - latency: 3.349115ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:35:07Z"
    - latency: 3.405956ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:34:07Z"
    - latency: 3.152409ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:33:07Z"
    - latency: 1.866978ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:32:07Z"
    - latency: 2.746556ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:31:07Z"
    - latency: 2.388404ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.213.13:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-03T23:30:07Z"
kind: List
metadata:
  resourceVersion: ""