apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32726"
    uid: 6b8e6ee9-6b57-46b6-ae83-2860924b04d4
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 842.928µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 1.252445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 1.065427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 1.052463ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 1.443175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:02:03Z"
    - latency: 1.125205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:01:03Z"
    - latency: 1.242444ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:00:03Z"
    - latency: 1.224137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:59:03Z"
    - latency: 886.6µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32727"
    uid: 18c42714-b149-4d74-bd2f-399cbd03f85a
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:31:03Z"
      message: 'load-balancer-api-external: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.022173ms
      message: 'load-balancer-api-external: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 8.758088ms
      message: 'load-balancer-api-external: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 5.118242ms
      message: 'load-balancer-api-external: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 8.697429ms
      message: 'load-balancer-api-external: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 5.735769ms
      message: 'load-balancer-api-external: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 8.452841ms
      message: 'load-balancer-api-external: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 5.144803ms
      message: 'load-balancer-api-external: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 8.73856ms
      message: 'load-balancer-api-external: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 6.463303ms
      message: 'load-balancer-api-external: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 10.541359ms
      message: 'load-balancer-api-external: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:03:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32728"
    uid: d68d13ba-bf5b-45c4-98ea-e3120204c455
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:31:03Z"
      message: 'load-balancer-api-internal: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.427239ms
      message: 'load-balancer-api-internal: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 8.954407ms
      message: 'load-balancer-api-internal: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 4.523477ms
      message: 'load-balancer-api-internal: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 8.662275ms
      message: 'load-balancer-api-internal: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 4.246332ms
      message: 'load-balancer-api-internal: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 8.484936ms
      message: 'load-balancer-api-internal: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 5.130808ms
      message: 'load-balancer-api-internal: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 8.824185ms
      message: 'load-balancer-api-internal: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 6.247813ms
      message: 'load-balancer-api-internal: tcp connection to aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 10.474698ms
      message: 'load-balancer-api-internal: resolved host name aba220cb1f2254be5bd39b197c7e0f94-4af5314cdb6f6b6d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:03:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-network-check-target-ip-10-0-139-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32724"
    uid: e1a34fb3-4dff-421d-8224-d29556db635a
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:03Z"
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.197458ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 2.31211ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 2.301804ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 2.196883ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 2.326595ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 2.804382ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:02:03Z"
    - latency: 2.116247ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:01:03Z"
    - latency: 2.505306ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:00:03Z"
    - latency: 2.399337ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:59:03Z"
    - latency: 2.433335ms
      message: 'network-check-target-ip-10-0-139-127: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-network-check-target-ip-10-0-139-157
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32722"
    uid: 9f97777c-3b00-464d-a3d7-652b665b04fa
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:03Z"
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.53µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 835.972µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 945.301µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 1.002869ms
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 946.682µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 759.154µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:02:03Z"
    - latency: 795.35µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:01:03Z"
    - latency: 967.539µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:00:03Z"
    - latency: 1.000803ms
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:59:03Z"
    - latency: 940.724µs
      message: 'network-check-target-ip-10-0-139-157: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-network-check-target-ip-10-0-143-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32725"
    uid: 95f447d3-0e8c-476e-930f-f38b279cfb18
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:32:03Z"
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.129896ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 2.239064ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 2.537575ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 2.310127ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 1.97633ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 2.123135ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:02:03Z"
    - latency: 2.260292ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:01:03Z"
    - latency: 2.078214ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:00:03Z"
    - latency: 2.471892ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:59:03Z"
    - latency: 2.199092ms
      message: 'network-check-target-ip-10-0-143-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T08:58:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:25:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-157-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-157.ec2.internal
      uid: c7aa74fe-70f5-403e-9d52-e0f1dfb81d8a
    resourceVersion: "32723"
    uid: 885cc206-23bf-43b6-8e43-7dcd68db69d5
  spec:
    sourcePod: network-check-source-7cbc45fddc-2bdxn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:31:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 850.36µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 1.780781ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:07:03Z"
    - latency: 995.322µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 1.796095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:06:03Z"
    - latency: 1.400116ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 2.024293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:05:03Z"
    - latency: 935.835µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 1.846193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:04:03Z"
    - latency: 860.852µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:03:03Z"
    - latency: 1.758701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:03:03Z"
kind: List
metadata:
  resourceVersion: ""