apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    generation: 132
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "38236"
    uid: fcfd652a-bdad-4007-a4f8-03079f51961a
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:26:34Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.45592ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 4.258284ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:32:34Z"
    - latency: 8.497718ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:31:34Z"
    - latency: 2.05947ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:30:34Z"
    - latency: 2.396368ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:29:34Z"
    - latency: 3.816603ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:28:34Z"
    - latency: 1.992448ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:27:34Z"
    - latency: 3.72662ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:26:34Z"
    - latency: 1.545158ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:25:34Z"
    - latency: 1.091996ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:24:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "36123"
    uid: c15de498-e716-4c9a-9c94-fe61a77ac2b0
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: 172.30.90.161:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:26:34Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.018063ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 2.269896ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:32:34Z"
    - latency: 5.29707ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:31:34Z"
    - latency: 3.66534ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:30:34Z"
    - latency: 2.424689ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:29:34Z"
    - latency: 6.54424ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:28:34Z"
    - latency: 2.127971ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:27:34Z"
    - latency: 5.521424ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:26:34Z"
    - latency: 2.840588ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:25:34Z"
    - latency: 1.387593ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.90.161:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:24:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "36120"
    uid: aada44ab-76da-4411-9ff9-a6a161056e5e
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:26:34Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.169459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 4.997661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:32:34Z"
    - latency: 4.236443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:31:34Z"
    - latency: 3.039155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:30:34Z"
    - latency: 2.013838ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:29:34Z"
    - latency: 6.826736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:28:34Z"
    - latency: 1.65541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:27:34Z"
    - latency: 3.397243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:26:34Z"
    - latency: 5.100423ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:25:34Z"
    - latency: 2.45922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:24:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "38127"
    uid: 829cfce6-85f9-492a-b5f2-264eab737a3f
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:25:34Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003964ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:37:34Z"
    - latency: 6.600612ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:37:34Z"
    - latency: 1.236011ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:36:34Z"
    - latency: 7.263707ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:36:34Z"
    - latency: 646.895µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:35:34Z"
    - latency: 8.782184ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:35:34Z"
    - latency: 716.778µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:34:34Z"
    - latency: 4.553101ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:34:34Z"
    - latency: 678.256µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 6.5161ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:33:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "38128"
    uid: 90cb10a4-413b-4a56-8a2b-4c2d9317e21c
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:25:34Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 357.06µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:37:34Z"
    - latency: 7.302378ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:37:34Z"
    - latency: 3.66199ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:36:34Z"
    - latency: 7.282397ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:36:34Z"
    - latency: 713.627µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:35:34Z"
    - latency: 8.624601ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:35:34Z"
    - latency: 221.646µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:34:34Z"
    - latency: 5.813522ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:34:34Z"
    - latency: 415.3µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 10.678321ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:33:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "36119"
    uid: 58301816-bdb2-482b-80bc-aa7f2880c985
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:26:34Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.770813ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 1.753332ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:32:34Z"
    - latency: 9.43331ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:31:34Z"
    - latency: 4.068958ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:30:34Z"
    - latency: 3.278421ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:29:34Z"
    - latency: 3.793943ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:28:34Z"
    - latency: 2.666104ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:27:34Z"
    - latency: 1.528437ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:26:34Z"
    - latency: 2.007538ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:25:34Z"
    - latency: 4.323705ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:24:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "38126"
    uid: 274ab9f6-54ec-4995-97df-60ee1f324eb6
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:25:34Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.353263ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:37:34Z"
    - latency: 3.805333ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:37:34Z"
    - latency: 1.533327ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:36:34Z"
    - latency: 2.703976ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:36:34Z"
    - latency: 3.25721ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:35:34Z"
    - latency: 3.479935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:35:34Z"
    - latency: 1.005495ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:34:34Z"
    - latency: 3.553096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:34:34Z"
    - latency: 1.660041ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 4.753177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-23T13:33:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "36118"
    uid: 5f5d41f0-7e23-4368-9548-5f585d385e24
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: 10.128.0.36:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:26:34Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.23677ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 1.813444ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:32:34Z"
    - latency: 8.849597ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:31:34Z"
    - latency: 4.486689ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:30:34Z"
    - latency: 2.830979ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:29:34Z"
    - latency: 6.595731ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:28:34Z"
    - latency: 1.912457ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:27:34Z"
    - latency: 1.297081ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:26:34Z"
    - latency: 1.270601ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:25:34Z"
    - latency: 4.367366ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:24:34Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-23T13:19:33Z"
    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: b53b2336-0704-4374-bbad-361d54a12f3b
    resourceVersion: "36121"
    uid: eb429d33-f99f-4d2f-8db6-270bafdabe02
  spec:
    sourcePod: network-check-source-58fb6744f5-b7dr8
    targetEndpoint: 172.30.119.95:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-23T13:26:34Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.314197ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:33:34Z"
    - latency: 5.421283ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:32:34Z"
    - latency: 9.598625ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:31:34Z"
    - latency: 4.216262ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:30:34Z"
    - latency: 3.099656ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:29:34Z"
    - latency: 3.884275ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:28:34Z"
    - latency: 2.709786ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:27:34Z"
    - latency: 5.593985ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:26:34Z"
    - latency: 5.079834ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:25:34Z"
    - latency: 6.096968ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.119.95:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-23T13:24:34Z"
kind: List
metadata:
  resourceVersion: ""