apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "19488"
    uid: a08a6e4f-e06d-4002-ab6b-159c1f0d9e9b
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:25:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.057392ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 873.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 965.117µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:37:24Z"
    - latency: 1.061948ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:36:24Z"
    - latency: 1.391206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:35:24Z"
    - latency: 877.842µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:34:24Z"
    - latency: 928.725µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:33:24Z"
    - latency: 826.189µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:32:24Z"
    - latency: 1.596297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:31:24Z"
    - latency: 945.959µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:30:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "20834"
    uid: debee080-d38c-4146-a5bf-23d23301b7a4
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:24:24Z"
      message: 'load-balancer-api-external: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.143966ms
      message: 'load-balancer-api-external: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:42:24Z"
    - latency: 6.504809ms
      message: 'load-balancer-api-external: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:42:24Z"
    - latency: 3.334344ms
      message: 'load-balancer-api-external: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:41:24Z"
    - latency: 8.250647ms
      message: 'load-balancer-api-external: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:41:24Z"
    - latency: 4.504974ms
      message: 'load-balancer-api-external: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:40:24Z"
    - latency: 7.60978ms
      message: 'load-balancer-api-external: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:40:24Z"
    - latency: 5.62067ms
      message: 'load-balancer-api-external: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 6.465521ms
      message: 'load-balancer-api-external: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 5.247414ms
      message: 'load-balancer-api-external: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 7.562305ms
      message: 'load-balancer-api-external: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:38:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "20833"
    uid: c713479f-5bd7-4dc1-8c08-3ac5347cc06e
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:24:24Z"
      message: 'load-balancer-api-internal: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.056487ms
      message: 'load-balancer-api-internal: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:42:24Z"
    - latency: 6.565411ms
      message: 'load-balancer-api-internal: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:42:24Z"
    - latency: 3.348412ms
      message: 'load-balancer-api-internal: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:41:24Z"
    - latency: 8.29182ms
      message: 'load-balancer-api-internal: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:41:24Z"
    - latency: 4.71214ms
      message: 'load-balancer-api-internal: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:40:24Z"
    - latency: 7.665174ms
      message: 'load-balancer-api-internal: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:40:24Z"
    - latency: 5.635134ms
      message: 'load-balancer-api-internal: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 6.513185ms
      message: 'load-balancer-api-internal: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 4.534728ms
      message: 'load-balancer-api-internal: tcp connection to ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 7.589535ms
      message: 'load-balancer-api-internal: resolved host name ada602bc46aa948088aaf9f6142f2a94-ca9ab764d38e09b2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:38:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-network-check-target-ip-10-0-138-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "19487"
    uid: 02e764f1-2eb5-40f7-8b88-30c4a5cb0a60
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:25:24Z"
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.040294ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 2.122874ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 1.825084ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:37:24Z"
    - latency: 1.899375ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:36:24Z"
    - latency: 1.633665ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:35:24Z"
    - latency: 1.855107ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:34:24Z"
    - latency: 1.844979ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:33:24Z"
    - latency: 1.960788ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:32:24Z"
    - latency: 2.050869ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:31:24Z"
    - latency: 1.972043ms
      message: 'network-check-target-ip-10-0-138-188: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:30:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-network-check-target-ip-10-0-139-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "19486"
    uid: e0c2090c-9c76-4cf1-8df0-b7e25621a126
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:25:24Z"
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.029289ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 2.294073ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 2.091275ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:37:24Z"
    - latency: 1.967726ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:36:24Z"
    - latency: 2.255054ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:35:24Z"
    - latency: 2.140627ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:34:24Z"
    - latency: 1.993947ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:33:24Z"
    - latency: 2.005299ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:32:24Z"
    - latency: 2.231323ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:31:24Z"
    - latency: 2.082384ms
      message: 'network-check-target-ip-10-0-139-170: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:30:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-network-check-target-ip-10-0-140-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "19485"
    uid: fea4dd6e-b1d6-457e-be53-be57cafb22e3
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:25:24Z"
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 919.17µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 1.374883ms
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 953.287µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:37:24Z"
    - latency: 1.105145ms
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:36:24Z"
    - latency: 787.582µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:35:24Z"
    - latency: 720.361µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:34:24Z"
    - latency: 886.579µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:33:24Z"
    - latency: 876.074µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:32:24Z"
    - latency: 946.358µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:31:24Z"
    - latency: 978.736µs
      message: 'network-check-target-ip-10-0-140-80: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:30:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T09:18:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-80-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-80.ec2.internal
      uid: cb646a7b-6192-4850-9c17-79aa9e7dc75c
    resourceVersion: "20831"
    uid: e8cde892-a9f0-4ea6-9c36-0434e89ce664
  spec:
    sourcePod: network-check-source-685456655f-nlpz7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T09:24:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 738.122µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:42:24Z"
    - latency: 1.641177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:42:24Z"
    - latency: 881.088µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:41:24Z"
    - latency: 1.739141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:41:24Z"
    - latency: 868.518µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:40:24Z"
    - latency: 1.802545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:40:24Z"
    - latency: 841.759µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 1.740552ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:39:24Z"
    - latency: 797.554µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T09:38:24Z"
    - latency: 2.152679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T09:38:24Z"
kind: List
metadata:
  resourceVersion: ""