apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "21566"
    uid: aa2cee53-5c9d-44fa-96b3-4173805b910f
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:47:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 845.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:01:52Z"
    - latency: 1.292012ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:52Z"
    - latency: 916.444µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:52Z"
    - latency: 774.045µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 805.475µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 1.052991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 1.341279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 1.097111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 1.145055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:52Z"
    - latency: 1.432075ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:52:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "20235"
    uid: 86c2605f-672e-4f5b-846e-9399611803d6
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:46:52Z"
      message: 'load-balancer-api-external: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.321983ms
      message: 'load-balancer-api-external: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 9.27028ms
      message: 'load-balancer-api-external: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 5.610223ms
      message: 'load-balancer-api-external: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 7.722784ms
      message: 'load-balancer-api-external: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 5.55183ms
      message: 'load-balancer-api-external: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 8.499166ms
      message: 'load-balancer-api-external: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 5.618976ms
      message: 'load-balancer-api-external: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 8.532605ms
      message: 'load-balancer-api-external: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 6.911181ms
      message: 'load-balancer-api-external: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 9.6914ms
      message: 'load-balancer-api-external: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "20236"
    uid: 6bfbcaf7-4366-47c6-9087-47281ce9aee5
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:46:52Z"
      message: 'load-balancer-api-internal: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.463593ms
      message: 'load-balancer-api-internal: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 9.286401ms
      message: 'load-balancer-api-internal: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 7.003127ms
      message: 'load-balancer-api-internal: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 7.768466ms
      message: 'load-balancer-api-internal: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 5.593009ms
      message: 'load-balancer-api-internal: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 8.585447ms
      message: 'load-balancer-api-internal: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 5.242652ms
      message: 'load-balancer-api-internal: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 8.506426ms
      message: 'load-balancer-api-internal: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 6.980096ms
      message: 'load-balancer-api-internal: tcp connection to a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 9.869464ms
      message: 'load-balancer-api-internal: resolved host name a02a453c93518445492c708b3b388bf1-2230622eb921ce79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:54:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-ip-10-0-134-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "21563"
    uid: 8b6344ed-16e3-4505-b482-e85f82ba5aee
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:47:52Z"
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.465µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:01:52Z"
    - latency: 939.665µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:52Z"
    - latency: 1.140707ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:52Z"
    - latency: 717.535µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 1.168795ms
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 812.419µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 773.208µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 791.762µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 818.374µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:52Z"
    - latency: 704.585µs
      message: 'network-check-target-ip-10-0-134-39: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:52:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-ip-10-0-140-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "21564"
    uid: 31c914db-9290-4fef-af07-4c60ea437555
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:47:52Z"
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.702186ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:01:52Z"
    - latency: 2.328266ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:52Z"
    - latency: 2.061028ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:52Z"
    - latency: 2.125222ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 2.16347ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 2.405634ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 2.082053ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 2.471649ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 2.588991ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:52Z"
    - latency: 2.19661ms
      message: 'network-check-target-ip-10-0-140-125: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:52:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-ip-10-0-142-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "21565"
    uid: fdbbd583-11da-43b8-aa66-12b1287c3ec8
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:47:52Z"
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.215242ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:01:52Z"
    - latency: 2.132525ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T21:00:52Z"
    - latency: 1.841763ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:59:52Z"
    - latency: 1.787614ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 1.953802ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 1.903179ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 1.980931ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 2.167354ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 2.172488ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:53:52Z"
    - latency: 2.039795ms
      message: 'network-check-target-ip-10-0-142-227: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:52:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-39-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-39.ec2.internal
      uid: fa663ae1-7b42-4760-bd59-b66f641491f1
    resourceVersion: "20234"
    uid: 12f392a5-d37e-4266-8659-7666ca96bb11
  spec:
    sourcePod: network-check-source-989f8b8dc-zk2lg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T20:46:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108378ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 1.800673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:58:52Z"
    - latency: 813.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 1.576506ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:57:52Z"
    - latency: 880.502µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 2.097244ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:56:52Z"
    - latency: 759.146µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 1.676711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:55:52Z"
    - latency: 1.317145ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:54:52Z"
    - latency: 2.243653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:54:52Z"
kind: List
metadata:
  resourceVersion: ""