apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62895"
    uid: fde0ec3d-b185-4276-8cea-ababe13636c4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:54: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.929619ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 1.415427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 980.461µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 1.229767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 1.162147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 1.141256ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:24:16Z"
    - latency: 4.577856ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:23:16Z"
    - latency: 1.144694ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:22:16Z"
    - latency: 953.39µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:21:16Z"
    - latency: 953.889µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62897"
    uid: 89047d47-0243-4049-8223-d681a9c5a298
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:53:16Z"
      message: 'load-balancer-api-external: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.772723ms
      message: 'load-balancer-api-external: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 7.730999ms
      message: 'load-balancer-api-external: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 5.415287ms
      message: 'load-balancer-api-external: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 7.989917ms
      message: 'load-balancer-api-external: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 4.110877ms
      message: 'load-balancer-api-external: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 7.269892ms
      message: 'load-balancer-api-external: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 5.257072ms
      message: 'load-balancer-api-external: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 6.70274ms
      message: 'load-balancer-api-external: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 4.697978ms
      message: 'load-balancer-api-external: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 9.579904ms
      message: 'load-balancer-api-external: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62896"
    uid: 9ec3b624-4627-462c-b60b-2f75e718c7df
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:53:16Z"
      message: 'load-balancer-api-internal: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.757843ms
      message: 'load-balancer-api-internal: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 8.042536ms
      message: 'load-balancer-api-internal: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 5.422581ms
      message: 'load-balancer-api-internal: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 7.911172ms
      message: 'load-balancer-api-internal: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 4.242901ms
      message: 'load-balancer-api-internal: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 7.17664ms
      message: 'load-balancer-api-internal: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 7.154913ms
      message: 'load-balancer-api-internal: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 6.750488ms
      message: 'load-balancer-api-internal: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 5.824756ms
      message: 'load-balancer-api-internal: tcp connection to ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 9.6423ms
      message: 'load-balancer-api-internal: resolved host name ae368d438ac564eff893aa625eeb48c1-83c6bffc42408f95.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:25:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-ip-10-0-129-212
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62892"
    uid: fbd6ec75-14e2-42a8-8f42-35bfd280f8ca
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:54:16Z"
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.52783ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 1.08407ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 1.061851ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 1.084808ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 1.676448ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 1.108018ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:24:16Z"
    - latency: 5.362477ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:23:16Z"
    - latency: 1.145648ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:22:16Z"
    - latency: 1.078283ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:21:16Z"
    - latency: 1.12827ms
      message: 'network-check-target-ip-10-0-129-212: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-ip-10-0-129-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62891"
    uid: 4e8e3340-1ae5-4181-a712-5b711654f1cf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:54:16Z"
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.96945ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 2.61521ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 2.329767ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 2.433261ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 2.423661ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 2.257432ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:24:16Z"
    - latency: 5.076203ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:23:16Z"
    - latency: 2.524827ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:22:16Z"
    - latency: 2.030913ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:21:16Z"
    - latency: 2.563451ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-ip-10-0-132-245
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62894"
    uid: fe11bfd2-c816-4958-9c6a-4bf393ffce67
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:54:16Z"
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.974338ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 2.493934ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 2.438009ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 2.015341ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 2.292355ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 2.341472ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:24:16Z"
    - latency: 5.484552ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:23:16Z"
    - latency: 2.89891ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:22:16Z"
    - latency: 2.19662ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:21:16Z"
    - latency: 2.143877ms
      message: 'network-check-target-ip-10-0-132-245: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:20:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T13:47:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-212-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-212.ec2.internal
      uid: 6a801e72-621a-4ad1-bacc-0375d0200598
    resourceVersion: "62893"
    uid: 5d823611-b418-407c-85b3-6ba3242a6d1e
  spec:
    sourcePod: network-check-source-7bc5b6bf85-glfqj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T13:53:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.04633ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 2.006704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:29:16Z"
    - latency: 1.383303ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 2.015036ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:28:16Z"
    - latency: 930.01µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 1.899205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:27:16Z"
    - latency: 1.134212ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 2.047877ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:26:16Z"
    - latency: 1.034367ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T14:25:16Z"
    - latency: 1.852987ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T14:25:16Z"
kind: List
metadata:
  resourceVersion: ""