apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "19021"
    uid: 12c4b6f3-865b-472c-8423-9f18ed48c38f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:28:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.03369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 1.016541ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 1.127177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:40:58Z"
    - latency: 921.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:39:58Z"
    - latency: 1.416614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:38:58Z"
    - latency: 1.249698ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:37:58Z"
    - latency: 977.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:36:58Z"
    - latency: 972.193µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:35:58Z"
    - latency: 1.153179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:34:58Z"
    - latency: 902.686µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "20397"
    uid: d1e48ebc-26e6-409b-a37a-396d8139d598
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:27:58Z"
      message: 'load-balancer-api-external: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.475388ms
      message: 'load-balancer-api-external: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:45:58Z"
    - latency: 12.744448ms
      message: 'load-balancer-api-external: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:45:58Z"
    - latency: 3.670883ms
      message: 'load-balancer-api-external: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:44:58Z"
    - latency: 8.548505ms
      message: 'load-balancer-api-external: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:44:58Z"
    - latency: 4.910933ms
      message: 'load-balancer-api-external: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:43:58Z"
    - latency: 10.168748ms
      message: 'load-balancer-api-external: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:43:58Z"
    - latency: 4.69572ms
      message: 'load-balancer-api-external: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 8.483774ms
      message: 'load-balancer-api-external: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 3.344187ms
      message: 'load-balancer-api-external: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 8.161079ms
      message: 'load-balancer-api-external: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:41:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "20398"
    uid: 9ef0a879-6945-4e11-ad1c-5192bfa9056c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:27:58Z"
      message: 'load-balancer-api-internal: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.902174ms
      message: 'load-balancer-api-internal: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:45:58Z"
    - latency: 12.612166ms
      message: 'load-balancer-api-internal: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:45:58Z"
    - latency: 5.236227ms
      message: 'load-balancer-api-internal: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:44:58Z"
    - latency: 8.465707ms
      message: 'load-balancer-api-internal: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:44:58Z"
    - latency: 4.957814ms
      message: 'load-balancer-api-internal: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:43:58Z"
    - latency: 10.12313ms
      message: 'load-balancer-api-internal: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:43:58Z"
    - latency: 4.672963ms
      message: 'load-balancer-api-internal: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 8.395556ms
      message: 'load-balancer-api-internal: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 3.40455ms
      message: 'load-balancer-api-internal: tcp connection to a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 8.06822ms
      message: 'load-balancer-api-internal: resolved host name a68fa96c039c04c568dbec7439b665bc-be49f50109ba4832.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:41:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-network-check-target-ip-10-0-132-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "19018"
    uid: 894cd42b-bfcd-4ede-81b5-9a410aede35b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:28:58Z"
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 811.744µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 890.899µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 882.372µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:40:58Z"
    - latency: 723.215µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:39:58Z"
    - latency: 1.737656ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:38:58Z"
    - latency: 843.837µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:37:58Z"
    - latency: 1.258694ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:36:58Z"
    - latency: 764.678µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:35:58Z"
    - latency: 1.400526ms
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:34:58Z"
    - latency: 737.762µs
      message: 'network-check-target-ip-10-0-132-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-network-check-target-ip-10-0-139-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "19020"
    uid: 22f7e6a9-60fb-4240-9c39-6daaab9a6b15
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:28:58Z"
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.199525ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 2.706256ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 2.127845ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:40:58Z"
    - latency: 2.221766ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:39:58Z"
    - latency: 2.204903ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:38:58Z"
    - latency: 2.156389ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:37:58Z"
    - latency: 2.092487ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:36:58Z"
    - latency: 2.159718ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:35:58Z"
    - latency: 2.033085ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:34:58Z"
    - latency: 2.093869ms
      message: 'network-check-target-ip-10-0-139-82: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-network-check-target-ip-10-0-142-189
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "19019"
    uid: 41cc10f6-1a39-4628-88b7-e70a033776e8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:28:58Z"
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.980175ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 1.909469ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 1.97371ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:40:58Z"
    - latency: 1.852776ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:39:58Z"
    - latency: 1.878387ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:38:58Z"
    - latency: 1.902522ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:37:58Z"
    - latency: 2.164534ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:36:58Z"
    - latency: 1.859274ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:35:58Z"
    - latency: 1.753841ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:34:58Z"
    - latency: 1.652308ms
      message: 'network-check-target-ip-10-0-142-189: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:33:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T13:21:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-223-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-223.ec2.internal
      uid: 0fc1d4a3-20e6-4c42-ad35-57caa6079d0e
    resourceVersion: "20396"
    uid: 66dc7c57-71e6-41c6-ac0c-b04a043e5cfb
  spec:
    sourcePod: network-check-source-7bc5b6bf85-w9h89
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T13:27:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 771.738µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:45:58Z"
    - latency: 3.511302ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:45:58Z"
    - latency: 1.376242ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:44:58Z"
    - latency: 1.591454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:44:58Z"
    - latency: 804.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:43:58Z"
    - latency: 1.700295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:43:58Z"
    - latency: 849.085µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 1.812741ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:42:58Z"
    - latency: 899.624µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T13:41:58Z"
    - latency: 1.859392ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T13:41:58Z"
kind: List
metadata:
  resourceVersion: ""