apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    generation: 336
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "76565"
    uid: d32ed12a-d0d1-4b49-af58-0e9b080a1f26
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:03:25Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.081568ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:27:25Z"
    - latency: 2.552743ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 2.082869ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 2.774029ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 1.686138ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 2.80317ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 5.084474ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:21:25Z"
    - latency: 2.516881ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:20:25Z"
    - latency: 5.559488ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:19:25Z"
    - latency: 3.375216ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:18:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "76562"
    uid: d0ebad45-c619-44ba-8609-dd69f441ac47
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: 172.30.206.130:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:03:25Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.015966ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:27:25Z"
    - latency: 3.17047ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 3.608412ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 2.569883ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 1.923985ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 3.620463ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 4.888429ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:21:25Z"
    - latency: 1.945965ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:20:25Z"
    - latency: 4.465087ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:19:25Z"
    - latency: 2.964014ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.206.130:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:18:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "76563"
    uid: 1cb3e2f8-cbe1-46b4-b33f-d438d93dc5d5
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:03:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.124541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:27:25Z"
    - latency: 2.841791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 3.360545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 2.666966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 1.953245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 2.938614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 4.932081ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:21:25Z"
    - latency: 1.542294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:20:25Z"
    - latency: 5.244169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:19:25Z"
    - latency: 2.432579ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:18:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "75997"
    uid: d509c45f-ad6e-489a-aac8-f516a12e4050
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:02:25Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 672.049µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 8.900763ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 679.759µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 13.300398ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 609.727µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 8.584524ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 1.05353ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 7.762171ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 1.590155ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 10.974922ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:22:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "75998"
    uid: f217d67a-62f5-4dc6-98b8-ed3f570ba460
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:02:25Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 228.217µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 13.243216ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 526.005µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 13.467633ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 1.481202ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 7.981157ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 587.036µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 7.603356ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 740.051µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 11.743343ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:22:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "76566"
    uid: 4c3125cc-058d-489f-bbdf-97f917850c97
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: 10.128.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:03:25Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.849515ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:27:25Z"
    - latency: 3.083577ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 5.411723ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 2.48311ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 4.429816ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 3.967883ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 6.108684ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:21:25Z"
    - latency: 4.92346ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:20:25Z"
    - latency: 4.55004ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:19:25Z"
    - latency: 5.398734ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.3:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:18:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "75996"
    uid: 41d86a22-f91a-43fd-86a7-bdbb5d14b346
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:02:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.312096ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 4.624001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 1.274447ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 9.50538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 1.42006ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 7.227335ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 1.309428ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 5.524307ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 2.479681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 7.350219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-03-20T10:22:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "76561"
    uid: 2f19ff61-7860-4edf-87a9-769523899747
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: 10.128.0.43:8443
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:03:25Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.452312ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:27:25Z"
    - latency: 3.040537ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 5.62489ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 2.562852ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 4.378405ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 1.592325ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 2.098619ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:21:25Z"
    - latency: 2.834431ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:20:25Z"
    - latency: 4.55858ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:19:25Z"
    - latency: 5.644371ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.43:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:18:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-03-20T08:56:24Z"
    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: 7bc50120-3879-4454-8162-ec2f348aada5
    resourceVersion: "76564"
    uid: 3d22db9a-30a7-4019-9df9-fa1e603cb5d2
  spec:
    sourcePod: network-check-source-b4bf74f6-fhvg6
    targetEndpoint: 172.30.13.250:443
  status:
    conditions:
    - lastTransitionTime: "2026-03-20T09:03:25Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.15694ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:27:25Z"
    - latency: 3.444437ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:26:25Z"
    - latency: 5.390983ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:25:25Z"
    - latency: 2.483781ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:24:25Z"
    - latency: 3.586272ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:23:25Z"
    - latency: 3.51419ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:22:25Z"
    - latency: 1.367369ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:21:25Z"
    - latency: 4.788176ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:20:25Z"
    - latency: 4.817767ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:19:25Z"
    - latency: 5.199298ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.13.250:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-03-20T10:18:25Z"
kind: List
metadata:
  resourceVersion: ""