apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "52855"
    uid: 955130ef-4a29-42db-b64a-0781cff43a4b
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:09:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 911.291µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 1.222592ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 1.241759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 802.803µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 1.184228ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:33:35Z"
    - latency: 872.31µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:32:35Z"
    - latency: 903.683µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:31:35Z"
    - latency: 871.678µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:30:35Z"
    - latency: 1.03016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:29:35Z"
    - latency: 1.13355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:28:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "54033"
    uid: c681a5d9-7f74-49e4-b8e1-3926092c4ac0
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:08:35Z"
      message: 'load-balancer-api-external: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.909704ms
      message: 'load-balancer-api-external: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:38:35Z"
    - latency: 6.64334ms
      message: 'load-balancer-api-external: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:38:35Z"
    - latency: 4.336533ms
      message: 'load-balancer-api-external: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 7.780367ms
      message: 'load-balancer-api-external: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 5.355318ms
      message: 'load-balancer-api-external: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 6.534391ms
      message: 'load-balancer-api-external: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 4.437875ms
      message: 'load-balancer-api-external: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 6.598925ms
      message: 'load-balancer-api-external: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 3.754447ms
      message: 'load-balancer-api-external: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 8.248194ms
      message: 'load-balancer-api-external: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "54034"
    uid: 1d914917-2bd8-46b3-be21-eca135ebc30c
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:08:35Z"
      message: 'load-balancer-api-internal: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.906064ms
      message: 'load-balancer-api-internal: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:38:35Z"
    - latency: 6.611704ms
      message: 'load-balancer-api-internal: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:38:35Z"
    - latency: 4.363101ms
      message: 'load-balancer-api-internal: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 7.743194ms
      message: 'load-balancer-api-internal: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 5.360994ms
      message: 'load-balancer-api-internal: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 6.500164ms
      message: 'load-balancer-api-internal: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 5.10227ms
      message: 'load-balancer-api-internal: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 6.573544ms
      message: 'load-balancer-api-internal: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 3.852099ms
      message: 'load-balancer-api-internal: tcp connection to a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 8.212914ms
      message: 'load-balancer-api-internal: resolved host name a5432c765e5354b3bb73619c912ff0f1-b2f0e6506b6d01a1.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:34:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-ip-10-0-128-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "52853"
    uid: ee23db54-db64-4be7-8288-533dc89c7df3
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:09:35Z"
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.989864ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 2.082227ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 1.962592ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 1.746456ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 1.784052ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:33:35Z"
    - latency: 1.843221ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:32:35Z"
    - latency: 2.191886ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:31:35Z"
    - latency: 1.962342ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:30:35Z"
    - latency: 1.846912ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:29:35Z"
    - latency: 1.776359ms
      message: 'network-check-target-ip-10-0-128-70: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:28:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-ip-10-0-129-199
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "52854"
    uid: 154711fd-c74f-48ef-bc0d-75b2364c3f4e
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:09:35Z"
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.076236ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 2.339549ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 2.498681ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 2.243402ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 2.291353ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:33:35Z"
    - latency: 2.338299ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:32:35Z"
    - latency: 1.902447ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:31:35Z"
    - latency: 2.183249ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:30:35Z"
    - latency: 2.307921ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:29:35Z"
    - latency: 2.195218ms
      message: 'network-check-target-ip-10-0-129-199: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:28:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-ip-10-0-142-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "52852"
    uid: 927dd981-cae1-4782-9dbf-857cbc0a1b38
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:09:35Z"
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.264µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 841.11µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 1.025028ms
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 912.074µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 874.545µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:33:35Z"
    - latency: 1.132384ms
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:32:35Z"
    - latency: 792.343µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:31:35Z"
    - latency: 947.325µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:30:35Z"
    - latency: 862.834µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:29:35Z"
    - latency: 939.517µs
      message: 'network-check-target-ip-10-0-142-99: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:28:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T03:02:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-99.ec2.internal
      uid: e7f1d1c4-b3a4-461d-8f04-75f7af2785a3
    resourceVersion: "54032"
    uid: 973d1d2f-dcb8-4101-b794-17c879d64910
  spec:
    sourcePod: network-check-source-989f8b8dc-ddgb2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T03:08:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.18738ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:38:35Z"
    - latency: 1.59774ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:38:35Z"
    - latency: 956.316µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 2.01696ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:37:35Z"
    - latency: 1.046638ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 1.810583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:36:35Z"
    - latency: 923.517µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 1.598447ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:35:35Z"
    - latency: 789.156µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T03:34:35Z"
    - latency: 1.823775ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T03:34:35Z"
kind: List
metadata:
  resourceVersion: ""