apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "52942"
    uid: a3dbfa51-2697-4c7a-bf84-739b4e713918
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:26:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.071545ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 1.11725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 1.235026ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 1.223713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:44:48Z"
    - latency: 1.429741ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:43:48Z"
    - latency: 1.059874ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:42:48Z"
    - latency: 1.048401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:41:48Z"
    - latency: 1.086614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:40:48Z"
    - latency: 1.079257ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:39:48Z"
    - latency: 922.773µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "54180"
    uid: aad32600-66d7-4710-9e7d-5792f345dd33
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:25:48Z"
      message: 'load-balancer-api-external: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.059066ms
      message: 'load-balancer-api-external: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:49:48Z"
    - latency: 6.306561ms
      message: 'load-balancer-api-external: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:49:48Z"
    - latency: 8.528704ms
      message: 'load-balancer-api-external: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:48:48Z"
    - latency: 6.983404ms
      message: 'load-balancer-api-external: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:48:48Z"
    - latency: 4.38107ms
      message: 'load-balancer-api-external: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 7.137886ms
      message: 'load-balancer-api-external: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 7.358618ms
      message: 'load-balancer-api-external: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 6.851844ms
      message: 'load-balancer-api-external: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 6.24454ms
      message: 'load-balancer-api-external: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 7.173905ms
      message: 'load-balancer-api-external: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:45:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "54179"
    uid: bcc394eb-82e8-4ce0-a243-3d502f044880
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:25:48Z"
      message: 'load-balancer-api-internal: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.04812ms
      message: 'load-balancer-api-internal: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:49:48Z"
    - latency: 6.339684ms
      message: 'load-balancer-api-internal: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:49:48Z"
    - latency: 7.026804ms
      message: 'load-balancer-api-internal: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:48:48Z"
    - latency: 7.151095ms
      message: 'load-balancer-api-internal: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:48:48Z"
    - latency: 4.351253ms
      message: 'load-balancer-api-internal: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 7.076717ms
      message: 'load-balancer-api-internal: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 7.353973ms
      message: 'load-balancer-api-internal: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 6.957568ms
      message: 'load-balancer-api-internal: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 4.973848ms
      message: 'load-balancer-api-internal: tcp connection to a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 7.130253ms
      message: 'load-balancer-api-internal: resolved host name a75f141b2f27e4f3f980fa6204891153-e1e569fb23f34ba2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:45:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-network-check-target-ip-10-0-131-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "52940"
    uid: 0be03b82-3a86-4aee-87e1-ed086963a2ad
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:26:48Z"
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.384817ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 2.651226ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 2.46885ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 2.370076ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:44:48Z"
    - latency: 3.277496ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:43:48Z"
    - latency: 2.451927ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:42:48Z"
    - latency: 3.204053ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:41:48Z"
    - latency: 2.582444ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:40:48Z"
    - latency: 2.734204ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:39:48Z"
    - latency: 2.123064ms
      message: 'network-check-target-ip-10-0-131-57: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-network-check-target-ip-10-0-135-150
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "52941"
    uid: 7a277a2d-95d9-45f9-b0d1-d8768ece8a55
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:26:48Z"
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.367615ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 2.140615ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 2.463961ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 2.490171ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:44:48Z"
    - latency: 2.209802ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:43:48Z"
    - latency: 2.339874ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:42:48Z"
    - latency: 2.386059ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:41:48Z"
    - latency: 2.30077ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:40:48Z"
    - latency: 2.464896ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:39:48Z"
    - latency: 2.621617ms
      message: 'network-check-target-ip-10-0-135-150: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-network-check-target-ip-10-0-141-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "52939"
    uid: d7c00ff2-8b51-4eb8-ad3a-bec15a17019f
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:26:48Z"
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.60005ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 1.253263ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 1.034551ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 1.078792ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:44:48Z"
    - latency: 1.749905ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:43:48Z"
    - latency: 965.099µs
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:42:48Z"
    - latency: 1.37528ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:41:48Z"
    - latency: 1.200275ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:40:48Z"
    - latency: 972.983µs
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:39:48Z"
    - latency: 1.424203ms
      message: 'network-check-target-ip-10-0-141-198: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:38:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T14:19:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-198-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-198.ec2.internal
      uid: 8447bb82-4f7a-48f2-8d67-903099f842b1
    resourceVersion: "54178"
    uid: 4a4d39e2-d8ef-48d5-9c15-888f6cf341f0
  spec:
    sourcePod: network-check-source-6f8b768455-xqj8m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T14:25:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.651µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:49:48Z"
    - latency: 1.815006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:49:48Z"
    - latency: 830.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:48:48Z"
    - latency: 1.7217ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:48:48Z"
    - latency: 1.083269ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 1.939298ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:47:48Z"
    - latency: 1.089922ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 1.981343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:46:48Z"
    - latency: 1.280278ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T14:45:48Z"
    - latency: 1.912701ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T14:45:48Z"
kind: List
metadata:
  resourceVersion: ""