apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "53189"
    uid: bf3cbb58-7341-4f65-8b42-6794882b5c49
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:20:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.043641ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 1.456273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 1.623525ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 1.066242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:36Z"
    - latency: 1.227088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:37:36Z"
    - latency: 1.195785ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:36:36Z"
    - latency: 1.175224ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:35:36Z"
    - latency: 1.006151ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:34:36Z"
    - latency: 1.307024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:33:36Z"
    - latency: 1.285903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:32:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "54880"
    uid: 558d860e-79d0-438b-92f8-c076ef1f50b7
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:19:36Z"
      message: 'load-balancer-api-external: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810285ms
      message: 'load-balancer-api-external: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:36Z"
    - latency: 8.464185ms
      message: 'load-balancer-api-external: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:43:36Z"
    - latency: 4.132819ms
      message: 'load-balancer-api-external: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:36Z"
    - latency: 8.962227ms
      message: 'load-balancer-api-external: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:42:36Z"
    - latency: 3.67403ms
      message: 'load-balancer-api-external: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 9.663972ms
      message: 'load-balancer-api-external: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 5.454472ms
      message: 'load-balancer-api-external: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 9.580146ms
      message: 'load-balancer-api-external: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 4.526218ms
      message: 'load-balancer-api-external: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 9.269432ms
      message: 'load-balancer-api-external: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:39:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "54879"
    uid: 673ccf4f-57bf-473f-8cbe-b08cb5be4e03
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:19:36Z"
      message: 'load-balancer-api-internal: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.475961ms
      message: 'load-balancer-api-internal: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:36Z"
    - latency: 8.487337ms
      message: 'load-balancer-api-internal: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:43:36Z"
    - latency: 4.164469ms
      message: 'load-balancer-api-internal: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:36Z"
    - latency: 8.879766ms
      message: 'load-balancer-api-internal: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:42:36Z"
    - latency: 3.668671ms
      message: 'load-balancer-api-internal: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 9.552426ms
      message: 'load-balancer-api-internal: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 6.047443ms
      message: 'load-balancer-api-internal: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 9.525088ms
      message: 'load-balancer-api-internal: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 4.933446ms
      message: 'load-balancer-api-internal: tcp connection to ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 9.322336ms
      message: 'load-balancer-api-internal: resolved host name ae2e5af696b0c47eab8b450cd8407cad-30f6892c4dec71a9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:39:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-network-check-target-ip-10-0-132-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "53187"
    uid: 710a5fa0-881b-4291-93a4-bcb3b5b8d15f
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:20:36Z"
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.623946ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 2.259815ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 3.059609ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 2.660953ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:36Z"
    - latency: 2.75721ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:37:36Z"
    - latency: 2.318993ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:36:36Z"
    - latency: 2.361747ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:35:36Z"
    - latency: 2.718922ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:34:36Z"
    - latency: 2.247025ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:33:36Z"
    - latency: 2.608739ms
      message: 'network-check-target-ip-10-0-132-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:32:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-network-check-target-ip-10-0-141-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "53188"
    uid: 8ded0dd5-bf67-44fd-aae2-fa3f85190fd3
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:20:36Z"
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.59357ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 2.732057ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 2.462965ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 2.606559ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:36Z"
    - latency: 2.652902ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:37:36Z"
    - latency: 2.436088ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:36:36Z"
    - latency: 2.310947ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:35:36Z"
    - latency: 2.631586ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:34:36Z"
    - latency: 2.624701ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:33:36Z"
    - latency: 2.707613ms
      message: 'network-check-target-ip-10-0-141-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:32:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-network-check-target-ip-10-0-143-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "53186"
    uid: fcf532d6-dfbe-4fa7-b208-53ab206f50e3
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:20:36Z"
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.182635ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 1.449538ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 1.701082ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 1.160248ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:38:36Z"
    - latency: 1.053455ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:37:36Z"
    - latency: 1.243747ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:36:36Z"
    - latency: 989.687µs
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:35:36Z"
    - latency: 967.101µs
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:34:36Z"
    - latency: 1.576182ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:33:36Z"
    - latency: 1.586607ms
      message: 'network-check-target-ip-10-0-143-43: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:32:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T19:13:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-43.ec2.internal
      uid: 8ec0c8e5-4f0f-4607-924c-e764b1722b47
    resourceVersion: "54878"
    uid: 388b9948-ed0e-40fe-bb1b-5f0d398270b0
  spec:
    sourcePod: network-check-source-685456655f-twfjs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T19:19:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 904.566µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:43:36Z"
    - latency: 1.949415ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:43:36Z"
    - latency: 951.675µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:42:36Z"
    - latency: 1.809252ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:42:36Z"
    - latency: 1.108916ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 2.071783ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:41:36Z"
    - latency: 1.175207ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 2.106706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:40:36Z"
    - latency: 1.246951ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T19:39:36Z"
    - latency: 2.14819ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T19:39:36Z"
kind: List
metadata:
  resourceVersion: ""