apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "68326"
    uid: 1c3ed51b-a714-4f21-988e-9123623fc3bf
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:55:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 896.875µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 1.320082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 1.156338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 1.149397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 1.181111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:58Z"
    - latency: 862.863µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:58Z"
    - latency: 1.20753ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:58Z"
    - latency: 949.814µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:58Z"
    - latency: 1.608001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:58Z"
    - latency: 1.113845ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "69180"
    uid: 969cdaeb-8fee-451d-9f7d-4647a8bae264
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:58Z"
      message: 'load-balancer-api-external: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.960688ms
      message: 'load-balancer-api-external: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:24:58Z"
    - latency: 8.596727ms
      message: 'load-balancer-api-external: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:24:58Z"
    - latency: 4.349294ms
      message: 'load-balancer-api-external: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 8.451545ms
      message: 'load-balancer-api-external: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 3.960742ms
      message: 'load-balancer-api-external: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 10.176576ms
      message: 'load-balancer-api-external: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 3.897554ms
      message: 'load-balancer-api-external: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 11.595618ms
      message: 'load-balancer-api-external: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 3.053733ms
      message: 'load-balancer-api-external: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 7.574ms
      message: 'load-balancer-api-external: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:20:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "69179"
    uid: 6af50908-9d6d-4ea5-a9c0-7aebacb2d653
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:58Z"
      message: 'load-balancer-api-internal: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.931933ms
      message: 'load-balancer-api-internal: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:24:58Z"
    - latency: 8.508249ms
      message: 'load-balancer-api-internal: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:24:58Z"
    - latency: 4.451367ms
      message: 'load-balancer-api-internal: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 8.360301ms
      message: 'load-balancer-api-internal: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 4.594136ms
      message: 'load-balancer-api-internal: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 10.075209ms
      message: 'load-balancer-api-internal: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 3.940594ms
      message: 'load-balancer-api-internal: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 11.529307ms
      message: 'load-balancer-api-internal: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 3.036372ms
      message: 'load-balancer-api-internal: tcp connection to aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 7.500069ms
      message: 'load-balancer-api-internal: resolved host name aa2eac67c5bc442fbb990a2ec8bb7c48-23bdf5015e3baab8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:20:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-network-check-target-ip-10-0-128-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "68323"
    uid: 0e9df9b8-1847-4d9d-b20a-bfda8b5a3e2c
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:55:58Z"
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 939.32µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 1.541639ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 1.127002ms
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 928.026µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 971.738µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:58Z"
    - latency: 868.572µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:58Z"
    - latency: 981.141µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:58Z"
    - latency: 967.506µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:58Z"
    - latency: 948.388µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:58Z"
    - latency: 962.415µs
      message: 'network-check-target-ip-10-0-128-141: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-network-check-target-ip-10-0-132-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "68324"
    uid: 1c089df6-a19b-4740-bcaf-ee9fd1760779
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:55:58Z"
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.000536ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 2.348515ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 2.127501ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 2.494056ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 2.655165ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:58Z"
    - latency: 2.402406ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:58Z"
    - latency: 1.998183ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:58Z"
    - latency: 2.235248ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:58Z"
    - latency: 2.295559ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:58Z"
    - latency: 2.172233ms
      message: 'network-check-target-ip-10-0-132-244: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-network-check-target-ip-10-0-132-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "68325"
    uid: 57357622-b270-4acd-8596-90a5929ffe55
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:55:58Z"
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.939558ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 2.284601ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 2.740336ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 2.406644ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 2.800246ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:19:58Z"
    - latency: 2.254009ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:18:58Z"
    - latency: 2.496117ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:17:58Z"
    - latency: 2.178472ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:16:58Z"
    - latency: 1.993644ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:15:58Z"
    - latency: 2.239828ms
      message: 'network-check-target-ip-10-0-132-83: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:14:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T13:48:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-141-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-141.ec2.internal
      uid: 487363e0-5704-4da4-8f42-c8ac3c0535a4
    resourceVersion: "69177"
    uid: 34e3c313-47a6-46aa-aa36-3db5812f62d5
  spec:
    sourcePod: network-check-source-7cbc45fddc-x95zg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T13:54:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 948.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:24:58Z"
    - latency: 1.689478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:24:58Z"
    - latency: 1.058214ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 2.126965ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:23:58Z"
    - latency: 932.391µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 1.774154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:22:58Z"
    - latency: 1.144563ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 1.768837ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:21:58Z"
    - latency: 861.696µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T14:20:58Z"
    - latency: 2.451651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T14:20:58Z"
kind: List
metadata:
  resourceVersion: ""