apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17835"
    uid: 4eacf723-7ef3-481b-89d8-6d572e152e0e
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:55:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 753.878µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:02:56Z"
    - latency: 1.022706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:01:56Z"
    - latency: 950.196µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 965.817µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 838.408µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 1.202991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 1.284181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 1.172174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:55:56Z"
    - latency: 1.049389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:54:56Z"
    - latency: 881.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:53:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17172"
    uid: 2be3fbb5-ba4a-44a4-94b1-91153cd01699
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:54:56Z"
      message: 'load-balancer-api-external: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.440871ms
      message: 'load-balancer-api-external: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 8.230866ms
      message: 'load-balancer-api-external: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 5.01671ms
      message: 'load-balancer-api-external: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 7.992067ms
      message: 'load-balancer-api-external: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 4.574008ms
      message: 'load-balancer-api-external: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 7.67906ms
      message: 'load-balancer-api-external: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 3.889714ms
      message: 'load-balancer-api-external: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 8.242847ms
      message: 'load-balancer-api-external: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 5.601623ms
      message: 'load-balancer-api-external: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 8.966224ms
      message: 'load-balancer-api-external: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:56:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17171"
    uid: a2323cf8-d68d-428d-a558-79a7b73be131
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:54:56Z"
      message: 'load-balancer-api-internal: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.233628ms
      message: 'load-balancer-api-internal: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 8.18531ms
      message: 'load-balancer-api-internal: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 5.002881ms
      message: 'load-balancer-api-internal: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 8.023025ms
      message: 'load-balancer-api-internal: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 4.644077ms
      message: 'load-balancer-api-internal: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 7.624515ms
      message: 'load-balancer-api-internal: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 4.940063ms
      message: 'load-balancer-api-internal: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 8.276685ms
      message: 'load-balancer-api-internal: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 5.14068ms
      message: 'load-balancer-api-internal: tcp connection to ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 8.890365ms
      message: 'load-balancer-api-internal: resolved host name ac0cc48cd3f064e178a1883102e0a054-a291affdb0261b09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:56:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-network-check-target-ip-10-0-136-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17834"
    uid: 6a588c60-fd3b-4a98-b482-b28cc9f21a73
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:55:56Z"
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.063337ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:02:56Z"
    - latency: 2.240835ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:01:56Z"
    - latency: 2.379618ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 2.162797ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 2.273212ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 2.027072ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 1.998367ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 2.159713ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:55:56Z"
    - latency: 1.84633ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:54:56Z"
    - latency: 2.174118ms
      message: 'network-check-target-ip-10-0-136-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:53:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-network-check-target-ip-10-0-139-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17832"
    uid: 562d92ac-b3ce-4f52-84fc-f3696944e13f
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:55:56Z"
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075778ms
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:02:56Z"
    - latency: 864.926µs
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:01:56Z"
    - latency: 872.542µs
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 1.15008ms
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 724.511µs
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 1.10881ms
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 798.767µs
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 1.03977ms
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:55:56Z"
    - latency: 810.539µs
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:54:56Z"
    - latency: 788.779µs
      message: 'network-check-target-ip-10-0-139-37: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:53:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-network-check-target-ip-10-0-141-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17833"
    uid: 2384a705-9773-4c80-a5a4-9cabd11e3781
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:55:56Z"
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.946612ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:02:56Z"
    - latency: 2.279235ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:01:56Z"
    - latency: 1.815102ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 1.771591ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 1.619906ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 1.779514ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 2.343568ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 1.838101ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:55:56Z"
    - latency: 1.840432ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:54:56Z"
    - latency: 1.80819ms
      message: 'network-check-target-ip-10-0-141-135: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:53:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T06:48:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-37.ec2.internal
      uid: 7e327d58-49e2-4aa8-9885-79379259287f
    resourceVersion: "17170"
    uid: 89a8e532-c47f-4077-898e-b759a4cb3ee2
  spec:
    sourcePod: network-check-source-dbd9cf844-pwdw9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T06:54:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.107µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 2.076704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T07:00:56Z"
    - latency: 1.103112ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 1.63097ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:59:56Z"
    - latency: 877.094µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 1.657021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:58:56Z"
    - latency: 1.018395ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 1.821121ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:57:56Z"
    - latency: 872.381µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T06:56:56Z"
    - latency: 2.1253ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T06:56:56Z"
kind: List
metadata:
  resourceVersion: ""