apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "54408"
    uid: 9fc67b7d-6281-4666-bc83-96aa5a3b5233
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:56:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.181809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 1.066323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 996.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 964.749µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:14:25Z"
    - latency: 1.298366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:13:25Z"
    - latency: 3.940725ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:12:25Z"
    - latency: 3.714314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:11:25Z"
    - latency: 962.75µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:10:25Z"
    - latency: 942.443µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:09:25Z"
    - latency: 1.642673ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:08:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "56154"
    uid: 2e85ccd0-7377-4c73-89de-625103f8ddbe
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:55:25Z"
      message: 'load-balancer-api-external: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.751796ms
      message: 'load-balancer-api-external: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:19:25Z"
    - latency: 8.570319ms
      message: 'load-balancer-api-external: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:19:25Z"
    - latency: 4.091662ms
      message: 'load-balancer-api-external: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:18:25Z"
    - latency: 8.904723ms
      message: 'load-balancer-api-external: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:18:25Z"
    - latency: 4.310733ms
      message: 'load-balancer-api-external: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 9.370402ms
      message: 'load-balancer-api-external: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 4.119337ms
      message: 'load-balancer-api-external: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 7.683545ms
      message: 'load-balancer-api-external: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 5.743662ms
      message: 'load-balancer-api-external: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 8.268414ms
      message: 'load-balancer-api-external: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:15:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "56155"
    uid: 3ff59770-131a-4496-84e9-0976783a2197
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:55:26Z"
      message: 'load-balancer-api-internal: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.798321ms
      message: 'load-balancer-api-internal: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:19:25Z"
    - latency: 8.60887ms
      message: 'load-balancer-api-internal: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:19:25Z"
    - latency: 3.894031ms
      message: 'load-balancer-api-internal: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:18:25Z"
    - latency: 8.936026ms
      message: 'load-balancer-api-internal: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:18:25Z"
    - latency: 4.340143ms
      message: 'load-balancer-api-internal: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 9.340808ms
      message: 'load-balancer-api-internal: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 4.898149ms
      message: 'load-balancer-api-internal: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 7.725321ms
      message: 'load-balancer-api-internal: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 5.861962ms
      message: 'load-balancer-api-internal: tcp connection to ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 8.251142ms
      message: 'load-balancer-api-internal: resolved host name ac3d9970db5154ab5bc974bff7aebbd9-36445b8db47ec6d2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:15:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-ip-10-0-129-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "54405"
    uid: adc341ea-238e-4575-ab04-847e08d3913c
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:56:25Z"
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.031517ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 1.473618ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 1.056203ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 1.063248ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:14:25Z"
    - latency: 1.281901ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:13:25Z"
    - latency: 5.823529ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:12:25Z"
    - latency: 3.601386ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:11:25Z"
    - latency: 1.110241ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:10:25Z"
    - latency: 892.29µs
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:09:25Z"
    - latency: 1.504002ms
      message: 'network-check-target-ip-10-0-129-128: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:08:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-ip-10-0-142-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "54406"
    uid: 1e8060ad-0659-45ff-aca4-2d084875619f
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:56:25Z"
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.453676ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 1.991741ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 2.356426ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 2.578368ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:14:25Z"
    - latency: 2.485502ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:13:25Z"
    - latency: 3.767644ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:12:25Z"
    - latency: 3.0112ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:11:25Z"
    - latency: 2.590887ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:10:25Z"
    - latency: 2.484663ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:09:25Z"
    - latency: 2.600692ms
      message: 'network-check-target-ip-10-0-142-208: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:08:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-ip-10-0-143-252
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "54407"
    uid: cb76f58c-b0a3-44aa-80f7-374c59edf886
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:56:25Z"
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.895798ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 2.512021ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 2.380556ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 2.310519ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:14:25Z"
    - latency: 2.41834ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:13:25Z"
    - latency: 2.740505ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:12:25Z"
    - latency: 3.033184ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:11:25Z"
    - latency: 2.463382ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:10:25Z"
    - latency: 2.229492ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:09:25Z"
    - latency: 2.311105ms
      message: 'network-check-target-ip-10-0-143-252: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:08:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-05T19:49:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-128.ec2.internal
      uid: fe9f429d-5733-4d2c-9475-66b75e9e8c59
    resourceVersion: "56152"
    uid: a8aaa613-e6ec-4ec3-b799-f659d93271a4
  spec:
    sourcePod: network-check-source-685456655f-srp6j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-05T19:55:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:19:25Z"
    - latency: 2.071289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:19:25Z"
    - latency: 928.375µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:18:25Z"
    - latency: 1.683893ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:18:25Z"
    - latency: 1.055372ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 2.330744ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:17:25Z"
    - latency: 945.262µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 2.068763ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:16:25Z"
    - latency: 858.739µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-05T20:15:25Z"
    - latency: 1.738096ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-05T20:15:25Z"
kind: List
metadata:
  resourceVersion: ""