apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    generation: 231
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56933"
    uid: 8369597d-e0be-4000-96c1-8dae76412cc4
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: 192.168.32.10:17697
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:40:23Z"
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    failures:
    - latency: 2.005073ms
      message: 'kubernetes-apiserver-endpoint-master-0: failed to establish a TCP
        connection to 192.168.32.10:17697: dial tcp 192.168.32.10:17697: connect:
        connection refused'
      reason: TCPConnectError
      success: false
      time: "2026-02-16T17:34:23Z"
    outages:
    - end: "2026-02-16T17:35:23Z"
      endLogs:
      - latency: 5.35441ms
        message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
          succeeded'
        reason: TCPConnect
        success: true
        time: "2026-02-16T17:35:23Z"
      - latency: 2.005073ms
        message: 'kubernetes-apiserver-endpoint-master-0: failed to establish a TCP
          connection to 192.168.32.10:17697: dial tcp 192.168.32.10:17697: connect:
          connection refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
      message: Connectivity restored after 1m0.001442803s
      start: "2026-02-16T17:34:23Z"
      startLogs:
      - latency: 2.005073ms
        message: 'kubernetes-apiserver-endpoint-master-0: failed to establish a TCP
          connection to 192.168.32.10:17697: dial tcp 192.168.32.10:17697: connect:
          connection refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
    successes:
    - latency: 1.693875ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 2.383313ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 1.830989ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 2.459675ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 2.671401ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 1.874229ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:10:23Z"
    - latency: 1.90422ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:09:23Z"
    - latency: 3.429331ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:08:23Z"
    - latency: 2.65799ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:07:23Z"
    - latency: 4.820238ms
      message: 'kubernetes-apiserver-endpoint-master-0: tcp connection to 192.168.32.10:17697
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56937"
    uid: 0c2c97bb-dba3-4706-ac7b-3971243dd3e8
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: 172.30.21.89:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:40:23Z"
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    failures:
    - latency: 1.53314ms
      message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP connection
        to 172.30.21.89:443: dial tcp 172.30.21.89:443: connect: connection refused'
      reason: TCPConnectError
      success: false
      time: "2026-02-16T17:34:23Z"
    outages:
    - end: "2026-02-16T17:35:23Z"
      endLogs:
      - latency: 2.873385ms
        message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
          succeeded'
        reason: TCPConnect
        success: true
        time: "2026-02-16T17:35:23Z"
      - latency: 1.53314ms
        message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP
          connection to 172.30.21.89:443: dial tcp 172.30.21.89:443: connect: connection
          refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
      message: Connectivity restored after 1m0.000500358s
      start: "2026-02-16T17:34:23Z"
      startLogs:
      - latency: 1.53314ms
        message: 'kubernetes-apiserver-service-cluster: failed to establish a TCP
          connection to 172.30.21.89:443: dial tcp 172.30.21.89:443: connect: connection
          refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
    successes:
    - latency: 5.352842ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 2.64123ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 8.430023ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 7.528489ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 3.00231ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 2.186578ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:10:23Z"
    - latency: 2.224929ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:09:23Z"
    - latency: 2.734742ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:08:23Z"
    - latency: 3.140193ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:07:23Z"
    - latency: 5.082385ms
      message: 'kubernetes-apiserver-service-cluster: tcp connection to 172.30.21.89:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56934"
    uid: 875ffb11-30e9-400a-bd6c-67433e070e6b
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: 172.30.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:40:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    failures:
    - latency: 1.061778ms
      message: 'kubernetes-default-service-cluster-0: failed to establish a TCP connection
        to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection refused'
      reason: TCPConnectError
      success: false
      time: "2026-02-16T17:34:23Z"
    outages:
    - end: "2026-02-16T17:35:23Z"
      endLogs:
      - latency: 7.413665ms
        message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
          succeeded'
        reason: TCPConnect
        success: true
        time: "2026-02-16T17:35:23Z"
      - latency: 1.061778ms
        message: 'kubernetes-default-service-cluster-0: failed to establish a TCP
          connection to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection
          refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
      message: Connectivity restored after 1m0.000533009s
      start: "2026-02-16T17:34:23Z"
      startLogs:
      - latency: 1.061778ms
        message: 'kubernetes-default-service-cluster-0: failed to establish a TCP
          connection to 172.30.0.1:443: dial tcp 172.30.0.1:443: connect: connection
          refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
    successes:
    - latency: 4.501019ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 3.741789ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 2.838095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 2.878786ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 2.483696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 2.109736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:10:23Z"
    - latency: 2.061514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:09:23Z"
    - latency: 3.581095ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:08:23Z"
    - latency: 2.110756ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:07:23Z"
    - latency: 4.276734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.30.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56940"
    uid: f1c72f39-fef5-4e32-a6e4-e5cfe9a64f43
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: api.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:39:23Z"
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    failures:
    - latency: 283.487µs
      message: 'load-balancer-api-external: failed to establish a TCP connection to
        api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection
        refused'
      reason: TCPConnectError
      success: false
      time: "2026-02-16T17:34:23Z"
    outages:
    - end: "2026-02-16T17:35:23Z"
      endLogs:
      - latency: 1.423207ms
        message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
          succeeded'
        reason: TCPConnect
        success: true
        time: "2026-02-16T17:35:23Z"
      - latency: 283.487µs
        message: 'load-balancer-api-external: failed to establish a TCP connection
          to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection
          refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
      message: Connectivity restored after 59.996933784s
      start: "2026-02-16T17:34:23Z"
      startLogs:
      - latency: 283.487µs
        message: 'load-balancer-api-external: failed to establish a TCP connection
          to api.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection
          refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
    successes:
    - latency: 657.147µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 16.725932ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 439.932µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 8.614848ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 823.981µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 16.842435ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 2.403684ms
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 12.289295ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 909.314µs
      message: 'load-balancer-api-external: tcp connection to api.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 9.09237ms
      message: 'load-balancer-api-external: resolved host name api.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56939"
    uid: 8bc790f2-75b8-45b2-8983-7d3f53211f0b
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: api-int.sno.openstack.lab:6443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:39:23Z"
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    failures:
    - latency: 302.118µs
      message: 'load-balancer-api-internal: failed to establish a TCP connection to
        api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect: connection
        refused'
      reason: TCPConnectError
      success: false
      time: "2026-02-16T17:34:23Z"
    outages:
    - end: "2026-02-16T17:35:23Z"
      endLogs:
      - latency: 310.668µs
        message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
          succeeded'
        reason: TCPConnect
        success: true
        time: "2026-02-16T17:35:23Z"
      - latency: 302.118µs
        message: 'load-balancer-api-internal: failed to establish a TCP connection
          to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect:
          connection refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
      message: Connectivity restored after 1m0.005427398s
      start: "2026-02-16T17:34:23Z"
      startLogs:
      - latency: 302.118µs
        message: 'load-balancer-api-internal: failed to establish a TCP connection
          to api-int.sno.openstack.lab:6443: dial tcp 192.168.32.10:6443: connect:
          connection refused'
        reason: TCPConnectError
        success: false
        time: "2026-02-16T17:34:23Z"
    successes:
    - latency: 3.126343ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 10.111868ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 1.229363ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 8.091834ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 1.325725ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 15.576152ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 1.14844ms
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 11.71581ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 404.011µs
      message: 'load-balancer-api-internal: tcp connection to api-int.sno.openstack.lab:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 10.994281ms
      message: 'load-balancer-api-internal: resolved host name api-int.sno.openstack.lab
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56935"
    uid: 4db02346-2bf4-408c-abe4-d2716a3c70f0
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: 10.128.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:40:23Z"
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.671607ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 4.749745ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 1.979292ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 1.89545ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 2.64811ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 5.627118ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:10:23Z"
    - latency: 3.490642ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:09:23Z"
    - latency: 1.667935ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:08:23Z"
    - latency: 3.569345ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:07:23Z"
    - latency: 4.433978ms
      message: 'network-check-target-master-0: tcp connection to 10.128.0.4:8080 succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56932"
    uid: 59f3fe95-ff4c-41d4-909f-da907bdaa295
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:39:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.352249ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 4.671214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 2.031103ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 3.524643ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 3.954735ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 9.366407ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 2.460665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 3.404029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 2.188038ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 4.660753ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-02-16T18:11:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56936"
    uid: 2fb180a8-16ab-41b9-bf98-286690911205
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: 10.128.0.36:8443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:40:23Z"
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.889527ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 2.178827ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 8.171426ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 3.719228ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 2.845176ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 3.342248ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:10:23Z"
    - latency: 3.212565ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:09:23Z"
    - latency: 9.115442ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:08:23Z"
    - latency: 2.206409ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:07:23Z"
    - latency: 4.112139ms
      message: 'openshift-apiserver-endpoint-master-0: tcp connection to 10.128.0.36:8443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-02-16T17:33:23Z"
    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: da39ce92-6a7c-4cce-aa8b-3e495e33f616
    resourceVersion: "56938"
    uid: 03768486-1397-4cee-8453-d6f98ee4f5fd
  spec:
    sourcePod: network-check-source-7d8f4c8c66-qjq9w
    targetEndpoint: 172.30.176.78:443
  status:
    conditions:
    - lastTransitionTime: "2026-02-16T17:40:23Z"
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.878506ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:15:23Z"
    - latency: 3.616925ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:14:23Z"
    - latency: 9.46137ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:13:23Z"
    - latency: 3.77845ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:12:23Z"
    - latency: 3.150324ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:11:23Z"
    - latency: 4.53583ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:10:23Z"
    - latency: 3.050801ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:09:23Z"
    - latency: 9.079521ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:08:23Z"
    - latency: 2.083635ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:07:23Z"
    - latency: 4.307074ms
      message: 'openshift-apiserver-service-cluster: tcp connection to 172.30.176.78:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-02-16T18:06:23Z"
kind: List
metadata:
  resourceVersion: ""