apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42:06Z"
    generation: 201
    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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "47252"
    uid: 6a5921db-e6ef-4cec-a4e6-c0e302c0e500
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:49:07Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.517456ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 1.361043ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 2.072241ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 1.715642ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 2.607594ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:13:07Z"
    - latency: 2.707276ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:12:07Z"
    - latency: 1.22522ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:11:07Z"
    - latency: 1.957328ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:10:07Z"
    - latency: 5.602158ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:09:07Z"
    - latency: 2.45553ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "45914"
    uid: a1c0e178-6380-43d8-be04-3fc7a540742a
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: 172.30.238.176:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:49:07Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.934641ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 4.153802ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 4.673924ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 2.505021ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 940.513µs
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:13:07Z"
    - latency: 2.84984ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:12:07Z"
    - latency: 2.988693ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:11:07Z"
    - latency: 8.99217ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:10:07Z"
    - latency: 5.104145ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:09:07Z"
    - latency: 3.431024ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.238.176:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "45913"
    uid: 818b4ddf-2867-485d-894f-88835fc73627
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:49:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.549947ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 3.70408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 2.015589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 2.257225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 3.67618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:13:07Z"
    - latency: 4.318365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:12:07Z"
    - latency: 3.355452ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:11:07Z"
    - latency: 6.422357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:10:07Z"
    - latency: 5.3169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:09:07Z"
    - latency: 3.616598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "46420"
    uid: fa9db1b4-a8ad-4350-843a-f674e29bff03
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:48:07Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 960.813µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:18:07Z"
    - latency: 11.952153ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:18:07Z"
    - latency: 406.83µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 20.151483ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 608.815µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 7.015672ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 1.590169ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 10.685612ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 992.305µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 9.276967ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "46419"
    uid: 9aaa5368-3fa0-4d3b-81a5-85f2f864f2b1
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:48:07Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 457.782µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:18:07Z"
    - latency: 12.389683ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:18:07Z"
    - latency: 1.344043ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 15.489939ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 717.347µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 6.828168ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 416.13µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 13.710385ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 948.283µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 9.285427ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "45912"
    uid: 7dad7198-8435-4ca5-9a45-dce4f6e95edd
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:49:07Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.526215ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 3.639739ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 4.297395ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 3.959636ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 2.43885ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:13:07Z"
    - latency: 4.856878ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:12:07Z"
    - latency: 5.661488ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:11:07Z"
    - latency: 3.940557ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:10:07Z"
    - latency: 3.035664ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:09:07Z"
    - latency: 12.316262ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "46418"
    uid: 42e2ed4a-663b-4fec-88bc-9eebb7df6dc1
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:48:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.548763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:18:07Z"
    - latency: 2.767358ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:18:07Z"
    - latency: 9.704248ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 6.249763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 1.406204ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 3.758522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 1.942068ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 7.689128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 1.750063ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 3.619759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-08T01:14:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "45917"
    uid: 29c0acb5-873b-4e0e-a192-37789c0dd08e
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: 10.128.0.39:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:49:07Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.410782ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 3.500655ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 4.212363ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 2.219925ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 3.423804ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:13:07Z"
    - latency: 5.110255ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:12:07Z"
    - latency: 2.816389ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:11:07Z"
    - latency: 2.797549ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:10:07Z"
    - latency: 2.934872ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:09:07Z"
    - latency: 3.692441ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.39:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:08:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-08T00:42: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: ed785f20-6908-4beb-b0f9-266862a1d3d1
    resourceVersion: "45915"
    uid: ec159fbb-2358-4c70-83ad-c030ea6b0b1f
  spec:
    sourcePod: network-check-source-7c67b67d47-sctv9
    targetEndpoint: 172.30.240.116:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-08T00:49:07Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.879544ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:17:07Z"
    - latency: 3.739972ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:16:07Z"
    - latency: 2.395558ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:15:07Z"
    - latency: 2.541502ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:14:07Z"
    - latency: 1.996819ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:13:07Z"
    - latency: 5.440803ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:12:07Z"
    - latency: 8.619711ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:11:07Z"
    - latency: 1.086557ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:10:07Z"
    - latency: 3.577328ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:09:07Z"
    - latency: 10.281572ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.240.116:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-08T01:08:07Z"
kind: List
metadata:
  resourceVersion: ""