apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "22683"
    uid: a1ee1272-138d-4c6a-b077-8711ef37143c
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:30:19Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.146728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 893.414µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 1.029817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:19Z"
    - latency: 1.045136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:19Z"
    - latency: 1.397617ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:19Z"
    - latency: 995.275µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:19Z"
    - latency: 1.126512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:19Z"
    - latency: 902.646µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:19Z"
    - latency: 1.069489ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:19Z"
    - latency: 1.099763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "24026"
    uid: 3f3e3266-d970-4e90-ad05-1386cd53c7b4
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:29:19Z"
      message: 'load-balancer-api-external: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.845288ms
      message: 'load-balancer-api-external: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:19Z"
    - latency: 7.908238ms
      message: 'load-balancer-api-external: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:47:19Z"
    - latency: 5.564386ms
      message: 'load-balancer-api-external: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:19Z"
    - latency: 8.697952ms
      message: 'load-balancer-api-external: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:46:19Z"
    - latency: 4.287356ms
      message: 'load-balancer-api-external: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:19Z"
    - latency: 7.944807ms
      message: 'load-balancer-api-external: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:45:19Z"
    - latency: 4.5588ms
      message: 'load-balancer-api-external: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 8.580342ms
      message: 'load-balancer-api-external: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 5.425311ms
      message: 'load-balancer-api-external: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 7.844075ms
      message: 'load-balancer-api-external: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:43:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "24027"
    uid: 6f499ceb-da81-490c-8d9f-2998676b4a1d
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:29:19Z"
      message: 'load-balancer-api-internal: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.853604ms
      message: 'load-balancer-api-internal: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:19Z"
    - latency: 7.872654ms
      message: 'load-balancer-api-internal: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:47:19Z"
    - latency: 5.664905ms
      message: 'load-balancer-api-internal: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:19Z"
    - latency: 8.56986ms
      message: 'load-balancer-api-internal: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:46:19Z"
    - latency: 4.465617ms
      message: 'load-balancer-api-internal: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:19Z"
    - latency: 8.030493ms
      message: 'load-balancer-api-internal: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:45:19Z"
    - latency: 3.652053ms
      message: 'load-balancer-api-internal: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 8.629045ms
      message: 'load-balancer-api-internal: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 5.340031ms
      message: 'load-balancer-api-internal: tcp connection to adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 7.942983ms
      message: 'load-balancer-api-internal: resolved host name adcc64f7d2600419e93935a8740b2fe4-033c563a3619199e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:43:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-ip-10-0-128-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "22682"
    uid: 7e0432b8-4011-49a7-83be-059dac7c4c35
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:30:19Z"
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.276026ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 2.426084ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 1.98528ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:19Z"
    - latency: 2.436218ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:19Z"
    - latency: 2.116327ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:19Z"
    - latency: 1.991273ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:19Z"
    - latency: 2.25941ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:19Z"
    - latency: 2.286017ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:19Z"
    - latency: 2.557141ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:19Z"
    - latency: 2.389579ms
      message: 'network-check-target-ip-10-0-128-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-ip-10-0-134-167
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "22680"
    uid: a15ff58a-ddd7-49b8-8c9b-41d394886084
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:30:19Z"
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.302301ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 2.336481ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 2.515406ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:19Z"
    - latency: 2.495961ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:19Z"
    - latency: 2.65211ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:19Z"
    - latency: 2.587102ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:19Z"
    - latency: 2.487772ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:19Z"
    - latency: 2.190228ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:19Z"
    - latency: 2.550395ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:19Z"
    - latency: 2.409513ms
      message: 'network-check-target-ip-10-0-134-167: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-ip-10-0-139-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "22681"
    uid: 714722c9-c420-43cf-bd05-1421851ee07a
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:30:19Z"
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.648572ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 1.245929ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 1.026332ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:42:19Z"
    - latency: 897.831µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:41:19Z"
    - latency: 861.178µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:40:19Z"
    - latency: 798.976µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:39:19Z"
    - latency: 973.171µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:38:19Z"
    - latency: 869.252µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:37:19Z"
    - latency: 1.148155ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:36:19Z"
    - latency: 902.248µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:35:19Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T16:23:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9fbb092-c8cf-43b6-8740-b2d866f50814
    resourceVersion: "24025"
    uid: 3b05fad1-9104-4d7e-bd3d-3a255b72f439
  spec:
    sourcePod: network-check-source-7cbc45fddc-nkkrd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:29:19Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.164858ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:47:19Z"
    - latency: 1.955088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:47:19Z"
    - latency: 1.188535ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:46:19Z"
    - latency: 1.624771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:46:19Z"
    - latency: 1.123383ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:45:19Z"
    - latency: 1.807028ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:45:19Z"
    - latency: 1.600126ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 2.029272ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:44:19Z"
    - latency: 862.151µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:43:19Z"
    - latency: 1.851901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:43:19Z"
kind: List
metadata:
  resourceVersion: ""