apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "29713"
    uid: 5cb8b0c1-147c-4f2f-b4dc-07184846c5d8
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:57:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.104233ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:04:23Z"
    - latency: 1.678802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:03:23Z"
    - latency: 843.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 1.055616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 966.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 917.08µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 1.26251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:23Z"
    - latency: 1.139597ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:57:23Z"
    - latency: 980.237µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:56:23Z"
    - latency: 958.066µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "28452"
    uid: 47e26d27-d94a-4f3e-bb90-f1b835f40017
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:56:24Z"
      message: 'load-balancer-api-external: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.856126ms
      message: 'load-balancer-api-external: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:24Z"
    - latency: 8.35789ms
      message: 'load-balancer-api-external: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 4.746743ms
      message: 'load-balancer-api-external: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:24Z"
    - latency: 8.535441ms
      message: 'load-balancer-api-external: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 5.488593ms
      message: 'load-balancer-api-external: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:24Z"
    - latency: 9.972901ms
      message: 'load-balancer-api-external: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 5.256127ms
      message: 'load-balancer-api-external: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:24Z"
    - latency: 10.088215ms
      message: 'load-balancer-api-external: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 4.822449ms
      message: 'load-balancer-api-external: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:24Z"
    - latency: 9.723695ms
      message: 'load-balancer-api-external: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T16:58:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "28451"
    uid: ef0904b8-80f1-42b0-a9dd-07349bfc6e1a
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:56:24Z"
      message: 'load-balancer-api-internal: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.997572ms
      message: 'load-balancer-api-internal: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:24Z"
    - latency: 8.225364ms
      message: 'load-balancer-api-internal: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 4.667093ms
      message: 'load-balancer-api-internal: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:24Z"
    - latency: 8.566739ms
      message: 'load-balancer-api-internal: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 5.540765ms
      message: 'load-balancer-api-internal: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:24Z"
    - latency: 10.001493ms
      message: 'load-balancer-api-internal: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 5.228898ms
      message: 'load-balancer-api-internal: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:24Z"
    - latency: 10.172487ms
      message: 'load-balancer-api-internal: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 4.046674ms
      message: 'load-balancer-api-internal: tcp connection to a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:24Z"
    - latency: 9.60748ms
      message: 'load-balancer-api-internal: resolved host name a94f2ee36e89c4cdabeebee04aaae0ed-25f91470fe349f46.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T16:58:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-network-check-target-ip-10-0-128-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "29712"
    uid: 8852c533-1713-487d-bb9a-5efcfce90511
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:57:24Z"
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.104712ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:04:23Z"
    - latency: 2.399195ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:03:23Z"
    - latency: 2.282047ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 2.060855ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 2.330624ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 2.223239ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 2.771009ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:23Z"
    - latency: 2.223169ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:57:23Z"
    - latency: 2.24316ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:56:23Z"
    - latency: 2.257528ms
      message: 'network-check-target-ip-10-0-128-59: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-network-check-target-ip-10-0-141-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "29711"
    uid: dbbb1197-59e4-47cb-b573-fea9f17b5d3a
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:57:24Z"
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.260998ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:04:23Z"
    - latency: 2.297329ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:03:23Z"
    - latency: 2.52369ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 2.530314ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 2.452321ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 2.53683ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 2.431589ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:23Z"
    - latency: 2.420478ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:57:23Z"
    - latency: 2.899ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:56:23Z"
    - latency: 2.392057ms
      message: 'network-check-target-ip-10-0-141-105: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-network-check-target-ip-10-0-143-240
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "29710"
    uid: f4398677-648e-4925-9817-228ddaffc473
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:57:23Z"
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.542µs
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:04:23Z"
    - latency: 811.122µs
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:03:23Z"
    - latency: 773.543µs
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 773.411µs
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 1.040146ms
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 835.194µs
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 1.047486ms
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:23Z"
    - latency: 1.125781ms
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:57:23Z"
    - latency: 1.676152ms
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:56:23Z"
    - latency: 989.03µs
      message: 'network-check-target-ip-10-0-143-240: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T16:50:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-240-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-240.ec2.internal
      uid: c9673380-4bfc-46e6-92f7-16cfda995803
    resourceVersion: "28450"
    uid: 7b2b4804-ac31-4b30-9a07-016a30e1952c
  spec:
    sourcePod: network-check-source-dbd9cf844-wxg56
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T16:56:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 951.206µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 1.623841ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:02:23Z"
    - latency: 909.818µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 1.702063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:01:23Z"
    - latency: 1.367929ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 1.821536ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T17:00:23Z"
    - latency: 1.089909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 2.182191ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T16:59:23Z"
    - latency: 939.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T16:58:23Z"
    - latency: 1.815863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T16:58:23Z"
kind: List
metadata:
  resourceVersion: ""