apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "51299"
    uid: 30bc8013-f62c-4aa3-b9a7-1cc93814ec09
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:09:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 981.522µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:30:04Z"
    - latency: 1.057678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:29:04Z"
    - latency: 1.331697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:28:04Z"
    - latency: 932.197µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:27:04Z"
    - latency: 1.208611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 1.434517ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 1.296748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 996.795µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 1.019527ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 970.307µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "47565"
    uid: 7b597e73-d55a-4ebf-9ad9-c2986ba452ca
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:08:04Z"
      message: 'load-balancer-api-external: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.351396ms
      message: 'load-balancer-api-external: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 9.920061ms
      message: 'load-balancer-api-external: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 4.529767ms
      message: 'load-balancer-api-external: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 8.655783ms
      message: 'load-balancer-api-external: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 5.437404ms
      message: 'load-balancer-api-external: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 9.26103ms
      message: 'load-balancer-api-external: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 5.298287ms
      message: 'load-balancer-api-external: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 8.674274ms
      message: 'load-balancer-api-external: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 4.376743ms
      message: 'load-balancer-api-external: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 9.915589ms
      message: 'load-balancer-api-external: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:22:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "47566"
    uid: bf96f1ab-a35d-48e0-8263-cfdf193fc605
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:08:04Z"
      message: 'load-balancer-api-internal: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.325152ms
      message: 'load-balancer-api-internal: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 10.003673ms
      message: 'load-balancer-api-internal: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 5.341644ms
      message: 'load-balancer-api-internal: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 8.553188ms
      message: 'load-balancer-api-internal: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 5.511373ms
      message: 'load-balancer-api-internal: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 9.302122ms
      message: 'load-balancer-api-internal: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 5.280182ms
      message: 'load-balancer-api-internal: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 8.74082ms
      message: 'load-balancer-api-internal: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 4.132223ms
      message: 'load-balancer-api-internal: tcp connection to a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 9.960106ms
      message: 'load-balancer-api-internal: resolved host name a3f3d6194705a4e208de19b49e8e7ab6-1a1c894891d743ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:22:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-ip-10-0-130-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "51297"
    uid: 02d6ec9c-e6dc-47e8-8e31-5d480baf9ccd
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:09:04Z"
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.328581ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:30:04Z"
    - latency: 2.518949ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:29:04Z"
    - latency: 2.561454ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:28:04Z"
    - latency: 2.418466ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:27:04Z"
    - latency: 2.353882ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 2.553722ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 1.982061ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 2.526013ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 2.157426ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 2.434214ms
      message: 'network-check-target-ip-10-0-130-125: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-ip-10-0-133-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "51298"
    uid: 68c53a3d-05c7-451e-92f0-38786bde6755
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:09:04Z"
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.163481ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:30:04Z"
    - latency: 2.364291ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:29:04Z"
    - latency: 2.426672ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:28:04Z"
    - latency: 2.472503ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:27:04Z"
    - latency: 2.236866ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 2.41264ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 2.273537ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 2.658776ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 2.563601ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 2.475824ms
      message: 'network-check-target-ip-10-0-133-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-ip-10-0-142-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "51296"
    uid: 0f4dc1fb-861c-488e-a9f9-fb5d9e8ebc6b
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:09:04Z"
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.42732ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:30:04Z"
    - latency: 1.026667ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:29:04Z"
    - latency: 965.362µs
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:28:04Z"
    - latency: 951.571µs
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:27:04Z"
    - latency: 1.654099ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 933.091µs
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 1.07333ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 1.447976ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 986.961µs
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 1.302324ms
      message: 'network-check-target-ip-10-0-142-105: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:21:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T14:02:03Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-105.ec2.internal
      uid: 0a42ad16-d41d-43ef-8443-6db909b45307
    resourceVersion: "47564"
    uid: 890b68a1-d274-401e-b7e0-824481497e62
  spec:
    sourcePod: network-check-source-685456655f-9jxpg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T14:08:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.349953ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 1.79047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:26:04Z"
    - latency: 952.703µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 2.128604ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:25:04Z"
    - latency: 944.719µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 1.918292ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:24:04Z"
    - latency: 1.015506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 1.879062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:23:04Z"
    - latency: 1.184531ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:22:04Z"
    - latency: 1.815814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:22:04Z"
kind: List
metadata:
  resourceVersion: ""