apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32695"
    uid: 2307e318-9986-4b73-9b37-c08ed3f6e90b
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:14Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.038684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 1.430028ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 1.310083ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 1.162373ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 1.269252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 989.198µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:14Z"
    - latency: 1.186426ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:14Z"
    - latency: 1.116692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:14Z"
    - latency: 1.118262ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:14Z"
    - latency: 1.228823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32697"
    uid: de986ed5-26bb-474e-8784-888821f1cdb8
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:14Z"
      message: 'load-balancer-api-external: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.242437ms
      message: 'load-balancer-api-external: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 7.443701ms
      message: 'load-balancer-api-external: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 5.929498ms
      message: 'load-balancer-api-external: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 7.029266ms
      message: 'load-balancer-api-external: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 5.779036ms
      message: 'load-balancer-api-external: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 7.297747ms
      message: 'load-balancer-api-external: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 5.471853ms
      message: 'load-balancer-api-external: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 7.270946ms
      message: 'load-balancer-api-external: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 5.343204ms
      message: 'load-balancer-api-external: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 6.933869ms
      message: 'load-balancer-api-external: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:29:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32696"
    uid: 2081115e-df59-4928-af0a-c1ad0dcdd7a9
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:14Z"
      message: 'load-balancer-api-internal: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.174375ms
      message: 'load-balancer-api-internal: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 7.477534ms
      message: 'load-balancer-api-internal: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 5.923903ms
      message: 'load-balancer-api-internal: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 6.99345ms
      message: 'load-balancer-api-internal: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 4.351149ms
      message: 'load-balancer-api-internal: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 7.360846ms
      message: 'load-balancer-api-internal: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 5.54692ms
      message: 'load-balancer-api-internal: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 7.197019ms
      message: 'load-balancer-api-internal: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 5.376423ms
      message: 'load-balancer-api-internal: tcp connection to ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 6.908771ms
      message: 'load-balancer-api-internal: resolved host name ad350c85b961143f0a43728a229db47e-3efafefcc462c50a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:29:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-network-check-target-ip-10-0-134-125
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32693"
    uid: aa9b88cf-7fcd-469a-ab6c-aa950301db8d
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:14Z"
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.767502ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 2.372851ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 2.984536ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 2.718855ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 2.507688ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 3.010132ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:14Z"
    - latency: 2.513418ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:14Z"
    - latency: 2.344095ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:14Z"
    - latency: 2.875444ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:14Z"
    - latency: 2.468897ms
      message: 'network-check-target-ip-10-0-134-125: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-network-check-target-ip-10-0-137-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32692"
    uid: fd23f78b-97a6-4467-9241-9f8ed428770f
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:14Z"
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.556875ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 2.196655ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 2.262523ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 2.329345ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 2.196494ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 2.347123ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:14Z"
    - latency: 2.659168ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:14Z"
    - latency: 2.432128ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:14Z"
    - latency: 2.610598ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:14Z"
    - latency: 2.79399ms
      message: 'network-check-target-ip-10-0-137-226: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-network-check-target-ip-10-0-142-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32691"
    uid: 63b48e9d-1065-47ed-8f86-fff3e824bc8d
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:58:14Z"
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.133688ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 1.590068ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 954.376µs
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 1.569158ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 1.071338ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 1.56318ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:28:14Z"
    - latency: 1.467434ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:27:14Z"
    - latency: 1.085844ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:26:14Z"
    - latency: 1.073493ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:25:14Z"
    - latency: 1.057679ms
      message: 'network-check-target-ip-10-0-142-175: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:24:14Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T18:51:13Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-175-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-175.ec2.internal
      uid: 01087784-21bd-40ff-b91e-88332a7279fa
    resourceVersion: "32694"
    uid: c26bff5f-9fe4-496b-9552-9a0467795041
  spec:
    sourcePod: network-check-source-6f8b768455-pprg4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T18:57:14Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.030089ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 2.116767ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:33:14Z"
    - latency: 1.116724ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 2.163051ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:32:14Z"
    - latency: 1.155161ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 2.127712ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:31:14Z"
    - latency: 1.475251ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 2.135554ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:30:14Z"
    - latency: 1.058329ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T19:29:14Z"
    - latency: 1.943736ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T19:29:14Z"
kind: List
metadata:
  resourceVersion: ""