apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "103033"
    uid: 9dcd6a3d-ca96-4ec4-8a93-0d40052acad0
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:25:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.074462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 1.421239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 1.108469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 6.604695ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:04Z"
    - latency: 1.915815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:24:04Z"
    - latency: 1.360098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:23:04Z"
    - latency: 1.121996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:22:04Z"
    - latency: 1.803344ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:21:04Z"
    - latency: 1.213443ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:20:04Z"
    - latency: 1.174633ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "104025"
    uid: 099ad9dc-7bdb-4dfc-a942-b4731cda9dbd
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:04Z"
      message: 'load-balancer-api-external: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.473831ms
      message: 'load-balancer-api-external: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:04Z"
    - latency: 6.43393ms
      message: 'load-balancer-api-external: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:30:04Z"
    - latency: 54.329876ms
      message: 'load-balancer-api-external: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:04Z"
    - latency: 6.95637ms
      message: 'load-balancer-api-external: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:29:04Z"
    - latency: 54.695406ms
      message: 'load-balancer-api-external: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 6.667663ms
      message: 'load-balancer-api-external: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 54.697237ms
      message: 'load-balancer-api-external: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 7.184953ms
      message: 'load-balancer-api-external: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 54.710307ms
      message: 'load-balancer-api-external: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 6.442218ms
      message: 'load-balancer-api-external: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:26:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "104026"
    uid: ec51b266-ef92-4a31-a6a2-2d408baacba0
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:04Z"
      message: 'load-balancer-api-internal: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.550949ms
      message: 'load-balancer-api-internal: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:04Z"
    - latency: 6.397633ms
      message: 'load-balancer-api-internal: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:30:04Z"
    - latency: 55.248375ms
      message: 'load-balancer-api-internal: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:04Z"
    - latency: 7.004248ms
      message: 'load-balancer-api-internal: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:29:04Z"
    - latency: 54.61877ms
      message: 'load-balancer-api-internal: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 6.622561ms
      message: 'load-balancer-api-internal: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 54.210797ms
      message: 'load-balancer-api-internal: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 7.222054ms
      message: 'load-balancer-api-internal: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 3.385936713s
      message: 'load-balancer-api-internal: tcp connection to a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 6.542875ms
      message: 'load-balancer-api-internal: resolved host name a99e23be2ae284760adacf985437c851-69fa068035f08793.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:26:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-network-check-target-ip-10-0-132-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "102937"
    uid: 887c1958-c4b8-4ea2-9b62-5d3650a1cf3d
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:25:04Z"
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127188ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 1.146747ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 1.390033ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 5.846031ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:04Z"
    - latency: 2.049569ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:24:04Z"
    - latency: 1.054499ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:23:04Z"
    - latency: 1.277907ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:22:04Z"
    - latency: 1.02231ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:21:04Z"
    - latency: 1.46919ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:20:04Z"
    - latency: 1.505198ms
      message: 'network-check-target-ip-10-0-132-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-network-check-target-ip-10-0-133-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "102938"
    uid: 0296a86d-7b56-406a-854e-0ee68cb2356a
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:25:04Z"
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052565ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 1.450697ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 1.330864ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 4.154249ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:04Z"
    - latency: 2.632355ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:24:04Z"
    - latency: 1.507795ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:23:04Z"
    - latency: 1.726967ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:22:04Z"
    - latency: 1.639267ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:21:04Z"
    - latency: 1.471715ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:20:04Z"
    - latency: 1.142287ms
      message: 'network-check-target-ip-10-0-133-7: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-network-check-target-ip-10-0-141-5
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "102939"
    uid: 4fc16d38-04bc-4c7e-8a76-175840135fa7
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:25:04Z"
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.864278ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 1.330238ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 1.621516ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 4.678268ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:25:04Z"
    - latency: 3.417844ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:24:04Z"
    - latency: 2.321062ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:23:04Z"
    - latency: 1.309016ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:22:04Z"
    - latency: 1.987706ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:21:04Z"
    - latency: 2.097634ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:20:04Z"
    - latency: 1.819764ms
      message: 'network-check-target-ip-10-0-141-5: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:19:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T19:18:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-82.us-west-1.compute.internal
      uid: e92c42ab-910c-411f-b86d-47ca0a8df3e6
    resourceVersion: "104021"
    uid: 00872023-ee78-4787-9b49-c73f199315de
  spec:
    sourcePod: network-check-source-6f78d59f99-2trjq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T19:24:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:30:04Z"
    - latency: 1.875218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:30:04Z"
    - latency: 912.423µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:29:04Z"
    - latency: 1.937448ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:29:04Z"
    - latency: 1.66927ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 1.997803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:28:04Z"
    - latency: 1.974447ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 1.746096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:27:04Z"
    - latency: 1.916428ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T20:26:04Z"
    - latency: 1.862395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T20:26:04Z"
kind: List
metadata:
  resourceVersion: ""