apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "59254"
    uid: 5ab11925-ede3-4400-9f6d-b7c40b68a2db
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.031754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:29Z"
    - latency: 950.758µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 1.711169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 910.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 1.085653ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.310479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 1.426051ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 1.273101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 1.050809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 1.092009ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "55457"
    uid: 5466b711-e28b-4217-856d-17e253a40bda
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:44:29Z"
      message: 'load-balancer-api-external: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.59186ms
      message: 'load-balancer-api-external: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 7.257015ms
      message: 'load-balancer-api-external: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 56.861225ms
      message: 'load-balancer-api-external: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 8.058642ms
      message: 'load-balancer-api-external: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 54.973506ms
      message: 'load-balancer-api-external: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 7.242252ms
      message: 'load-balancer-api-external: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 54.834403ms
      message: 'load-balancer-api-external: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 7.595504ms
      message: 'load-balancer-api-external: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 55.071413ms
      message: 'load-balancer-api-external: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 8.388069ms
      message: 'load-balancer-api-external: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:40:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "55458"
    uid: c7bbb2e7-a65c-4416-8da6-819b86a94d55
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:44:29Z"
      message: 'load-balancer-api-internal: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.600172ms
      message: 'load-balancer-api-internal: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 7.218194ms
      message: 'load-balancer-api-internal: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 56.870364ms
      message: 'load-balancer-api-internal: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 7.989616ms
      message: 'load-balancer-api-internal: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 57.448334ms
      message: 'load-balancer-api-internal: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 7.174271ms
      message: 'load-balancer-api-internal: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 55.271002ms
      message: 'load-balancer-api-internal: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 7.547904ms
      message: 'load-balancer-api-internal: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 55.129387ms
      message: 'load-balancer-api-internal: tcp connection to a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 8.335679ms
      message: 'load-balancer-api-internal: resolved host name a41523619245140049339d55e6c91ffd-78a63a0feb3ef4fb.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:40:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-ip-10-0-141-115
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "59250"
    uid: 95ddc81c-702b-465f-a99c-fcfdc300848f
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:29Z"
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 854.783µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:29Z"
    - latency: 973.699µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 1.290295ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 1.060531ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 764.048µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.831196ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 1.271005ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 1.496183ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 1.336474ms
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 874.47µs
      message: 'network-check-target-ip-10-0-141-115: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-ip-10-0-141-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "59251"
    uid: 5b258346-8ece-42ae-9866-b9a6b5a3c35f
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:29Z"
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.933127ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:29Z"
    - latency: 1.92043ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 1.516164ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 1.854458ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 1.869504ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.663111ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 2.121113ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 2.169444ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 2.090393ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 1.961724ms
      message: 'network-check-target-ip-10-0-141-37: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-ip-10-0-142-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "59252"
    uid: 528bea5a-08b1-4716-8651-5befd91b743b
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:45:29Z"
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.221844ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:48:29Z"
    - latency: 1.949544ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 2.451083ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 2.205675ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 2.19719ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.963412ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 2.131228ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 2.216482ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 2.321239ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 2.270366ms
      message: 'network-check-target-ip-10-0-142-4: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:38:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-115-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-115.us-west-1.compute.internal
      uid: 0c4d0e76-d2a3-40f1-b9de-fc5b1c0abd33
    resourceVersion: "55451"
    uid: d72acd02-a019-4a30-9280-34588b44f9ae
  spec:
    sourcePod: network-check-source-6f78d59f99-v2p5n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:44:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 784.852µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.700667ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 805.075µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 2.459864ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 857.789µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 1.880807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 954.428µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 1.666072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 909.801µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 2.03293ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:40:29Z"
kind: List
metadata:
  resourceVersion: ""