apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "53930"
    uid: f006491d-e93d-4d7e-a766-a027ed097849
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:16:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.249396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 1.120516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 888.167µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 1.418661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:34:54Z"
    - latency: 949.083µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:33:54Z"
    - latency: 1.105408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:32:54Z"
    - latency: 1.15267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:31:54Z"
    - latency: 1.018296ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:30:54Z"
    - latency: 1.000698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:29:54Z"
    - latency: 754.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:28:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "55646"
    uid: c14aec96-404a-4298-af0d-1774b54176b7
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:15:54Z"
      message: 'load-balancer-api-external: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.021212ms
      message: 'load-balancer-api-external: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:39:54Z"
    - latency: 11.96273ms
      message: 'load-balancer-api-external: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:39:54Z"
    - latency: 6.028697ms
      message: 'load-balancer-api-external: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:38:54Z"
    - latency: 7.011421ms
      message: 'load-balancer-api-external: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:38:54Z"
    - latency: 3.279377ms
      message: 'load-balancer-api-external: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 8.844144ms
      message: 'load-balancer-api-external: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 3.291817ms
      message: 'load-balancer-api-external: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 8.605846ms
      message: 'load-balancer-api-external: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 5.952684ms
      message: 'load-balancer-api-external: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 8.272854ms
      message: 'load-balancer-api-external: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:35:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "55647"
    uid: 55acaf60-3b9b-49e8-853d-5bd1923c12cf
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:15:54Z"
      message: 'load-balancer-api-internal: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.676262ms
      message: 'load-balancer-api-internal: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:39:54Z"
    - latency: 11.904065ms
      message: 'load-balancer-api-internal: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:39:54Z"
    - latency: 5.98631ms
      message: 'load-balancer-api-internal: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:38:54Z"
    - latency: 7.139434ms
      message: 'load-balancer-api-internal: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:38:54Z"
    - latency: 3.321212ms
      message: 'load-balancer-api-internal: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 8.812681ms
      message: 'load-balancer-api-internal: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 3.16763ms
      message: 'load-balancer-api-internal: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 8.659688ms
      message: 'load-balancer-api-internal: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 5.969261ms
      message: 'load-balancer-api-internal: tcp connection to a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 8.328395ms
      message: 'load-balancer-api-internal: resolved host name a3dd30a3f9af644a4b8ec980cbb68dbf-86cfafec7b1feeb7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:35:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-network-check-target-ip-10-0-132-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "53927"
    uid: e45407ea-f39b-4ad7-bc01-a5d2ee0c99a4
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:16:54Z"
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.179743ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 2.049899ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 2.070841ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 1.992175ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:34:54Z"
    - latency: 1.835284ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:33:54Z"
    - latency: 1.720505ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:32:54Z"
    - latency: 2.157265ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:31:54Z"
    - latency: 2.295257ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:30:54Z"
    - latency: 2.028019ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:29:54Z"
    - latency: 1.642938ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:28:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-network-check-target-ip-10-0-137-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "53929"
    uid: 8bdc694e-19e1-4573-a82b-bfcfea5f0e1f
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:16:54Z"
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.369289ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 2.4618ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 2.301043ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 2.477097ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:34:54Z"
    - latency: 2.235971ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:33:54Z"
    - latency: 2.036926ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:32:54Z"
    - latency: 2.579488ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:31:54Z"
    - latency: 2.608374ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:30:54Z"
    - latency: 2.494321ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:29:54Z"
    - latency: 1.98785ms
      message: 'network-check-target-ip-10-0-137-172: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:28:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-network-check-target-ip-10-0-143-169
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "53928"
    uid: f0cc424d-c518-4ec9-a987-f141ef2f5627
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:16:54Z"
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.250379ms
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 1.055626ms
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 894.089µs
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 833.274µs
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:34:54Z"
    - latency: 1.30144ms
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:33:54Z"
    - latency: 728.796µs
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:32:54Z"
    - latency: 1.294186ms
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:31:54Z"
    - latency: 721.493µs
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:30:54Z"
    - latency: 959.085µs
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:29:54Z"
    - latency: 831.837µs
      message: 'network-check-target-ip-10-0-143-169: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:28:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T16:09:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-169-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-169.ec2.internal
      uid: 0ccc8114-d356-4056-bb2c-8a921206bc66
    resourceVersion: "55645"
    uid: baa4b22d-2262-4f4c-8611-2c560a1cb0e1
  spec:
    sourcePod: network-check-source-685456655f-wc5hh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T16:15:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.384µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:39:54Z"
    - latency: 1.828532ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:39:54Z"
    - latency: 967.395µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:38:54Z"
    - latency: 1.821384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:38:54Z"
    - latency: 1.05051ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 2.215768ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:37:54Z"
    - latency: 976.765µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 1.879026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:36:54Z"
    - latency: 757.861µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T16:35:54Z"
    - latency: 1.61415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T16:35:54Z"
kind: List
metadata:
  resourceVersion: ""