apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "44472"
    uid: 23c2a7ea-7ab7-4c90-86c6-663cee3b0813
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:15:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 952.141µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:36:53Z"
    - latency: 742.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:35:53Z"
    - latency: 946.567µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:34:53Z"
    - latency: 1.019643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:33:53Z"
    - latency: 923.705µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 962.633µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 1.404632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 1.085926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 1.00248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 1.045648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:27:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "40078"
    uid: b0b2bb65-facb-48a9-b81d-079b4dcbc598
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:14:53Z"
      message: 'load-balancer-api-external: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.626496ms
      message: 'load-balancer-api-external: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 11.581553ms
      message: 'load-balancer-api-external: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 4.300173ms
      message: 'load-balancer-api-external: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 7.881057ms
      message: 'load-balancer-api-external: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 3.705258ms
      message: 'load-balancer-api-external: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 9.855579ms
      message: 'load-balancer-api-external: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 3.863805ms
      message: 'load-balancer-api-external: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 8.268774ms
      message: 'load-balancer-api-external: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 3.721122ms
      message: 'load-balancer-api-external: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 9.199539ms
      message: 'load-balancer-api-external: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:28:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "40077"
    uid: 56de54da-254a-4ced-a5c1-0c9e8abc8106
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:14:53Z"
      message: 'load-balancer-api-internal: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.125921ms
      message: 'load-balancer-api-internal: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 11.640008ms
      message: 'load-balancer-api-internal: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 4.902712ms
      message: 'load-balancer-api-internal: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 7.948142ms
      message: 'load-balancer-api-internal: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 3.674307ms
      message: 'load-balancer-api-internal: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 9.909138ms
      message: 'load-balancer-api-internal: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 3.839003ms
      message: 'load-balancer-api-internal: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 8.34489ms
      message: 'load-balancer-api-internal: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 4.333081ms
      message: 'load-balancer-api-internal: tcp connection to a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 9.280861ms
      message: 'load-balancer-api-internal: resolved host name a55535c11b44f42ba8c02f928b905529-9c644f33fcb2f126.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:28:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-139-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "44471"
    uid: 27cc3aa0-f054-4ad6-a066-115b3d301f30
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:15:53Z"
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.988402ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:36:53Z"
    - latency: 1.994144ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:35:53Z"
    - latency: 2.11132ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:34:53Z"
    - latency: 2.136422ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:33:53Z"
    - latency: 1.916677ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 2.404937ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 2.053647ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 1.771944ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 2.427204ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 2.117476ms
      message: 'network-check-target-ip-10-0-139-217: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:27:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-139-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "44470"
    uid: 06e327f8-7b34-47a7-a4a9-3b97e9d9c0e4
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:15:53Z"
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.003409ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:36:53Z"
    - latency: 1.827417ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:35:53Z"
    - latency: 1.848076ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:34:53Z"
    - latency: 1.861148ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:33:53Z"
    - latency: 1.978119ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 1.99062ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 1.95797ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 1.950983ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 1.880142ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 1.804403ms
      message: 'network-check-target-ip-10-0-139-85: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:27:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-ip-10-0-143-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "44469"
    uid: 68809e72-db93-456e-8298-46bc2d4dde57
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:15:53Z"
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208721ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:36:53Z"
    - latency: 920.256µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:35:53Z"
    - latency: 790.532µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:34:53Z"
    - latency: 1.119745ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:33:53Z"
    - latency: 780.754µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 1.099203ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 931.695µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 744.065µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 1.74511ms
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 791.926µs
      message: 'network-check-target-ip-10-0-143-189: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:27:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-21T14:08:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-189-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-189.ec2.internal
      uid: 6addb081-65f2-4185-b518-a417241bb7ea
    resourceVersion: "40076"
    uid: f83c1829-1664-4719-a754-7ce8d13c8034
  spec:
    sourcePod: network-check-source-7f44b6dd87-v2mgt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-21T14:14:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 800.057µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 1.835548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:32:53Z"
    - latency: 844.172µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 1.659675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:31:53Z"
    - latency: 745.829µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 1.879021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:30:53Z"
    - latency: 798.734µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 1.660961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:29:53Z"
    - latency: 792.912µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-21T14:28:53Z"
    - latency: 2.430903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-21T14:28:53Z"
kind: List
metadata:
  resourceVersion: ""