apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "71779"
    uid: 89e0062f-4d9e-4139-85b8-05d19a654a26
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:01:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.087128ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:43:02Z"
    - latency: 918.377µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 1.217455ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 1.01966ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 1.543274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 1.271229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 1.020724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:37:02Z"
    - latency: 1.059928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:36:02Z"
    - latency: 1.029229ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:35:02Z"
    - latency: 1.612889ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "70009"
    uid: dd7aa559-f823-4807-b12a-83e6378a9c0e
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:00:02Z"
      message: 'load-balancer-api-external: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.770069ms
      message: 'load-balancer-api-external: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 9.799189ms
      message: 'load-balancer-api-external: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 5.553535ms
      message: 'load-balancer-api-external: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 9.343861ms
      message: 'load-balancer-api-external: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 4.566806ms
      message: 'load-balancer-api-external: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 13.749453ms
      message: 'load-balancer-api-external: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 5.122662ms
      message: 'load-balancer-api-external: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 9.422614ms
      message: 'load-balancer-api-external: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 5.300911ms
      message: 'load-balancer-api-external: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 8.987227ms
      message: 'load-balancer-api-external: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:38:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "70010"
    uid: 1b37cff7-e883-4771-bc2b-89aa49f193e9
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:00:02Z"
      message: 'load-balancer-api-internal: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.973634ms
      message: 'load-balancer-api-internal: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 9.769804ms
      message: 'load-balancer-api-internal: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 4.595346ms
      message: 'load-balancer-api-internal: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 9.274266ms
      message: 'load-balancer-api-internal: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 4.547004ms
      message: 'load-balancer-api-internal: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 13.812031ms
      message: 'load-balancer-api-internal: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 5.116292ms
      message: 'load-balancer-api-internal: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 9.475692ms
      message: 'load-balancer-api-internal: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 3.930603ms
      message: 'load-balancer-api-internal: tcp connection to a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 9.040771ms
      message: 'load-balancer-api-internal: resolved host name a9d4f830b6a5f47dfa9825a9c71c6d7c-5afb9b2ff4c5ae85.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:38:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-network-check-target-ip-10-0-135-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "71777"
    uid: 66532e6a-687d-4e44-b2be-e77de67046ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:01:02Z"
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.156497ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:43:02Z"
    - latency: 891.817µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 1.319657ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 959.39µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 952.051µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 1.352309ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 890.397µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:37:02Z"
    - latency: 995.668µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:36:02Z"
    - latency: 968.186µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:35:02Z"
    - latency: 918.153µs
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-network-check-target-ip-10-0-136-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "71776"
    uid: a2f2482b-893d-494c-ba5a-b61f98252749
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:01:02Z"
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.49593ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:43:02Z"
    - latency: 2.191842ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 2.06791ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 2.213939ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 1.912018ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 2.257445ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 2.537068ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:37:02Z"
    - latency: 2.164346ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:36:02Z"
    - latency: 2.066174ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:35:02Z"
    - latency: 2.574067ms
      message: 'network-check-target-ip-10-0-136-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-network-check-target-ip-10-0-137-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "71778"
    uid: ff1cf343-9d8c-4e5f-883a-de961092ac14
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:01:02Z"
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.016024ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:43:02Z"
    - latency: 2.521056ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 2.489119ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 2.509662ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 2.634873ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 2.668535ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 2.306877ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:37:02Z"
    - latency: 2.501614ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:36:02Z"
    - latency: 2.639602ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:35:02Z"
    - latency: 2.503055ms
      message: 'network-check-target-ip-10-0-137-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:34:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-29T20:54:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-229-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-229.ec2.internal
      uid: a4ef2cf4-cc45-47c9-817f-f430000728d4
    resourceVersion: "70006"
    uid: 783a7db1-6486-4407-a000-b52c6de2eff2
  spec:
    sourcePod: network-check-source-7d88cb55d8-p7gcw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-29T21:00:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.355684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 1.817156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:42:02Z"
    - latency: 1.007465ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 1.911548ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:41:02Z"
    - latency: 902.33µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 1.985205ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:40:02Z"
    - latency: 1.092008ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 2.201454ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:39:02Z"
    - latency: 1.451274ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-29T21:38:02Z"
    - latency: 1.969395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-29T21:38:02Z"
kind: List
metadata:
  resourceVersion: ""