apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "22566"
    uid: 5addc348-0d53-4e59-8acb-bf7dc72fc7ec
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.227469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:25Z"
    - latency: 1.195187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:25Z"
    - latency: 1.119459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:25Z"
    - latency: 838.778µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 1.225927ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 1.252133ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 1.631793ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 1.311666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 1.240485ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:25Z"
    - latency: 1.10174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "21138"
    uid: 58d2e2d4-fb51-4ed2-ab5e-a741c2a8b15f
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:50:25Z"
      message: 'load-balancer-api-external: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.552406ms
      message: 'load-balancer-api-external: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 10.603418ms
      message: 'load-balancer-api-external: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 5.017175ms
      message: 'load-balancer-api-external: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 7.856341ms
      message: 'load-balancer-api-external: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 4.858201ms
      message: 'load-balancer-api-external: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 7.415746ms
      message: 'load-balancer-api-external: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 5.40074ms
      message: 'load-balancer-api-external: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 6.848149ms
      message: 'load-balancer-api-external: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 5.448753ms
      message: 'load-balancer-api-external: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 12.068329ms
      message: 'load-balancer-api-external: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:58:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "21137"
    uid: 74f8591b-48f3-4164-bf7b-ab4a97fe9366
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:50:25Z"
      message: 'load-balancer-api-internal: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.614759ms
      message: 'load-balancer-api-internal: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 10.576903ms
      message: 'load-balancer-api-internal: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 5.07002ms
      message: 'load-balancer-api-internal: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 7.773659ms
      message: 'load-balancer-api-internal: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 6.275678ms
      message: 'load-balancer-api-internal: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 7.387806ms
      message: 'load-balancer-api-internal: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 5.171361ms
      message: 'load-balancer-api-internal: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 6.749383ms
      message: 'load-balancer-api-internal: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 5.486679ms
      message: 'load-balancer-api-internal: tcp connection to a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 12.020573ms
      message: 'load-balancer-api-internal: resolved host name a57899a7ba6a646e68ef9d106b8b59f3-b2ebf0ffa61c1c0b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:58:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-network-check-target-ip-10-0-130-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "22563"
    uid: 1d53c317-d853-477e-87ec-2f71aec32744
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:25Z"
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.374414ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:25Z"
    - latency: 1.369926ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:25Z"
    - latency: 1.491981ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:25Z"
    - latency: 1.222387ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 898.26µs
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 1.055846ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 1.153008ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 939.39µs
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 898.426µs
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:25Z"
    - latency: 1.008539ms
      message: 'network-check-target-ip-10-0-130-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-network-check-target-ip-10-0-138-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "22564"
    uid: 1361d63f-bb79-457d-847c-9aaa15fa33f7
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:25Z"
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.214624ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:25Z"
    - latency: 2.067098ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:25Z"
    - latency: 2.197102ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:25Z"
    - latency: 1.906406ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 1.652233ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 1.735112ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 1.997254ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 2.191516ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 2.136629ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:25Z"
    - latency: 2.077662ms
      message: 'network-check-target-ip-10-0-138-138: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-network-check-target-ip-10-0-143-227
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "22565"
    uid: 3dbbaa85-ea69-4084-b0cb-4729f3e9016c
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:51:25Z"
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.279974ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:05:25Z"
    - latency: 2.347784ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:04:25Z"
    - latency: 2.27199ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:03:25Z"
    - latency: 2.27398ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 2.230123ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 2.211362ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 2.16596ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 2.576525ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 2.55972ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:57:25Z"
    - latency: 2.424262ms
      message: 'network-check-target-ip-10-0-143-227: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:56:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T11:44:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-200.ec2.internal
      uid: c828b56c-c607-41c7-bbd5-1cc7f2f7ab7b
    resourceVersion: "21136"
    uid: ea3421a1-8fb7-4741-a5bf-7685842b8863
  spec:
    sourcePod: network-check-source-989f8b8dc-6cc7x
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T11:50:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 931.913µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 2.275006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:02:25Z"
    - latency: 959.891µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 2.18418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:01:25Z"
    - latency: 929.09µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 1.803737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T12:00:25Z"
    - latency: 1.239175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 2.122937ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:59:25Z"
    - latency: 920.14µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T11:58:25Z"
    - latency: 2.574716ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T11:58:25Z"
kind: List
metadata:
  resourceVersion: ""