apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "30654"
    uid: 15bf2e7a-195d-4e5a-b8a7-b5b858d6250f
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:04:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.777608ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:11:38Z"
    - latency: 1.245501ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:10:38Z"
    - latency: 1.092216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 3.200333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 1.296011ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 1.339769ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 2.254071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 1.406326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:04:38Z"
    - latency: 1.941192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:03:38Z"
    - latency: 1.375657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "27425"
    uid: cbbcab00-35c4-4c8a-937c-9b1498841593
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:03:38Z"
      message: 'load-balancer-api-external: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 20.58773ms
      message: 'load-balancer-api-external: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 8.918791ms
      message: 'load-balancer-api-external: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 18.544606ms
      message: 'load-balancer-api-external: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 9.630213ms
      message: 'load-balancer-api-external: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 17.1757ms
      message: 'load-balancer-api-external: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 10.257493ms
      message: 'load-balancer-api-external: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 17.33028ms
      message: 'load-balancer-api-external: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 7.295248ms
      message: 'load-balancer-api-external: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 21.153111ms
      message: 'load-balancer-api-external: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 11.284106ms
      message: 'load-balancer-api-external: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:05:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:38Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "27426"
    uid: d090959b-19a8-436c-beeb-660acb536526
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:03:38Z"
      message: 'load-balancer-api-internal: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 19.005878ms
      message: 'load-balancer-api-internal: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 3.880158ms
      message: 'load-balancer-api-internal: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 18.897469ms
      message: 'load-balancer-api-internal: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 4.872814ms
      message: 'load-balancer-api-internal: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 16.735738ms
      message: 'load-balancer-api-internal: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 5.480789ms
      message: 'load-balancer-api-internal: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 17.903227ms
      message: 'load-balancer-api-internal: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 2.208605ms
      message: 'load-balancer-api-internal: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 16.98599ms
      message: 'load-balancer-api-internal: tcp connection to a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 7.402401ms
      message: 'load-balancer-api-internal: resolved host name a2b5a87ca036d4590957ebd1a53db251-0e0214b1a4a6ecbc.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:05:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-network-check-target-ip-10-0-128-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "30653"
    uid: 88c5ab94-c6bd-4ef8-a817-66ea63d82187
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:04:38Z"
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.814324ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:11:38Z"
    - latency: 2.48165ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:10:38Z"
    - latency: 2.239997ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 2.637322ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 2.659982ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 2.479471ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 2.163056ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 2.438643ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:04:38Z"
    - latency: 3.954516ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:03:38Z"
    - latency: 2.154407ms
      message: 'network-check-target-ip-10-0-128-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-network-check-target-ip-10-0-131-114
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "30651"
    uid: e20ff4c7-6b5d-4fe1-9761-2873c2fd2753
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:04:38Z"
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.906197ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:11:38Z"
    - latency: 2.411022ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:10:38Z"
    - latency: 1.962957ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 5.346341ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 2.247813ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 2.39095ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 2.566825ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 2.629375ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:04:38Z"
    - latency: 2.85675ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:03:38Z"
    - latency: 2.489438ms
      message: 'network-check-target-ip-10-0-131-114: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-network-check-target-ip-10-0-143-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "30650"
    uid: 443b014f-6817-4065-962e-846171ea25b5
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:04:38Z"
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.336841ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:11:38Z"
    - latency: 1.225565ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:10:38Z"
    - latency: 945.326µs
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 842.158µs
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 980.471µs
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 989.772µs
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 2.602692ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 1.562983ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:04:38Z"
    - latency: 1.519385ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:03:38Z"
    - latency: 1.001385ms
      message: 'network-check-target-ip-10-0-143-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:02:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T11:57:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-70.ec2.internal
      uid: 8d6e3167-b341-4336-9482-38c3e291a4fd
    resourceVersion: "27423"
    uid: 8a7395fa-d73d-4093-bb61-0bcb40ec9575
  spec:
    sourcePod: network-check-source-6f78d59f99-d5ppl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:03:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.120573ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 1.968018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:09:38Z"
    - latency: 2.59161ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 3.738126ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:08:38Z"
    - latency: 1.058026ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 1.741756ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:07:38Z"
    - latency: 1.056447ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 2.538915ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:06:38Z"
    - latency: 869.965µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T12:05:38Z"
    - latency: 3.207071ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T12:05:38Z"
kind: List
metadata:
  resourceVersion: ""