apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    generation: 234
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46549"
    uid: 93419731-d4f7-4e0b-b84a-d9e4db4b6734
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:17: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.915212ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 4.219643ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 1.839898ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 2.119778ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 4.161574ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:41:15Z"
    - latency: 2.450139ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:40:15Z"
    - latency: 2.78758ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:39:15Z"
    - latency: 2.765529ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:38:15Z"
    - latency: 5.306931ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:37:15Z"
    - latency: 3.096ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46553"
    uid: e1c2fa30-ba5a-4c24-bf70-5e4bed7a7f42
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: 172.30.254.66:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:17:16Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.238614ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 2.734027ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 5.283988ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 2.736258ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 3.776803ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:41:15Z"
    - latency: 3.70931ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:40:15Z"
    - latency: 3.481533ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:39:15Z"
    - latency: 4.094301ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:38:15Z"
    - latency: 6.521131ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:37:15Z"
    - latency: 3.687749ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.254.66:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46551"
    uid: 13f593b9-f2e7-4726-99c5-e85e165222f6
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:17:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.043327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 5.029099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 1.976414ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 2.333855ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 1.958102ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:41:15Z"
    - latency: 5.361993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:40:15Z"
    - latency: 3.42485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:39:15Z"
    - latency: 4.573897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:38:15Z"
    - latency: 5.082714ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:37:15Z"
    - latency: 3.213334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46941"
    uid: 6141ca06-3d20-4f76-81ab-f6d9b7b1a00e
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:16:16Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.067815ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:46:16Z"
    - latency: 8.633224ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:46:15Z"
    - latency: 3.288025ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:16Z"
    - latency: 6.403474ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 612.669µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:16Z"
    - latency: 9.82553ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 1.465256ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:16Z"
    - latency: 7.58773ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 894.099µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:16Z"
    - latency: 6.656765ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:42:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46942"
    uid: a469e591-d6a6-4e59-9f8f-63c2952dcc23
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:16:16Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 927.159µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:46:16Z"
    - latency: 9.010477ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:46:15Z"
    - latency: 2.539431ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:16Z"
    - latency: 7.081646ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 555.318µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:16Z"
    - latency: 10.075098ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 1.300121ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:16Z"
    - latency: 7.481447ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 1.374354ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:16Z"
    - latency: 6.270922ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:42:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46554"
    uid: 1cc23647-6923-4415-a237-64612e7f3bf0
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:17:15Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.019738ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 2.987375ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 8.129298ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 4.073362ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 2.406357ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:41:15Z"
    - latency: 2.49404ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:40:15Z"
    - latency: 8.764782ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:39:15Z"
    - latency: 7.331896ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:38:15Z"
    - latency: 10.569021ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:37:15Z"
    - latency: 4.772004ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46940"
    uid: ad4da75a-96da-4ba0-815d-7c54b485a14d
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:16:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.525329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:46:16Z"
    - latency: 3.949685ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:46:15Z"
    - latency: 3.693288ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 3.343707ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 1.673772ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:16Z"
    - latency: 7.419414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 5.06237ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 4.071059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 6.284353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 2.742929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2025-12-04T12:42:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46550"
    uid: ff335fb0-4c2d-44fe-a981-ee3f828e3d74
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: 10.128.0.42:8443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:17:16Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.12551ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 3.82497ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 3.817072ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 3.912317ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 2.617235ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:41:15Z"
    - latency: 4.008129ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:40:15Z"
    - latency: 5.004501ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:39:15Z"
    - latency: 3.639347ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:38:15Z"
    - latency: 10.665614ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:37:15Z"
    - latency: 4.737622ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.42:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:36:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2025-12-04T12:10:14Z"
    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: 9618c86a-8a87-4c00-8dd2-9747684d64b3
    resourceVersion: "46552"
    uid: fa7b917e-4231-4bc8-91a8-b49a7395ae0d
  spec:
    sourcePod: network-check-source-85d8db45d4-5bjlq
    targetEndpoint: 172.30.182.44:443
  status:
    conditions:
    - lastTransitionTime: "2025-12-04T12:17:16Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.363296ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:45:15Z"
    - latency: 2.152948ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:44:15Z"
    - latency: 3.070307ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:43:15Z"
    - latency: 4.251768ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:42:15Z"
    - latency: 2.073037ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:41:15Z"
    - latency: 4.205955ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:40:15Z"
    - latency: 3.942346ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:39:15Z"
    - latency: 4.099842ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:38:15Z"
    - latency: 10.945373ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:37:15Z"
    - latency: 5.429715ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.182.44:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2025-12-04T12:36:15Z"
kind: List
metadata:
  resourceVersion: ""