apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "56550"
    uid: d62b9661-c075-4183-a132-1fdd9fed3da1
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:57: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.125707ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:25:58Z"
    - latency: 1.151836ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:24:58Z"
    - latency: 1.186515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:23:58Z"
    - latency: 948.607µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:22:58Z"
    - latency: 979.043µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:21:58Z"
    - latency: 953.478µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 1.04566ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 1.153542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 876.889µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 1.121445ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "52080"
    uid: 77e14322-ea25-4e2e-bf8e-4b2d04a6bbee
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:56:58Z"
      message: 'load-balancer-api-external: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.338392ms
      message: 'load-balancer-api-external: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 8.837632ms
      message: 'load-balancer-api-external: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 4.137473ms
      message: 'load-balancer-api-external: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 7.708819ms
      message: 'load-balancer-api-external: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 4.117012ms
      message: 'load-balancer-api-external: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 8.946671ms
      message: 'load-balancer-api-external: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 3.317311ms
      message: 'load-balancer-api-external: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 8.097021ms
      message: 'load-balancer-api-external: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 4.755132ms
      message: 'load-balancer-api-external: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
    - latency: 8.663017ms
      message: 'load-balancer-api-external: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "52079"
    uid: e65c8012-1398-42c8-881b-9cb027e2a757
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:56:58Z"
      message: 'load-balancer-api-internal: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.346978ms
      message: 'load-balancer-api-internal: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 8.880936ms
      message: 'load-balancer-api-internal: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 4.336772ms
      message: 'load-balancer-api-internal: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 7.80573ms
      message: 'load-balancer-api-internal: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 5.122248ms
      message: 'load-balancer-api-internal: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 8.844236ms
      message: 'load-balancer-api-internal: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 5.345299ms
      message: 'load-balancer-api-internal: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 7.998431ms
      message: 'load-balancer-api-internal: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 4.752729ms
      message: 'load-balancer-api-internal: tcp connection to a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
    - latency: 8.692395ms
      message: 'load-balancer-api-internal: resolved host name a39142bd3959945aa80306d4e0b0868d-85a54202b8a5b53a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-network-check-target-ip-10-0-138-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "56549"
    uid: 6149afb4-694c-46d7-b927-33a8669d00ae
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:57:58Z"
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.403889ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:25:58Z"
    - latency: 2.229563ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:24:58Z"
    - latency: 2.560955ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:23:58Z"
    - latency: 2.361271ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:22:58Z"
    - latency: 2.066286ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:21:58Z"
    - latency: 2.383807ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 2.409467ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 2.379984ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 2.340484ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 2.223152ms
      message: 'network-check-target-ip-10-0-138-126: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-network-check-target-ip-10-0-142-151
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "56547"
    uid: 184acc49-1ee1-49a0-8552-0372004a194c
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:57:58Z"
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.208274ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:25:58Z"
    - latency: 1.242471ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:24:58Z"
    - latency: 1.315853ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:23:58Z"
    - latency: 1.080157ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:22:58Z"
    - latency: 887.863µs
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:21:58Z"
    - latency: 1.365257ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 1.062013ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 991.346µs
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 1.190855ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 1.374263ms
      message: 'network-check-target-ip-10-0-142-151: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-network-check-target-ip-10-0-142-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "56548"
    uid: 1c52ca53-6071-46ff-adde-c701f147ef1f
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:57:58Z"
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.413608ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:25:58Z"
    - latency: 2.766507ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:24:58Z"
    - latency: 2.186726ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:23:58Z"
    - latency: 2.783238ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:22:58Z"
    - latency: 2.28769ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:21:58Z"
    - latency: 2.453664ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 2.50733ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 2.790332ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 2.357281ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 2.373932ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:50:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-151-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-151.ec2.internal
      uid: 6fda5fcd-2d9c-4411-8139-7c833f2fb002
    resourceVersion: "52078"
    uid: a7968fe3-c19d-48d4-a1c0-d57297909f23
  spec:
    sourcePod: network-check-source-869dcfcdcd-pr2fz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:56:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 983.599µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 1.831921ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:20:58Z"
    - latency: 1.296675ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 1.881586ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:19:58Z"
    - latency: 1.091414ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 1.771873ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:18:58Z"
    - latency: 1.123393ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 1.49593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:17:58Z"
    - latency: 933.417µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:58Z"
    - latency: 1.822888ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:16:58Z"
kind: List
metadata:
  resourceVersion: ""