apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    generation: 147
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "37199"
    uid: 9a7c2a65-2f8a-4bb6-8d8a-83aa530e254d
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:44:38Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.489955ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:51:38Z"
    - latency: 1.941586ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:50:38Z"
    - latency: 2.487252ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 2.167924ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 2.786879ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 2.167604ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 5.384004ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 2.246416ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:44:38Z"
    - latency: 1.411765ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:43:38Z"
    - latency: 2.210045ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:42:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "37201"
    uid: a634f3c6-26f3-4bb1-a41b-375eeb45ce53
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: 172.30.133.107:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:44:38Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.187466ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:51:38Z"
    - latency: 3.301878ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:50:38Z"
    - latency: 4.06669ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 2.504632ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 2.834381ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 2.688907ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 2.868402ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 2.860401ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:44:38Z"
    - latency: 1.730714ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:43:38Z"
    - latency: 7.733163ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.133.107:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:42:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:36Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "37200"
    uid: 48db0aaa-f83d-4f73-bc44-e19e3db01d7d
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:44:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.950591ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:51:38Z"
    - latency: 2.759246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:50:38Z"
    - latency: 3.850995ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 2.43452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 1.962609ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 2.700198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 2.233825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 1.886578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:44:38Z"
    - latency: 2.570245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:43:38Z"
    - latency: 5.459156ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:42:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "35111"
    uid: 1487ba36-c6d0-4f03-9cd0-0b5d02f794ee
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:43:38Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 589.305µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 15.249977ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 205.355µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 14.216321ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 950.754µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 12.917682ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 2.234326ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 7.882696ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 790.769µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 14.757278ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "35112"
    uid: 77c9de7c-7214-40e8-8778-9bba347e455c
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:43:38Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.302µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 15.669558ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 995.404µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 12.072989ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 491.922µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 12.997064ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 173.605µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 11.597889ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 1.646801ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 14.885131ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "37198"
    uid: 4b0cf4c9-c2d0-4f1a-835d-9ded0ee621fa
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:44:38Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019134ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:51:38Z"
    - latency: 3.405981ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:50:38Z"
    - latency: 4.073201ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 908.553µs
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 6.451271ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 4.134924ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 7.762594ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 4.598775ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:44:38Z"
    - latency: 2.545523ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:43:38Z"
    - latency: 1.546359ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:42:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "35110"
    uid: 825c84b7-a533-4cf3-bcce-7f2ea8d96ed6
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:43:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.777363ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 9.218928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 1.819215ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 7.411513ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 3.487757ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 6.746379ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 3.028985ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 2.935873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 4.481871ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 7.018385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-12T18:45:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "37203"
    uid: c7828264-d5de-4836-ab21-1730f9269b38
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: 10.128.0.37:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:44:38Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.93552ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:51:38Z"
    - latency: 2.858468ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:50:38Z"
    - latency: 4.420569ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 7.469885ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 5.239191ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 2.056862ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 2.80005ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 1.899517ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:44:38Z"
    - latency: 2.367739ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:43:38Z"
    - latency: 10.671046ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.37:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:42:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-12T18:37:37Z"
    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: 2b794e11-4c79-4c26-ab97-24c47eefd23d
    resourceVersion: "37202"
    uid: a89cb4c0-bbd7-4bfb-9757-8ad8cad1a2b3
  spec:
    sourcePod: network-check-source-7c67b67d47-g4dkj
    targetEndpoint: 172.30.173.174:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-12T18:44:38Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.817197ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:51:38Z"
    - latency: 3.669068ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:50:38Z"
    - latency: 4.533032ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:49:38Z"
    - latency: 7.383233ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:48:38Z"
    - latency: 6.664166ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:47:38Z"
    - latency: 5.722353ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:46:38Z"
    - latency: 6.888562ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:45:38Z"
    - latency: 1.59578ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:44:38Z"
    - latency: 1.863667ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:43:38Z"
    - latency: 10.229135ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.173.174:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-12T18:42:38Z"
kind: List
metadata:
  resourceVersion: ""