apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "28722"
    uid: 208c83b9-c8ab-4fd6-92fe-b81e7cc8c455
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:40Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.227644ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:25:40Z"
    - latency: 1.151501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:24:40Z"
    - latency: 1.020707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:23:40Z"
    - latency: 1.196522ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:22:40Z"
    - latency: 1.275911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:40Z"
    - latency: 981.03µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:40Z"
    - latency: 1.103301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:40Z"
    - latency: 1.179799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:40Z"
    - latency: 1.094409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:40Z"
    - latency: 977.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "30355"
    uid: 1dff07e6-e566-42d8-b8f2-78a246c3e778
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:40Z"
      message: 'load-balancer-api-external: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.290538ms
      message: 'load-balancer-api-external: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:40Z"
    - latency: 9.309755ms
      message: 'load-balancer-api-external: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:31:40Z"
    - latency: 4.85298ms
      message: 'load-balancer-api-external: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:40Z"
    - latency: 8.876707ms
      message: 'load-balancer-api-external: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:30:40Z"
    - latency: 6.284465ms
      message: 'load-balancer-api-external: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:40Z"
    - latency: 13.528662ms
      message: 'load-balancer-api-external: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:29:40Z"
    - latency: 4.821286ms
      message: 'load-balancer-api-external: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:40Z"
    - latency: 8.131898ms
      message: 'load-balancer-api-external: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:28:40Z"
    - latency: 6.791947ms
      message: 'load-balancer-api-external: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:40Z"
    - latency: 10.539966ms
      message: 'load-balancer-api-external: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "30354"
    uid: 5ab7bc37-b8f2-41b0-9adb-669fc24d747a
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:40Z"
      message: 'load-balancer-api-internal: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.495783ms
      message: 'load-balancer-api-internal: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:40Z"
    - latency: 9.237366ms
      message: 'load-balancer-api-internal: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:31:40Z"
    - latency: 4.861016ms
      message: 'load-balancer-api-internal: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:40Z"
    - latency: 8.800418ms
      message: 'load-balancer-api-internal: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:30:40Z"
    - latency: 6.171668ms
      message: 'load-balancer-api-internal: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:40Z"
    - latency: 13.610674ms
      message: 'load-balancer-api-internal: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:29:40Z"
    - latency: 6.725562ms
      message: 'load-balancer-api-internal: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:40Z"
    - latency: 8.08056ms
      message: 'load-balancer-api-internal: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:28:40Z"
    - latency: 7.171844ms
      message: 'load-balancer-api-internal: tcp connection to a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:40Z"
    - latency: 10.584913ms
      message: 'load-balancer-api-internal: resolved host name a5a035b3ce8f740b49a08d3c03ecad15-9f51263538568f3b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:27:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-135-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "28720"
    uid: 1bf3f729-cb74-49ff-bf4d-d3c0b2a2d42b
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:40Z"
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.848852ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:25:40Z"
    - latency: 2.347142ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:24:40Z"
    - latency: 2.778854ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:23:40Z"
    - latency: 2.464177ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:22:40Z"
    - latency: 2.645493ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:40Z"
    - latency: 2.394356ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:40Z"
    - latency: 2.471435ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:40Z"
    - latency: 2.30265ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:40Z"
    - latency: 2.334076ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:40Z"
    - latency: 2.741646ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-136-140
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "28718"
    uid: 7f93ba36-4645-414d-8b7c-40c954e6d860
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:40Z"
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.555393ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:25:40Z"
    - latency: 2.417246ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:24:40Z"
    - latency: 2.466792ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:23:40Z"
    - latency: 2.352563ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:22:40Z"
    - latency: 2.32668ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:40Z"
    - latency: 2.215522ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:40Z"
    - latency: 2.261619ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:40Z"
    - latency: 2.385355ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:40Z"
    - latency: 2.31491ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:40Z"
    - latency: 2.057022ms
      message: 'network-check-target-ip-10-0-136-140: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-ip-10-0-139-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "28719"
    uid: af0770c7-705b-4263-bad4-e1edba096f47
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:50:40Z"
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.692808ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:25:40Z"
    - latency: 928.371µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:24:40Z"
    - latency: 1.360157ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:23:40Z"
    - latency: 935.361µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:22:40Z"
    - latency: 1.363184ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:40Z"
    - latency: 984.198µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:40Z"
    - latency: 945.101µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:40Z"
    - latency: 961.548µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:40Z"
    - latency: 1.552848ms
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:40Z"
    - latency: 881.258µs
      message: 'network-check-target-ip-10-0-139-5: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:40Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:43:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-5-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-5.ec2.internal
      uid: 3611c4ad-6684-4681-a1af-a82a2ae7535f
    resourceVersion: "30353"
    uid: d10044e9-bd1d-4d7c-9ec4-d0346ac9ba26
  spec:
    sourcePod: network-check-source-7cbc45fddc-m7l6f
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:49:40Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.38µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:40Z"
    - latency: 1.64332ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:31:40Z"
    - latency: 736.46µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:40Z"
    - latency: 1.722788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:30:40Z"
    - latency: 1.241801ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:40Z"
    - latency: 1.874085ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:29:40Z"
    - latency: 1.155999ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:40Z"
    - latency: 1.716744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:28:40Z"
    - latency: 949.136µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:40Z"
    - latency: 2.955022ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:27:40Z"
kind: List
metadata:
  resourceVersion: ""