apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "54101"
    uid: b28dcf94-3bbe-419b-b808-650c20b9bef0
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:58:24Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 924.553µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 1.277263ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 967.331µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:16:24Z"
    - latency: 1.007908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:15:24Z"
    - latency: 1.364631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:14:24Z"
    - latency: 1.216396ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:13:24Z"
    - latency: 1.145728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:12:24Z"
    - latency: 1.005284ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:11:24Z"
    - latency: 1.326007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:10:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "55836"
    uid: ae1261f8-588f-49be-9f7e-df54119508f3
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:57:24Z"
      message: 'load-balancer-api-external: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.924238ms
      message: 'load-balancer-api-external: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:21:24Z"
    - latency: 8.537757ms
      message: 'load-balancer-api-external: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:21:24Z"
    - latency: 3.990422ms
      message: 'load-balancer-api-external: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:20:24Z"
    - latency: 10.214317ms
      message: 'load-balancer-api-external: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:20:24Z"
    - latency: 4.06549ms
      message: 'load-balancer-api-external: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 12.7863ms
      message: 'load-balancer-api-external: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 3.728756ms
      message: 'load-balancer-api-external: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 7.695121ms
      message: 'load-balancer-api-external: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 4.77033ms
      message: 'load-balancer-api-external: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 11.174349ms
      message: 'load-balancer-api-external: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:17:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "55837"
    uid: 64ca1373-4bf0-48b4-a4f7-f56803cbe6fe
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:57:24Z"
      message: 'load-balancer-api-internal: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.194315ms
      message: 'load-balancer-api-internal: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:21:24Z"
    - latency: 8.725885ms
      message: 'load-balancer-api-internal: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:21:24Z"
    - latency: 5.252244ms
      message: 'load-balancer-api-internal: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:20:24Z"
    - latency: 10.27013ms
      message: 'load-balancer-api-internal: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:20:24Z"
    - latency: 5.540155ms
      message: 'load-balancer-api-internal: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 12.727872ms
      message: 'load-balancer-api-internal: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 4.425809ms
      message: 'load-balancer-api-internal: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 7.770276ms
      message: 'load-balancer-api-internal: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 4.782827ms
      message: 'load-balancer-api-internal: tcp connection to a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 11.139716ms
      message: 'load-balancer-api-internal: resolved host name a9b0d796dedcd40fb8fb3a080c442940-0ece592bd5ab3fea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:17:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-network-check-target-ip-10-0-133-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "54099"
    uid: 895cd699-fafd-4866-a978-ee383b29d5d2
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:58:24Z"
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.178279ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 2.479998ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 2.381664ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 2.355894ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:16:24Z"
    - latency: 2.409703ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:15:24Z"
    - latency: 2.192619ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:14:24Z"
    - latency: 2.659651ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:13:24Z"
    - latency: 2.814331ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:12:24Z"
    - latency: 2.430356ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:11:24Z"
    - latency: 1.777687ms
      message: 'network-check-target-ip-10-0-133-14: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:10:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-network-check-target-ip-10-0-140-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "54100"
    uid: 850d9a09-a72d-46e5-9aae-6b2763bfabc0
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:58:24Z"
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.130835ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 2.016784ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 2.36223ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 2.408767ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:16:24Z"
    - latency: 2.479848ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:15:24Z"
    - latency: 2.452645ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:14:24Z"
    - latency: 3.02716ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:13:24Z"
    - latency: 2.606022ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:12:24Z"
    - latency: 2.51031ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:11:24Z"
    - latency: 2.214959ms
      message: 'network-check-target-ip-10-0-140-64: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:10:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-network-check-target-ip-10-0-143-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "54098"
    uid: d449fc8a-0999-417b-9a06-a917c720584f
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:58:24Z"
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.038928ms
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 976.329µs
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 921.913µs
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 1.040857ms
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:16:24Z"
    - latency: 1.1303ms
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:15:24Z"
    - latency: 955.444µs
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:14:24Z"
    - latency: 905.75µs
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:13:24Z"
    - latency: 1.079682ms
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:12:24Z"
    - latency: 1.159054ms
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:11:24Z"
    - latency: 1.531141ms
      message: 'network-check-target-ip-10-0-143-184: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:10:24Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T07:51:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-184-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-184.ec2.internal
      uid: d246238f-6f56-4dad-b46b-cae7f2981d62
    resourceVersion: "55834"
    uid: 5822564e-8432-47f6-bb17-262c8b0ee4d1
  spec:
    sourcePod: network-check-source-685456655f-8z556
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T07:57:24Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.097479ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:21:24Z"
    - latency: 1.690391ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:21:24Z"
    - latency: 905.571µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:20:24Z"
    - latency: 1.842912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:20:24Z"
    - latency: 757.285µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 2.04565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:19:24Z"
    - latency: 863.976µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 2.030767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:18:24Z"
    - latency: 825.669µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T08:17:24Z"
    - latency: 1.809449ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T08:17:24Z"
kind: List
metadata:
  resourceVersion: ""