apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "18617"
    uid: 419b483e-fa60-4163-a973-017514f77e85
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 810.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 1.12878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:07Z"
    - latency: 826.865µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:07Z"
    - latency: 1.114449ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:09:07Z"
    - latency: 1.063197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:08:07Z"
    - latency: 878.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:07:07Z"
    - latency: 916.952µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:06:07Z"
    - latency: 1.371956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:05:07Z"
    - latency: 863.939µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:04:07Z"
    - latency: 1.243869ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:03:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "20749"
    uid: 63406b7f-121c-4dc2-9079-7910a18d1dea
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:04:07Z"
      message: 'load-balancer-api-external: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.171495ms
      message: 'load-balancer-api-external: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:07Z"
    - latency: 7.432204ms
      message: 'load-balancer-api-external: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:16:07Z"
    - latency: 6.663089ms
      message: 'load-balancer-api-external: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:07Z"
    - latency: 7.073199ms
      message: 'load-balancer-api-external: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:15:07Z"
    - latency: 4.090899ms
      message: 'load-balancer-api-external: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:07Z"
    - latency: 6.618455ms
      message: 'load-balancer-api-external: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:14:07Z"
    - latency: 6.399153ms
      message: 'load-balancer-api-external: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:07Z"
    - latency: 7.639015ms
      message: 'load-balancer-api-external: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:13:07Z"
    - latency: 5.703241ms
      message: 'load-balancer-api-external: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 6.604671ms
      message: 'load-balancer-api-external: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:12:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "20748"
    uid: cab901f4-7d76-4c30-98f8-68ca1733b343
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:04:07Z"
      message: 'load-balancer-api-internal: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.117392ms
      message: 'load-balancer-api-internal: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:07Z"
    - latency: 7.468776ms
      message: 'load-balancer-api-internal: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:16:07Z"
    - latency: 6.666059ms
      message: 'load-balancer-api-internal: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:07Z"
    - latency: 7.119793ms
      message: 'load-balancer-api-internal: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:15:07Z"
    - latency: 3.778972ms
      message: 'load-balancer-api-internal: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:07Z"
    - latency: 6.661785ms
      message: 'load-balancer-api-internal: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:14:07Z"
    - latency: 3.558614ms
      message: 'load-balancer-api-internal: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:07Z"
    - latency: 7.703198ms
      message: 'load-balancer-api-internal: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:13:07Z"
    - latency: 5.56615ms
      message: 'load-balancer-api-internal: tcp connection to a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 6.673103ms
      message: 'load-balancer-api-internal: resolved host name a795ea6d85fa545579f0401bc09884af-cb7d424b29f6becf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:12:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-network-check-target-ip-10-0-141-195
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "18614"
    uid: a034dffa-0c23-401a-baf5-c764fd383835
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:07Z"
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 817.255µs
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 1.044311ms
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:07Z"
    - latency: 970.069µs
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:07Z"
    - latency: 807.783µs
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:09:07Z"
    - latency: 1.198558ms
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:08:07Z"
    - latency: 878.479µs
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:07:07Z"
    - latency: 1.013263ms
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:06:07Z"
    - latency: 1.477597ms
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:05:07Z"
    - latency: 1.306191ms
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:04:07Z"
    - latency: 1.557701ms
      message: 'network-check-target-ip-10-0-141-195: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:03:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-network-check-target-ip-10-0-142-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "18615"
    uid: c7a62325-790d-49c3-9168-007b32a0a950
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:07Z"
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.303636ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 2.375583ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:07Z"
    - latency: 2.382545ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:07Z"
    - latency: 2.245976ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:09:07Z"
    - latency: 2.495473ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:08:07Z"
    - latency: 2.254487ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:07:07Z"
    - latency: 2.315054ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:06:07Z"
    - latency: 2.556914ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:05:07Z"
    - latency: 2.488365ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:04:07Z"
    - latency: 2.624499ms
      message: 'network-check-target-ip-10-0-142-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:03:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-network-check-target-ip-10-0-142-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "18616"
    uid: 33d8b0d9-40da-489d-9a4c-9eb831262ae4
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:05:07Z"
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.227129ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 2.294458ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:11:07Z"
    - latency: 1.934312ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:10:07Z"
    - latency: 2.357211ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:09:07Z"
    - latency: 2.11932ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:08:07Z"
    - latency: 1.950072ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:07:07Z"
    - latency: 2.357966ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:06:07Z"
    - latency: 1.898628ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:05:07Z"
    - latency: 2.356776ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:04:07Z"
    - latency: 2.779677ms
      message: 'network-check-target-ip-10-0-142-86: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:03:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T14:58:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-195-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-195.ec2.internal
      uid: 23bf1bb4-389d-4144-974a-a234f35f6c8d
    resourceVersion: "20746"
    uid: 432c34c3-23a8-4bcd-bf7f-9dceb11ce55b
  spec:
    sourcePod: network-check-source-7b678d77c7-8d689
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T15:04:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.031111ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:16:07Z"
    - latency: 1.654939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:16:07Z"
    - latency: 890.063µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:15:07Z"
    - latency: 1.449869ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:15:07Z"
    - latency: 823.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:14:07Z"
    - latency: 1.667787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:14:07Z"
    - latency: 1.307276ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:13:07Z"
    - latency: 2.12359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:13:07Z"
    - latency: 874.344µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T15:12:07Z"
    - latency: 1.739075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T15:12:07Z"
kind: List
metadata:
  resourceVersion: ""