apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "55265"
    uid: 05542c6a-8129-420d-ba54-350b83247644
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:51:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.274021ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 1.015227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 1.168878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 910.511µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 1.256762ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:15:20Z"
    - latency: 1.044375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:14:20Z"
    - latency: 1.301511ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:13:20Z"
    - latency: 1.371469ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:12:20Z"
    - latency: 920.626µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:11:20Z"
    - latency: 1.406111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:10:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "56226"
    uid: 9b3e51d8-829b-4a43-8a4b-895f835ce016
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:50:20Z"
      message: 'load-balancer-api-external: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.397611ms
      message: 'load-balancer-api-external: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:20Z"
    - latency: 7.746569ms
      message: 'load-balancer-api-external: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:20:20Z"
    - latency: 5.93562ms
      message: 'load-balancer-api-external: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 6.768017ms
      message: 'load-balancer-api-external: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 4.28501ms
      message: 'load-balancer-api-external: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 7.084357ms
      message: 'load-balancer-api-external: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 5.042171ms
      message: 'load-balancer-api-external: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 7.110273ms
      message: 'load-balancer-api-external: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 4.076526ms
      message: 'load-balancer-api-external: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 7.305977ms
      message: 'load-balancer-api-external: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "56224"
    uid: 2d125e53-939c-4a3a-90da-4ebe3a92da5f
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:50:20Z"
      message: 'load-balancer-api-internal: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.194951ms
      message: 'load-balancer-api-internal: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:20Z"
    - latency: 7.774656ms
      message: 'load-balancer-api-internal: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:20:20Z"
    - latency: 5.919748ms
      message: 'load-balancer-api-internal: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 6.858686ms
      message: 'load-balancer-api-internal: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 4.319159ms
      message: 'load-balancer-api-internal: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 7.119772ms
      message: 'load-balancer-api-internal: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 5.305555ms
      message: 'load-balancer-api-internal: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 7.138987ms
      message: 'load-balancer-api-internal: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 5.13734ms
      message: 'load-balancer-api-internal: tcp connection to a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 7.331563ms
      message: 'load-balancer-api-internal: resolved host name a56c9879814ff43bdb821fe8fa0d950f-04e857d0a96a6d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-network-check-target-ip-10-0-141-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "55263"
    uid: 135281de-f255-4782-8c23-f0ceafb12643
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:51:20Z"
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.402728ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 2.676614ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 2.339183ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 2.370416ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 2.947947ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:15:20Z"
    - latency: 2.495276ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:14:20Z"
    - latency: 1.884822ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:13:20Z"
    - latency: 2.597549ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:12:20Z"
    - latency: 2.049022ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:11:20Z"
    - latency: 2.267414ms
      message: 'network-check-target-ip-10-0-141-73: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:10:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-network-check-target-ip-10-0-143-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "55262"
    uid: 5c131818-d379-4f5d-aeda-fb53f66c7dca
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:51:20Z"
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 991.944µs
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 1.139288ms
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 951.19µs
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 775.07µs
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 1.077422ms
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:15:20Z"
    - latency: 1.257194ms
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:14:20Z"
    - latency: 941.729µs
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:13:20Z"
    - latency: 1.197781ms
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:12:20Z"
    - latency: 1.198093ms
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:11:20Z"
    - latency: 1.593403ms
      message: 'network-check-target-ip-10-0-143-200: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:10:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-network-check-target-ip-10-0-143-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "55264"
    uid: a46b8926-ee73-4df2-88a6-2fecd4c26896
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:51:20Z"
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.046657ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 2.316295ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 2.163266ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 2.249403ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 2.306835ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:15:20Z"
    - latency: 2.452624ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:14:20Z"
    - latency: 2.204607ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:13:20Z"
    - latency: 2.420929ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:12:20Z"
    - latency: 2.188198ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:11:20Z"
    - latency: 2.36147ms
      message: 'network-check-target-ip-10-0-143-65: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:10:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T00:44:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-200.ec2.internal
      uid: 59e71546-ab61-4edb-9738-f43fde9c1b4f
    resourceVersion: "56221"
    uid: c940923f-92b4-4576-96a7-d85137e31bbd
  spec:
    sourcePod: network-check-source-869dcfcdcd-r6wkz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T00:50:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.467µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:20:20Z"
    - latency: 2.002903ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:20:20Z"
    - latency: 798.879µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 1.789371ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:19:20Z"
    - latency: 905.026µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 1.951801ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:18:20Z"
    - latency: 821.506µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 2.214198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:17:20Z"
    - latency: 1.040151ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T01:16:20Z"
    - latency: 1.632726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T01:16:20Z"
kind: List
metadata:
  resourceVersion: ""