apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32043"
    uid: dfcf7398-ece7-490d-b90c-055dbf976564
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:40:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 1.029771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 1.418365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 1.060707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 1.01771ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 1.047595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:13Z"
    - latency: 1.155638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:09:13Z"
    - latency: 1.269822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:08:13Z"
    - latency: 953.819µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:07:13Z"
    - latency: 1.026744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:06:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32044"
    uid: 593b984b-4159-49cc-8f45-2f10642472f2
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:39:13Z"
      message: 'load-balancer-api-external: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.577041ms
      message: 'load-balancer-api-external: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 6.312178ms
      message: 'load-balancer-api-external: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 4.543776ms
      message: 'load-balancer-api-external: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 8.138552ms
      message: 'load-balancer-api-external: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 4.457318ms
      message: 'load-balancer-api-external: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 6.366104ms
      message: 'load-balancer-api-external: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 5.461111ms
      message: 'load-balancer-api-external: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 6.95259ms
      message: 'load-balancer-api-external: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 4.733382ms
      message: 'load-balancer-api-external: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 6.5062ms
      message: 'load-balancer-api-external: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:11:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32045"
    uid: 25544b3d-6aa3-43f3-a6ba-d98d64b79fdf
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:39:13Z"
      message: 'load-balancer-api-internal: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.119229ms
      message: 'load-balancer-api-internal: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 6.220932ms
      message: 'load-balancer-api-internal: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 4.464036ms
      message: 'load-balancer-api-internal: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 8.097289ms
      message: 'load-balancer-api-internal: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 4.430276ms
      message: 'load-balancer-api-internal: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 6.294347ms
      message: 'load-balancer-api-internal: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 5.482512ms
      message: 'load-balancer-api-internal: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 6.901347ms
      message: 'load-balancer-api-internal: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 4.876519ms
      message: 'load-balancer-api-internal: tcp connection to ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 6.420147ms
      message: 'load-balancer-api-internal: resolved host name ae00b0a575fcf49a3911c11bae80efbc-4981c18b028d9b59.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:11:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-network-check-target-ip-10-0-130-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32039"
    uid: 5fea1095-17f5-4780-86fe-2002afc38e39
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:40:13Z"
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.972502ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 2.218913ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 2.45768ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 2.202197ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 2.305365ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 2.506132ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:13Z"
    - latency: 2.307208ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:09:13Z"
    - latency: 2.36543ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:08:13Z"
    - latency: 2.740848ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:07:13Z"
    - latency: 2.43805ms
      message: 'network-check-target-ip-10-0-130-23: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:06:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-network-check-target-ip-10-0-140-68
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32041"
    uid: 9c335a09-7f97-47f9-9154-7d34c1663baa
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:40:13Z"
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.103287ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 1.947634ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 1.872315ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 2.037618ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 2.008395ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 2.040524ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:13Z"
    - latency: 1.926755ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:09:13Z"
    - latency: 1.856573ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:08:13Z"
    - latency: 1.91597ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:07:13Z"
    - latency: 1.988438ms
      message: 'network-check-target-ip-10-0-140-68: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:06:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-network-check-target-ip-10-0-143-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32040"
    uid: 693edc6e-af94-4525-af43-cb00d2a63ff1
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:40:13Z"
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.764µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 1.306131ms
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 1.038396ms
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 976.436µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 856.783µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 841.8µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:10:13Z"
    - latency: 872.428µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:09:13Z"
    - latency: 1.407669ms
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:08:13Z"
    - latency: 917.514µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:07:13Z"
    - latency: 892.875µs
      message: 'network-check-target-ip-10-0-143-0: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:06:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T18:33:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-0-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-0.ec2.internal
      uid: e70dea67-e51f-4f6c-93d8-8d9e33a7d945
    resourceVersion: "32042"
    uid: e38a1be2-74a2-41a8-9fd8-2b9c86dffb91
  spec:
    sourcePod: network-check-source-989f8b8dc-tph4x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T18:39:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 817.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 1.663612ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:15:13Z"
    - latency: 858.439µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 1.639107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:14:13Z"
    - latency: 749.211µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 1.788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:13:13Z"
    - latency: 1.165163ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 1.9501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:12:13Z"
    - latency: 1.063304ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T19:11:13Z"
    - latency: 1.779568ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T19:11:13Z"
kind: List
metadata:
  resourceVersion: ""