apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "82697"
    uid: ae6c97b8-dd08-4ead-a92e-674dca943076
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:47:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.29231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:43:41Z"
    - latency: 1.49245ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:42:41Z"
    - latency: 878.494µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:41:41Z"
    - latency: 979.48µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 1.123066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 929.011µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 1.038797ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 1.119387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 1.142623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:35:41Z"
    - latency: 1.02197ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "79409"
    uid: 198c1926-f9da-4475-b87d-c5684a622462
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:46:41Z"
      message: 'load-balancer-api-external: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.340859ms
      message: 'load-balancer-api-external: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 13.19685ms
      message: 'load-balancer-api-external: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 3.547437ms
      message: 'load-balancer-api-external: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 7.092062ms
      message: 'load-balancer-api-external: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 4.725176ms
      message: 'load-balancer-api-external: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 7.326657ms
      message: 'load-balancer-api-external: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 4.52266ms
      message: 'load-balancer-api-external: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 7.557899ms
      message: 'load-balancer-api-external: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 4.009598ms
      message: 'load-balancer-api-external: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 7.189664ms
      message: 'load-balancer-api-external: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:36:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "79408"
    uid: 356dbcee-fb0e-45dc-bfb0-265f3a421f77
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:46:41Z"
      message: 'load-balancer-api-internal: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.385394ms
      message: 'load-balancer-api-internal: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 13.141128ms
      message: 'load-balancer-api-internal: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 3.573527ms
      message: 'load-balancer-api-internal: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 7.175567ms
      message: 'load-balancer-api-internal: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 4.705123ms
      message: 'load-balancer-api-internal: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 7.232656ms
      message: 'load-balancer-api-internal: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 8.61232ms
      message: 'load-balancer-api-internal: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 7.584534ms
      message: 'load-balancer-api-internal: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 4.217967ms
      message: 'load-balancer-api-internal: tcp connection to a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 7.107563ms
      message: 'load-balancer-api-internal: resolved host name a844c27658fee453eba0058238481a7d-74d058c433dcda42.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:36:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-network-check-target-ip-10-0-132-133
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "82695"
    uid: cd6eeccf-dd20-4a1b-9b76-d296233bfef5
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:47:41Z"
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.335048ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:43:41Z"
    - latency: 2.747451ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:42:41Z"
    - latency: 1.993608ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:41:41Z"
    - latency: 2.559555ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 2.354319ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 2.243052ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 2.376532ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 2.453346ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 2.889657ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:35:41Z"
    - latency: 2.496652ms
      message: 'network-check-target-ip-10-0-132-133: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-network-check-target-ip-10-0-132-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "82696"
    uid: 623c0e05-2a16-448f-9c7c-6fcedf89db33
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:47:41Z"
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.388246ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:43:41Z"
    - latency: 2.577192ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:42:41Z"
    - latency: 2.213559ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:41:41Z"
    - latency: 2.243787ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 2.365878ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 2.563864ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 2.875465ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 2.234701ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 2.308262ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:35:41Z"
    - latency: 2.479204ms
      message: 'network-check-target-ip-10-0-132-59: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-network-check-target-ip-10-0-135-111
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "82694"
    uid: f6ad8a09-79b9-4d2d-b37c-35b66abf28cc
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:47:41Z"
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.708µs
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:43:41Z"
    - latency: 1.878585ms
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:42:41Z"
    - latency: 1.384202ms
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:41:41Z"
    - latency: 1.725968ms
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 1.062923ms
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 1.598093ms
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 949.481µs
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 951.967µs
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 966.147µs
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:35:41Z"
    - latency: 997.953µs
      message: 'network-check-target-ip-10-0-135-111: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:34:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T16:40:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-111-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-111.ec2.internal
      uid: f17994b3-9fb2-4c23-8b50-9c404d7052cf
    resourceVersion: "79407"
    uid: f8ee1667-8bf3-498a-9020-e76fecac9798
  spec:
    sourcePod: network-check-source-7d88cb55d8-vds59
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T16:46:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 779.73µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 1.91579ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:40:41Z"
    - latency: 906.799µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 1.727107ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:39:41Z"
    - latency: 890.513µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 2.29665ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:38:41Z"
    - latency: 1.013044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 2.044078ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:37:41Z"
    - latency: 1.286723ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T17:36:41Z"
    - latency: 2.189006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T17:36:41Z"
kind: List
metadata:
  resourceVersion: ""