apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "73081"
    uid: 743bfdd0-5938-48d9-92f5-db14c3e1f0bb
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:32:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.085012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:21:43Z"
    - latency: 1.176664ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:20:43Z"
    - latency: 1.572353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 1.053678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 1.209016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 1.285917ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 1.131577ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 1.405601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:14:43Z"
    - latency: 1.507ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:13:43Z"
    - latency: 999.846µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:12:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "70929"
    uid: ad9edbe2-12d0-4c01-b9b7-bee70c505966
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:31:43Z"
      message: 'load-balancer-api-external: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.285578ms
      message: 'load-balancer-api-external: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 8.249583ms
      message: 'load-balancer-api-external: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 4.951205ms
      message: 'load-balancer-api-external: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 8.342857ms
      message: 'load-balancer-api-external: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 6.18785ms
      message: 'load-balancer-api-external: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 8.63706ms
      message: 'load-balancer-api-external: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 4.557073ms
      message: 'load-balancer-api-external: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 7.06692ms
      message: 'load-balancer-api-external: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 6.621107ms
      message: 'load-balancer-api-external: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 8.821635ms
      message: 'load-balancer-api-external: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:15:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "70928"
    uid: a3a56ad5-797a-451c-ae1e-6d6cfaf6174c
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:31:43Z"
      message: 'load-balancer-api-internal: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.296645ms
      message: 'load-balancer-api-internal: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 8.224262ms
      message: 'load-balancer-api-internal: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 4.918685ms
      message: 'load-balancer-api-internal: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 8.30103ms
      message: 'load-balancer-api-internal: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 4.591449ms
      message: 'load-balancer-api-internal: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 8.605366ms
      message: 'load-balancer-api-internal: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 6.430754ms
      message: 'load-balancer-api-internal: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 7.038489ms
      message: 'load-balancer-api-internal: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 5.713953ms
      message: 'load-balancer-api-internal: tcp connection to a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 8.770571ms
      message: 'load-balancer-api-internal: resolved host name a851cce9482224865a5b16bf79e20694-0bc652909c0582b9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:15:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-132-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "73080"
    uid: 55ff6c9d-fbfa-4c3a-8c71-afd380d2b4a2
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:32:43Z"
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.310958ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:21:43Z"
    - latency: 2.286402ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:20:43Z"
    - latency: 2.409042ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 2.272443ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 2.24999ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 2.42692ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 2.186391ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 2.422616ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:14:43Z"
    - latency: 2.271202ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:13:43Z"
    - latency: 2.437769ms
      message: 'network-check-target-ip-10-0-132-37: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:12:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-133-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "73078"
    uid: 86f036c3-feee-4cc8-9f19-e8360775983f
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:32:43Z"
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 962.678µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:21:43Z"
    - latency: 1.429163ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:20:43Z"
    - latency: 1.025854ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 836.417µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 959.654µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 976.48µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 1.132276ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 1.380711ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:14:43Z"
    - latency: 1.058407ms
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:13:43Z"
    - latency: 994.29µs
      message: 'network-check-target-ip-10-0-133-70: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:12:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-ip-10-0-134-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "73079"
    uid: 7bb87968-f4d2-4346-ba68-56e643f306be
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:32:43Z"
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.276076ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:21:43Z"
    - latency: 2.396452ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:20:43Z"
    - latency: 2.617371ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 2.155995ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 2.082706ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 2.715158ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 2.288862ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 2.459987ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:14:43Z"
    - latency: 2.357839ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:13:43Z"
    - latency: 2.468214ms
      message: 'network-check-target-ip-10-0-134-153: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:12:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-08-05T16:25:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-70.ec2.internal
      uid: 9ae2f5bb-916a-40cc-9783-9971c19dab37
    resourceVersion: "70927"
    uid: 210f058c-9445-4d6f-8e05-21bd78dd6d95
  spec:
    sourcePod: network-check-source-65bdbbff45-l6g5t
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-08-05T16:31:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 1.824853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:19:43Z"
    - latency: 1.255505ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 1.777212ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:18:43Z"
    - latency: 967.704µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 1.834289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:17:43Z"
    - latency: 1.185719ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 1.859785ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:16:43Z"
    - latency: 837.763µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-08-05T17:15:43Z"
    - latency: 2.10579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-08-05T17:15:43Z"
kind: List
metadata:
  resourceVersion: ""