apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "69820"
    uid: d96c620b-deda-4432-90f7-7f049f5ff087
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:18:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 735.644µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:00:37Z"
    - latency: 1.14035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:59:37Z"
    - latency: 1.195873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:58:37Z"
    - latency: 1.386898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:37Z"
    - latency: 1.510363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:37Z"
    - latency: 1.108159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:37Z"
    - latency: 1.265267ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:37Z"
    - latency: 1.140551ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:37Z"
    - latency: 1.3017ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:37Z"
    - latency: 897.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "74924"
    uid: 7f2e95d5-4e85-4861-a285-025e4f7ed356
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:17:37Z"
      message: 'load-balancer-api-external: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.063103ms
      message: 'load-balancer-api-external: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:05:37Z"
    - latency: 7.29769ms
      message: 'load-balancer-api-external: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:05:37Z"
    - latency: 4.150347ms
      message: 'load-balancer-api-external: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:04:37Z"
    - latency: 6.97056ms
      message: 'load-balancer-api-external: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:04:37Z"
    - latency: 3.215291ms
      message: 'load-balancer-api-external: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:03:37Z"
    - latency: 7.790346ms
      message: 'load-balancer-api-external: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:03:37Z"
    - latency: 5.059657ms
      message: 'load-balancer-api-external: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:02:37Z"
    - latency: 6.598146ms
      message: 'load-balancer-api-external: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:02:37Z"
    - latency: 4.589108ms
      message: 'load-balancer-api-external: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:01:37Z"
    - latency: 9.586184ms
      message: 'load-balancer-api-external: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:01:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "74925"
    uid: 4ccffd8d-7c54-42d5-a03e-46a4f7b7eb96
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:17:37Z"
      message: 'load-balancer-api-internal: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.96514ms
      message: 'load-balancer-api-internal: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:05:37Z"
    - latency: 7.215086ms
      message: 'load-balancer-api-internal: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:05:37Z"
    - latency: 4.116335ms
      message: 'load-balancer-api-internal: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:04:37Z"
    - latency: 6.991937ms
      message: 'load-balancer-api-internal: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:04:37Z"
    - latency: 4.965357ms
      message: 'load-balancer-api-internal: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:03:37Z"
    - latency: 7.767491ms
      message: 'load-balancer-api-internal: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:03:37Z"
    - latency: 5.436918ms
      message: 'load-balancer-api-internal: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:02:37Z"
    - latency: 6.656438ms
      message: 'load-balancer-api-internal: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:02:37Z"
    - latency: 5.384201ms
      message: 'load-balancer-api-internal: tcp connection to a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:01:37Z"
    - latency: 9.616877ms
      message: 'load-balancer-api-internal: resolved host name a233af821cd424527a5b0fb8d812459f-40f97a2e2893089f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:01:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-ip-10-0-133-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "69818"
    uid: 54fe223a-fa5c-402b-ae8a-d0de3b1b8e5d
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:18:37Z"
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.613442ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:00:37Z"
    - latency: 2.099412ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:59:37Z"
    - latency: 2.218147ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:58:37Z"
    - latency: 2.088595ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:37Z"
    - latency: 2.550574ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:37Z"
    - latency: 1.839757ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:37Z"
    - latency: 1.837441ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:37Z"
    - latency: 2.389671ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:37Z"
    - latency: 2.183252ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:37Z"
    - latency: 2.010014ms
      message: 'network-check-target-ip-10-0-133-72: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-ip-10-0-136-137
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "69817"
    uid: 795f821a-865e-4165-9a69-bca011a8f04e
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:18:37Z"
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.265525ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:00:37Z"
    - latency: 967.225µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:59:37Z"
    - latency: 1.309021ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:58:37Z"
    - latency: 1.311315ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:37Z"
    - latency: 1.792992ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:37Z"
    - latency: 855.962µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:37Z"
    - latency: 956.848µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:37Z"
    - latency: 977.149µs
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:37Z"
    - latency: 1.043445ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:37Z"
    - latency: 1.117003ms
      message: 'network-check-target-ip-10-0-136-137: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-ip-10-0-140-243
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "69819"
    uid: a4dc3919-545d-4890-8f9c-17d62c5752c2
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:18:37Z"
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.121744ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:00:37Z"
    - latency: 2.317452ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:59:37Z"
    - latency: 2.599135ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:58:37Z"
    - latency: 2.453357ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:57:37Z"
    - latency: 2.31179ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:56:37Z"
    - latency: 2.017249ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:55:37Z"
    - latency: 2.350857ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:54:37Z"
    - latency: 2.17742ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:53:37Z"
    - latency: 1.994688ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:52:37Z"
    - latency: 2.271762ms
      message: 'network-check-target-ip-10-0-140-243: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T20:51:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T20:11:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-137-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-137.ec2.internal
      uid: d635f2e3-9e9d-4e77-914d-a602504fadeb
    resourceVersion: "74923"
    uid: 094d5baa-c00a-4b7b-bc1c-9011f005c064
  spec:
    sourcePod: network-check-source-7d88cb55d8-p9npb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T20:17:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.977µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:05:37Z"
    - latency: 1.848282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:05:37Z"
    - latency: 1.174289ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:04:37Z"
    - latency: 1.729257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:04:37Z"
    - latency: 913.319µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:03:37Z"
    - latency: 2.375945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:03:37Z"
    - latency: 945.504µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:02:37Z"
    - latency: 2.03912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:02:37Z"
    - latency: 1.150921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T21:01:37Z"
    - latency: 1.841887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T21:01:37Z"
kind: List
metadata:
  resourceVersion: ""