apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64839"
    uid: 427551d7-6e04-4821-bfa8-0ad255e0efa9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:51:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.015255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 937.91µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 1.258215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 1.255519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 872.81µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 877.975µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:21:16Z"
    - latency: 1.258724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:20:16Z"
    - latency: 821.237µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:19:16Z"
    - latency: 3.005606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:18:16Z"
    - latency: 1.073265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:17:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64840"
    uid: b4103d9d-3362-4a9e-8398-db473d68c211
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:50:16Z"
      message: 'load-balancer-api-external: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.372574ms
      message: 'load-balancer-api-external: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 7.502936ms
      message: 'load-balancer-api-external: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 4.800865ms
      message: 'load-balancer-api-external: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 9.692489ms
      message: 'load-balancer-api-external: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 3.847018ms
      message: 'load-balancer-api-external: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 7.071778ms
      message: 'load-balancer-api-external: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 4.549843ms
      message: 'load-balancer-api-external: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 7.483748ms
      message: 'load-balancer-api-external: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 4.23298ms
      message: 'load-balancer-api-external: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 6.487683ms
      message: 'load-balancer-api-external: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:22:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64841"
    uid: a508171b-646e-41dd-ad1d-fd2f77f701e9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:50:16Z"
      message: 'load-balancer-api-internal: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.429087ms
      message: 'load-balancer-api-internal: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 7.524538ms
      message: 'load-balancer-api-internal: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 5.222844ms
      message: 'load-balancer-api-internal: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 9.781412ms
      message: 'load-balancer-api-internal: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 3.812125ms
      message: 'load-balancer-api-internal: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 7.143321ms
      message: 'load-balancer-api-internal: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 4.463213ms
      message: 'load-balancer-api-internal: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 7.530945ms
      message: 'load-balancer-api-internal: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 4.359753ms
      message: 'load-balancer-api-internal: tcp connection to a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 6.554809ms
      message: 'load-balancer-api-internal: resolved host name a473e2cae20c9401488c4bf325d67422-d083a5f49666b011.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:22:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-network-check-target-ip-10-0-136-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64837"
    uid: df738e20-54fc-4350-8875-41aed1b625cc
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:51:16Z"
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.351157ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 2.481722ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 2.20351ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 2.306225ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 2.370292ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 2.282271ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:21:16Z"
    - latency: 2.070217ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:20:16Z"
    - latency: 2.205781ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:19:16Z"
    - latency: 3.6702ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:18:16Z"
    - latency: 2.330812ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:17:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-network-check-target-ip-10-0-139-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64836"
    uid: a1c8b582-86a5-4d00-8a42-0cf4d87fe634
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:51:16Z"
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.273582ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 2.476964ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 2.537144ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 2.327274ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 2.356028ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 2.343264ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:21:16Z"
    - latency: 2.2761ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:20:16Z"
    - latency: 2.324211ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:19:16Z"
    - latency: 2.58025ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:18:16Z"
    - latency: 2.135176ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:17:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-network-check-target-ip-10-0-142-77
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64835"
    uid: f83411e9-21f3-447b-99dd-7bd0c6c29342
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:51:16Z"
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 916.12µs
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 918.083µs
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 925.16µs
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 1.044016ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 1.369338ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 1.137365ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:21:16Z"
    - latency: 1.429632ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:20:16Z"
    - latency: 994.968µs
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:19:16Z"
    - latency: 1.181725ms
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:18:16Z"
    - latency: 959.823µs
      message: 'network-check-target-ip-10-0-142-77: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:17:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-18T16:44:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-77-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-77.ec2.internal
      uid: 61f1b553-ab80-4e41-baff-0d5eaa9c99f9
    resourceVersion: "64838"
    uid: d841a254-998c-4bac-9918-bdbf36db0d0a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-bq5fh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-18T16:50:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.513203ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 1.856488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:26:16Z"
    - latency: 731.584µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 1.777499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:25:16Z"
    - latency: 877.777µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 1.717423ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:24:16Z"
    - latency: 792.626µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 1.689359ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:23:16Z"
    - latency: 911.197µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-18T17:22:16Z"
    - latency: 1.592587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-18T17:22:16Z"
kind: List
metadata:
  resourceVersion: ""