apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "17697"
    uid: 27b00ea7-3b4e-4160-852d-175bc75b8a4b
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:54:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.194649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 1.005365ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:07Z"
    - latency: 756.387µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:07Z"
    - latency: 905.745µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:07Z"
    - latency: 953.75µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:07Z"
    - latency: 859.244µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:07Z"
    - latency: 1.003355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:07Z"
    - latency: 1.022982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:07Z"
    - latency: 940.145µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:07Z"
    - latency: 961.689µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "19868"
    uid: 752bd190-ff87-429d-babf-70dd769dcb98
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:53:07Z"
      message: 'load-balancer-api-external: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.007399ms
      message: 'load-balancer-api-external: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:07Z"
    - latency: 7.704273ms
      message: 'load-balancer-api-external: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:05:07Z"
    - latency: 4.512043ms
      message: 'load-balancer-api-external: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:07Z"
    - latency: 7.811946ms
      message: 'load-balancer-api-external: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:04:07Z"
    - latency: 5.842305ms
      message: 'load-balancer-api-external: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:07Z"
    - latency: 10.115188ms
      message: 'load-balancer-api-external: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:03:07Z"
    - latency: 3.754364ms
      message: 'load-balancer-api-external: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:07Z"
    - latency: 8.521183ms
      message: 'load-balancer-api-external: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:02:07Z"
    - latency: 5.397214ms
      message: 'load-balancer-api-external: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 8.342643ms
      message: 'load-balancer-api-external: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "19867"
    uid: 2ee4166d-37ee-4a6f-9757-b087c309178c
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:53:07Z"
      message: 'load-balancer-api-internal: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.091748ms
      message: 'load-balancer-api-internal: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:07Z"
    - latency: 7.681601ms
      message: 'load-balancer-api-internal: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:05:07Z"
    - latency: 4.523345ms
      message: 'load-balancer-api-internal: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:07Z"
    - latency: 7.762358ms
      message: 'load-balancer-api-internal: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:04:07Z"
    - latency: 5.903614ms
      message: 'load-balancer-api-internal: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:07Z"
    - latency: 10.020317ms
      message: 'load-balancer-api-internal: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:03:07Z"
    - latency: 3.762615ms
      message: 'load-balancer-api-internal: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:07Z"
    - latency: 8.506078ms
      message: 'load-balancer-api-internal: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:02:07Z"
    - latency: 5.333058ms
      message: 'load-balancer-api-internal: tcp connection to ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 8.317332ms
      message: 'load-balancer-api-internal: resolved host name ad0cd7de85a844153be8f62ee3e5c6bb-99d237560c2eaca0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:01:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-network-check-target-ip-10-0-134-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "17694"
    uid: 5a64a04a-c77f-49b0-b785-4318aadd8987
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:54:07Z"
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.145073ms
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 726.548µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:07Z"
    - latency: 902.629µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:07Z"
    - latency: 977.81µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:07Z"
    - latency: 758.877µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:07Z"
    - latency: 820.879µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:07Z"
    - latency: 724.531µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:07Z"
    - latency: 872.851µs
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:07Z"
    - latency: 1.229152ms
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:07Z"
    - latency: 1.356239ms
      message: 'network-check-target-ip-10-0-134-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-network-check-target-ip-10-0-137-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "17695"
    uid: 1290898e-b5f5-45b1-884a-ac394082e054
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:54:07Z"
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.213862ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 2.290149ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:07Z"
    - latency: 2.229252ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:07Z"
    - latency: 2.401547ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:07Z"
    - latency: 2.157005ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:07Z"
    - latency: 2.046818ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:07Z"
    - latency: 2.302898ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:07Z"
    - latency: 2.395484ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:07Z"
    - latency: 2.111405ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:07Z"
    - latency: 2.221695ms
      message: 'network-check-target-ip-10-0-137-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-network-check-target-ip-10-0-137-27
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "17696"
    uid: 3ee4a3d9-1fa1-4e7e-ba00-bf19e38cbc9c
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:54:07Z"
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.690113ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 1.803061ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:00:07Z"
    - latency: 1.932949ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:59:07Z"
    - latency: 1.761284ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:58:07Z"
    - latency: 1.659081ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:57:07Z"
    - latency: 1.865536ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:56:07Z"
    - latency: 1.837703ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:55:07Z"
    - latency: 1.918858ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:54:07Z"
    - latency: 2.012788ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:53:07Z"
    - latency: 2.038858ms
      message: 'network-check-target-ip-10-0-137-27: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T02:52:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T02:47:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-146.ec2.internal
      uid: c68c0309-bc07-4ba5-a51d-dc544f5335ce
    resourceVersion: "19866"
    uid: 59144f22-aeaa-401f-9ca1-c2f9aef7163d
  spec:
    sourcePod: network-check-source-7cbc45fddc-llwcx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T02:53:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 757.887µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:05:07Z"
    - latency: 1.572125ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:05:07Z"
    - latency: 997.351µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:04:07Z"
    - latency: 1.603529ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:04:07Z"
    - latency: 771.354µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:03:07Z"
    - latency: 1.930074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:03:07Z"
    - latency: 762.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:02:07Z"
    - latency: 2.280411ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:02:07Z"
    - latency: 770.948µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T03:01:07Z"
    - latency: 1.550341ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T03:01:07Z"
kind: List
metadata:
  resourceVersion: ""