apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32177"
    uid: 82c8c509-5e11-4b1e-bdd7-ca34a791ef4d
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 938.278µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 1.156002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 1.079172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 1.406567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 1.329986ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:25Z"
    - latency: 929.837µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:25Z"
    - latency: 970.183µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:25Z"
    - latency: 1.011316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:25Z"
    - latency: 905.873µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:49:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32178"
    uid: 4006d2a8-4205-43b9-9ca0-e99fa1bdaf6c
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:22:25Z"
      message: 'load-balancer-api-external: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.218625ms
      message: 'load-balancer-api-external: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 9.407934ms
      message: 'load-balancer-api-external: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 4.57326ms
      message: 'load-balancer-api-external: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 9.311527ms
      message: 'load-balancer-api-external: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 4.454086ms
      message: 'load-balancer-api-external: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 8.678113ms
      message: 'load-balancer-api-external: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 5.607036ms
      message: 'load-balancer-api-external: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 8.175392ms
      message: 'load-balancer-api-external: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 4.66804ms
      message: 'load-balancer-api-external: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 8.177071ms
      message: 'load-balancer-api-external: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:54:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32179"
    uid: cce1ae40-5743-49ec-b80b-91c8297181c4
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:22:25Z"
      message: 'load-balancer-api-internal: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.136556ms
      message: 'load-balancer-api-internal: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 9.502481ms
      message: 'load-balancer-api-internal: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 4.587161ms
      message: 'load-balancer-api-internal: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 9.241557ms
      message: 'load-balancer-api-internal: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 4.148227ms
      message: 'load-balancer-api-internal: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 8.574767ms
      message: 'load-balancer-api-internal: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 5.627616ms
      message: 'load-balancer-api-internal: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 8.141462ms
      message: 'load-balancer-api-internal: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 4.793718ms
      message: 'load-balancer-api-internal: tcp connection to a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 8.136629ms
      message: 'load-balancer-api-internal: resolved host name a5d277813ec9c4f77a369a0c79fd5058-d34fbd019d307da2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:54:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-ip-10-0-136-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32175"
    uid: 9d71e5a4-5402-41f6-bef1-2a7db0fa654d
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:25Z"
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.233463ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 2.304079ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 2.184561ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 2.159768ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 2.064234ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 2.513613ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:25Z"
    - latency: 2.016682ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:25Z"
    - latency: 2.288171ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:25Z"
    - latency: 1.86465ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:25Z"
    - latency: 2.338695ms
      message: 'network-check-target-ip-10-0-136-12: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:49:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-ip-10-0-140-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32173"
    uid: 5c998928-e2cd-4d97-8f2d-32c398946d76
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:25Z"
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.614331ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 696.64µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 1.235018ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 1.363011ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 895.385µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 1.527697ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:25Z"
    - latency: 871.052µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:25Z"
    - latency: 1.368869ms
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:25Z"
    - latency: 938.385µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:25Z"
    - latency: 982.666µs
      message: 'network-check-target-ip-10-0-140-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:49:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-ip-10-0-142-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32174"
    uid: a4db900a-f016-4359-9622-9478d34f88ad
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:23:25Z"
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.765326ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 2.028347ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 1.875528ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 1.696332ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 1.816152ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 2.089098ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:53:25Z"
    - latency: 1.504777ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:52:25Z"
    - latency: 1.989687ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:51:25Z"
    - latency: 2.124098ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:50:25Z"
    - latency: 1.837574ms
      message: 'network-check-target-ip-10-0-142-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:49:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T21:16:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-54.ec2.internal
      uid: 74fee3b5-b066-4952-8566-c3f2fb754dd6
    resourceVersion: "32176"
    uid: c2fe3f1e-d92b-4d57-a5fd-d4079cd750c5
  spec:
    sourcePod: network-check-source-989f8b8dc-2m2h6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T21:22:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 973.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 2.301981ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:58:25Z"
    - latency: 839.404µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 2.095849ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:57:25Z"
    - latency: 988.468µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 1.943482ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:56:25Z"
    - latency: 872.948µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 1.699786ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:55:25Z"
    - latency: 756.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:54:25Z"
    - latency: 1.516751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T21:54:25Z"
kind: List
metadata:
  resourceVersion: ""