apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "106996"
    uid: cafc4360-e06a-401a-a527-26cb80718c4d
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:09:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.847176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 1.010445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 1.188526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:03:30Z"
    - latency: 1.472486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:02:30Z"
    - latency: 1.310969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:01:30Z"
    - latency: 991.164µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:00:30Z"
    - latency: 963.759µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:59:30Z"
    - latency: 1.273654ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:58:30Z"
    - latency: 985.66µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:57:30Z"
    - latency: 1.276025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "110015"
    uid: d1b116ad-c92a-4887-a295-79211dbc6310
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:08:30Z"
      message: 'load-balancer-api-external: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 52.498037ms
      message: 'load-balancer-api-external: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:30Z"
    - latency: 7.305441ms
      message: 'load-balancer-api-external: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:08:30Z"
    - latency: 53.193009ms
      message: 'load-balancer-api-external: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:30Z"
    - latency: 7.369428ms
      message: 'load-balancer-api-external: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:07:30Z"
    - latency: 55.51699ms
      message: 'load-balancer-api-external: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:30Z"
    - latency: 6.902171ms
      message: 'load-balancer-api-external: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:06:30Z"
    - latency: 50.164424ms
      message: 'load-balancer-api-external: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 6.04332ms
      message: 'load-balancer-api-external: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 57.166184ms
      message: 'load-balancer-api-external: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 9.780075ms
      message: 'load-balancer-api-external: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:04:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "110016"
    uid: 2b1cd677-d83a-4c39-8a82-30a27c70a4ed
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:08:30Z"
      message: 'load-balancer-api-internal: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.689499ms
      message: 'load-balancer-api-internal: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:30Z"
    - latency: 7.108123ms
      message: 'load-balancer-api-internal: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:08:30Z"
    - latency: 56.658813ms
      message: 'load-balancer-api-internal: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:30Z"
    - latency: 7.396116ms
      message: 'load-balancer-api-internal: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:07:30Z"
    - latency: 55.507966ms
      message: 'load-balancer-api-internal: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:30Z"
    - latency: 6.848984ms
      message: 'load-balancer-api-internal: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:06:30Z"
    - latency: 50.128857ms
      message: 'load-balancer-api-internal: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 6.073116ms
      message: 'load-balancer-api-internal: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 51.399769ms
      message: 'load-balancer-api-internal: tcp connection to ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 9.806606ms
      message: 'load-balancer-api-internal: resolved host name ae753dff0150c41c2b123ad91ad36b56-7d3113d1bc7bb9ad.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:04:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-network-check-target-ip-10-0-130-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "106992"
    uid: 4cd24a0f-43fd-41b8-8484-251da7b6e08b
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:09:30Z"
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.703µs
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 1.008571ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 1.588969ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:03:30Z"
    - latency: 927.296µs
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:02:30Z"
    - latency: 1.540608ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:01:30Z"
    - latency: 904.557µs
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:00:30Z"
    - latency: 902.489µs
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:59:30Z"
    - latency: 912.672µs
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:58:30Z"
    - latency: 1.310915ms
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:57:30Z"
    - latency: 876.875µs
      message: 'network-check-target-ip-10-0-130-229: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-network-check-target-ip-10-0-135-181
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "106993"
    uid: dcc1fd6c-d2b5-461d-a73c-def0ae660096
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:09:30Z"
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.67667ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 2.568132ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 2.755576ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:03:30Z"
    - latency: 2.265008ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:02:30Z"
    - latency: 2.486034ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:01:30Z"
    - latency: 2.963415ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:00:30Z"
    - latency: 2.257148ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:59:30Z"
    - latency: 2.488344ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:58:30Z"
    - latency: 2.207819ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:57:30Z"
    - latency: 1.982582ms
      message: 'network-check-target-ip-10-0-135-181: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-network-check-target-ip-10-0-142-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "106995"
    uid: dbfb1c66-5de7-4c8c-87fc-1a86199e0efc
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:09:30Z"
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.667867ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 2.640817ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 2.676072ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:03:30Z"
    - latency: 2.42191ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:02:30Z"
    - latency: 2.12032ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:01:30Z"
    - latency: 2.306347ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:00:30Z"
    - latency: 2.284612ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:59:30Z"
    - latency: 2.489921ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:58:30Z"
    - latency: 2.388379ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:57:30Z"
    - latency: 2.047852ms
      message: 'network-check-target-ip-10-0-142-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T15:56:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T15:02:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-229-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-229.us-west-2.compute.internal
      uid: 1723615c-d9ab-4148-9739-3129dd6621a3
    resourceVersion: "110014"
    uid: ae74a1d0-926d-4de6-a42b-f7b12435f55d
  spec:
    sourcePod: network-check-source-6f78d59f99-p8v6z
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:08:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 957.192µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:30Z"
    - latency: 1.95714ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:08:30Z"
    - latency: 1.394748ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:30Z"
    - latency: 1.844362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:07:30Z"
    - latency: 881.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:30Z"
    - latency: 1.927092ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:06:30Z"
    - latency: 888.035µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 1.781829ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:05:30Z"
    - latency: 1.008904ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:04:30Z"
    - latency: 1.801148ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:04:30Z"
kind: List
metadata:
  resourceVersion: ""