apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39545"
    uid: f25ce580-7aa8-474a-a8ff-69a63b47e8a3
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 890.18µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:08Z"
    - latency: 902.848µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 1.112696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 914.294µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 955.728µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 1.069246ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 1.274663ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:15:08Z"
    - latency: 822.334µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:14:08Z"
    - latency: 1.17064ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:13:08Z"
    - latency: 1.14853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:12:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39006"
    uid: 9c0d0644-13d5-416b-ad9a-125389a551bd
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:38:08Z"
      message: 'load-balancer-api-external: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.629846ms
      message: 'load-balancer-api-external: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 8.342532ms
      message: 'load-balancer-api-external: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 4.337228ms
      message: 'load-balancer-api-external: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 12.545173ms
      message: 'load-balancer-api-external: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 5.574435ms
      message: 'load-balancer-api-external: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 8.305212ms
      message: 'load-balancer-api-external: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 6.079504ms
      message: 'load-balancer-api-external: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 8.970681ms
      message: 'load-balancer-api-external: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 5.553421ms
      message: 'load-balancer-api-external: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 9.875861ms
      message: 'load-balancer-api-external: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:16:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39005"
    uid: 9d70bc9e-9b14-4913-9a15-fd03568688be
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:38:08Z"
      message: 'load-balancer-api-internal: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.914623ms
      message: 'load-balancer-api-internal: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 8.366351ms
      message: 'load-balancer-api-internal: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 5.857215ms
      message: 'load-balancer-api-internal: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 12.535809ms
      message: 'load-balancer-api-internal: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 4.97875ms
      message: 'load-balancer-api-internal: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 8.357867ms
      message: 'load-balancer-api-internal: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 6.133928ms
      message: 'load-balancer-api-internal: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 9.041872ms
      message: 'load-balancer-api-internal: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 5.368749ms
      message: 'load-balancer-api-internal: tcp connection to acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 9.904528ms
      message: 'load-balancer-api-internal: resolved host name acd57e44645974634987fbb25f47769a-73d485a9fd59e9a7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:16:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-network-check-target-ip-10-0-131-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39544"
    uid: 8f9ad2b7-af6a-4bfa-bdad-04ddbc28b180
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:08Z"
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.370867ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:08Z"
    - latency: 2.657547ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 2.485482ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 2.349434ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 2.204588ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 2.079675ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 2.344262ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:15:08Z"
    - latency: 2.333025ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:14:08Z"
    - latency: 2.674659ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:13:08Z"
    - latency: 2.279072ms
      message: 'network-check-target-ip-10-0-131-128: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:12:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-network-check-target-ip-10-0-132-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39542"
    uid: 4197efb0-0efd-4d86-86f4-a30258ebde3e
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:08Z"
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.427µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:08Z"
    - latency: 987.297µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 1.034628ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 799.925µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 937.307µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 991.54µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 967.861µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:15:08Z"
    - latency: 822.304µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:14:08Z"
    - latency: 1.330538ms
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:13:08Z"
    - latency: 943.413µs
      message: 'network-check-target-ip-10-0-132-9: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:12:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-network-check-target-ip-10-0-143-106
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39543"
    uid: 1f09bb2e-9f45-4264-9995-ad86b9548da3
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:08Z"
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.271589ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:21:08Z"
    - latency: 2.678501ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 2.40574ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 2.092382ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 2.229473ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 2.403868ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 2.248655ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:15:08Z"
    - latency: 2.155263ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:14:08Z"
    - latency: 2.249747ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:13:08Z"
    - latency: 2.359194ms
      message: 'network-check-target-ip-10-0-143-106: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:12:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-9-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-9.ec2.internal
      uid: ee0b0e48-e2e4-48ec-ac1a-87d65403816c
    resourceVersion: "39004"
    uid: 478ed6fe-5442-4b29-a384-59cf8777563b
  spec:
    sourcePod: network-check-source-7cbc45fddc-28z94
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:38:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 748.178µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 1.702445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:20:08Z"
    - latency: 1.334252ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 2.01395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:19:08Z"
    - latency: 891.097µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 1.731511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:18:08Z"
    - latency: 788.471µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 2.05914ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:17:08Z"
    - latency: 770.117µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:16:08Z"
    - latency: 2.026374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:16:08Z"
kind: List
metadata:
  resourceVersion: ""