apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65148"
    uid: a32b2438-686d-40f6-b585-fac8804eb9eb
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:40:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 984.961µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 765.793µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 1.035841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 995.626µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 924.891µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 985.52µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:10:24Z"
    - latency: 1.273691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:09:24Z"
    - latency: 952.254µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:08:24Z"
    - latency: 1.134594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:07:24Z"
    - latency: 1.068494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:06:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65150"
    uid: 7dffd7e3-c356-4c70-a4fb-3a5918527956
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:39:24Z"
      message: 'load-balancer-api-external: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.234451ms
      message: 'load-balancer-api-external: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 6.668345ms
      message: 'load-balancer-api-external: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 6.385493ms
      message: 'load-balancer-api-external: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 7.21819ms
      message: 'load-balancer-api-external: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 3.977069ms
      message: 'load-balancer-api-external: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 6.997086ms
      message: 'load-balancer-api-external: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 4.732904ms
      message: 'load-balancer-api-external: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 7.925181ms
      message: 'load-balancer-api-external: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 3.895313ms
      message: 'load-balancer-api-external: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 5.735817ms
      message: 'load-balancer-api-external: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:11:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65149"
    uid: 285c875b-4efe-4ec1-8064-b2ed792dfc12
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:39:24Z"
      message: 'load-balancer-api-internal: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.197713ms
      message: 'load-balancer-api-internal: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 6.766265ms
      message: 'load-balancer-api-internal: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 6.371921ms
      message: 'load-balancer-api-internal: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 7.152152ms
      message: 'load-balancer-api-internal: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 4.915341ms
      message: 'load-balancer-api-internal: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 6.96514ms
      message: 'load-balancer-api-internal: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 4.714042ms
      message: 'load-balancer-api-internal: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 7.89476ms
      message: 'load-balancer-api-internal: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 3.908366ms
      message: 'load-balancer-api-internal: tcp connection to a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 5.882842ms
      message: 'load-balancer-api-internal: resolved host name a15e764378c3543c4ab1b3813de7f278-03150edd2825ceab.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:11:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-network-check-target-ip-10-0-130-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65146"
    uid: 29fb8b3f-cf0e-417b-a2e6-e87e42aae919
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:40:24Z"
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.190578ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 1.855594ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 2.246837ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 2.260581ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 2.311509ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 2.27705ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:10:24Z"
    - latency: 2.517788ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:09:24Z"
    - latency: 2.340815ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:08:24Z"
    - latency: 2.241019ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:07:24Z"
    - latency: 2.26594ms
      message: 'network-check-target-ip-10-0-130-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:06:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-network-check-target-ip-10-0-139-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65145"
    uid: 6c4dfb6e-cfe0-4767-b127-7a4f97436867
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:40:24Z"
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.857731ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 1.502959ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 1.971442ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 2.002815ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 2.06318ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 1.964588ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:10:24Z"
    - latency: 1.838165ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:09:24Z"
    - latency: 2.029618ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:08:24Z"
    - latency: 1.959656ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:07:24Z"
    - latency: 1.879779ms
      message: 'network-check-target-ip-10-0-139-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:06:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-network-check-target-ip-10-0-142-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65144"
    uid: 9976e691-081d-4414-80c6-e32841cb636b
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:40:24Z"
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 725.085µs
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 863.871µs
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 1.662051ms
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 1.32054ms
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 892.107µs
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 958.423µs
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:10:24Z"
    - latency: 944.14µs
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:09:24Z"
    - latency: 1.101139ms
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:08:24Z"
    - latency: 1.020091ms
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:07:24Z"
    - latency: 906.389µs
      message: 'network-check-target-ip-10-0-142-40: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:06:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T19:33:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-40-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-40.ec2.internal
      uid: 8f289e1c-c1e3-4b8b-bc7e-ab9373f26e0c
    resourceVersion: "65147"
    uid: 965be3ff-0e6b-4503-a8ef-0545e3a7342e
  spec:
    sourcePod: network-check-source-869dcfcdcd-r2cdl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T19:39:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.678µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 1.827955ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:15:24Z"
    - latency: 761.598µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 2.032485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:14:24Z"
    - latency: 817.337µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 1.941807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:13:24Z"
    - latency: 950.26µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 1.881793ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:12:24Z"
    - latency: 929.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T20:11:24Z"
    - latency: 1.723517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T20:11:24Z"
kind: List
metadata:
  resourceVersion: ""