apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "20621"
    uid: 1a6a0489-b141-4d45-864b-11fc40c678d3
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:53:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 964.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 1.107238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 1.112076ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:05:20Z"
    - latency: 1.026237ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:20Z"
    - latency: 1.011638ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:20Z"
    - latency: 1.098007ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:20Z"
    - latency: 876.833µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:20Z"
    - latency: 1.132863ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:20Z"
    - latency: 1.096074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:20Z"
    - latency: 1.175983ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "22273"
    uid: e98e0b51-4738-4233-b3e9-4b39a5bc9206
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:52:20Z"
      message: 'load-balancer-api-external: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.654189ms
      message: 'load-balancer-api-external: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:10:20Z"
    - latency: 12.253097ms
      message: 'load-balancer-api-external: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:10:20Z"
    - latency: 5.691672ms
      message: 'load-balancer-api-external: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:09:20Z"
    - latency: 8.131164ms
      message: 'load-balancer-api-external: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:09:20Z"
    - latency: 6.280694ms
      message: 'load-balancer-api-external: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:08:20Z"
    - latency: 8.214344ms
      message: 'load-balancer-api-external: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:08:20Z"
    - latency: 4.811444ms
      message: 'load-balancer-api-external: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 9.17553ms
      message: 'load-balancer-api-external: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 4.425589ms
      message: 'load-balancer-api-external: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 7.692668ms
      message: 'load-balancer-api-external: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:06:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "22274"
    uid: a8a472f0-c5f6-4f6e-9d05-d50e9db2e4d7
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:52:20Z"
      message: 'load-balancer-api-internal: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.912876ms
      message: 'load-balancer-api-internal: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:10:20Z"
    - latency: 12.286472ms
      message: 'load-balancer-api-internal: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:10:20Z"
    - latency: 5.937227ms
      message: 'load-balancer-api-internal: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:09:20Z"
    - latency: 8.161965ms
      message: 'load-balancer-api-internal: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:09:20Z"
    - latency: 4.106377ms
      message: 'load-balancer-api-internal: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:08:20Z"
    - latency: 8.265564ms
      message: 'load-balancer-api-internal: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:08:20Z"
    - latency: 3.885054ms
      message: 'load-balancer-api-internal: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 9.204777ms
      message: 'load-balancer-api-internal: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 4.324652ms
      message: 'load-balancer-api-internal: tcp connection to ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 7.724883ms
      message: 'load-balancer-api-internal: resolved host name ab106b1a2e6ed4adfa3ec4d55520735c-64b025abaab469c8.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:06:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-network-check-target-ip-10-0-132-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "20618"
    uid: f91d936a-3838-4e50-ab64-bc41c51f9861
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:53:20Z"
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.398736ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 800.755µs
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 839.162µs
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:05:20Z"
    - latency: 872.931µs
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:20Z"
    - latency: 831.103µs
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:20Z"
    - latency: 1.808219ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:20Z"
    - latency: 1.1366ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:20Z"
    - latency: 958.429µs
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:20Z"
    - latency: 1.205591ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:20Z"
    - latency: 1.443105ms
      message: 'network-check-target-ip-10-0-132-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-network-check-target-ip-10-0-137-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "20620"
    uid: e96bdee9-1d9c-4f0f-804f-df996cadc549
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:53:20Z"
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.830772ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 2.040212ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 2.066616ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:05:20Z"
    - latency: 1.813538ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:20Z"
    - latency: 1.942227ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:20Z"
    - latency: 2.211221ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:20Z"
    - latency: 1.942914ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:20Z"
    - latency: 2.259943ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:20Z"
    - latency: 2.160843ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:20Z"
    - latency: 1.604755ms
      message: 'network-check-target-ip-10-0-137-66: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-network-check-target-ip-10-0-143-239
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "20619"
    uid: f19c4be3-065b-4b61-ab35-4617c74143bd
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:53:20Z"
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.871005ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 2.251115ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 2.222427ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:05:20Z"
    - latency: 2.152993ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:20Z"
    - latency: 2.326068ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:20Z"
    - latency: 2.307405ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:20Z"
    - latency: 2.0873ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:20Z"
    - latency: 2.440359ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:20Z"
    - latency: 2.177355ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:20Z"
    - latency: 2.198821ms
      message: 'network-check-target-ip-10-0-143-239: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:46:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-137.ec2.internal
      uid: 01d57809-3518-4496-9d86-3e7d1ab604cc
    resourceVersion: "22272"
    uid: 9aeb87cb-7d22-48d3-a6e2-85b3eebef9de
  spec:
    sourcePod: network-check-source-685456655f-rq4hm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:52:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 900.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:10:20Z"
    - latency: 1.842521ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:10:20Z"
    - latency: 903.173µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:09:20Z"
    - latency: 2.198966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:09:20Z"
    - latency: 965.352µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:08:20Z"
    - latency: 1.732216ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:08:20Z"
    - latency: 982.614µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 2.932044ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:07:20Z"
    - latency: 975.487µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:06:20Z"
    - latency: 1.856622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:06:20Z"
kind: List
metadata:
  resourceVersion: ""