apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "23307"
    uid: 7af3e0cf-025c-4e0e-a3a4-01cfa021806e
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.122417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 1.474835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 1.11602ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:18:42Z"
    - latency: 998.63µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:17:42Z"
    - latency: 1.216177ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:16:42Z"
    - latency: 1.034614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:15:42Z"
    - latency: 1.088744ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:14:42Z"
    - latency: 1.146672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:13:42Z"
    - latency: 1.219372ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:12:42Z"
    - latency: 960.937µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "24728"
    uid: 91f6eb11-8965-446c-933a-0648ee43f235
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:42Z"
      message: 'load-balancer-api-external: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.558037ms
      message: 'load-balancer-api-external: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:42Z"
    - latency: 6.690102ms
      message: 'load-balancer-api-external: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:23:42Z"
    - latency: 4.575555ms
      message: 'load-balancer-api-external: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:42Z"
    - latency: 7.33016ms
      message: 'load-balancer-api-external: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:22:42Z"
    - latency: 5.220203ms
      message: 'load-balancer-api-external: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:21:42Z"
    - latency: 6.246226ms
      message: 'load-balancer-api-external: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:21:42Z"
    - latency: 5.01389ms
      message: 'load-balancer-api-external: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 7.553187ms
      message: 'load-balancer-api-external: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 6.292007ms
      message: 'load-balancer-api-external: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 7.847019ms
      message: 'load-balancer-api-external: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "24729"
    uid: 6af32188-5415-4f6a-affa-9f88551570ee
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:42Z"
      message: 'load-balancer-api-internal: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.573965ms
      message: 'load-balancer-api-internal: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:42Z"
    - latency: 6.608505ms
      message: 'load-balancer-api-internal: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:23:42Z"
    - latency: 4.564118ms
      message: 'load-balancer-api-internal: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:42Z"
    - latency: 7.425621ms
      message: 'load-balancer-api-internal: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:22:42Z"
    - latency: 5.170013ms
      message: 'load-balancer-api-internal: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:21:42Z"
    - latency: 6.270895ms
      message: 'load-balancer-api-internal: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:21:42Z"
    - latency: 4.901293ms
      message: 'load-balancer-api-internal: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 7.478022ms
      message: 'load-balancer-api-internal: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 5.693546ms
      message: 'load-balancer-api-internal: tcp connection to aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 7.810016ms
      message: 'load-balancer-api-internal: resolved host name aa0f78bc89c1f4895bf995b5c967ba5a-f15fd51bbbd69a03.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:19:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-ip-10-0-128-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "23305"
    uid: ec3c2991-1e91-45b6-a343-9aa963cb6aef
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:42Z"
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.170261ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 2.382556ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 2.188445ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:18:42Z"
    - latency: 2.207871ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:17:42Z"
    - latency: 2.265142ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:16:42Z"
    - latency: 2.291478ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:15:42Z"
    - latency: 2.126793ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:14:42Z"
    - latency: 2.339818ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:13:42Z"
    - latency: 2.21406ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:12:42Z"
    - latency: 2.22409ms
      message: 'network-check-target-ip-10-0-128-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-ip-10-0-128-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "23306"
    uid: fdd9a72b-dbf7-476c-a50d-b3647b6c69bd
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:42Z"
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.282294ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 2.405509ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 2.217515ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:18:42Z"
    - latency: 2.143607ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:17:42Z"
    - latency: 2.209021ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:16:42Z"
    - latency: 2.037788ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:15:42Z"
    - latency: 2.198127ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:14:42Z"
    - latency: 2.6271ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:13:42Z"
    - latency: 2.061267ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:12:42Z"
    - latency: 2.311359ms
      message: 'network-check-target-ip-10-0-128-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-ip-10-0-131-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "23304"
    uid: e2dbf476-e0d7-444e-9b5c-b89334358ca7
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:06:42Z"
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.45406ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 1.069676ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 886.966µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:18:42Z"
    - latency: 1.107014ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:17:42Z"
    - latency: 1.049294ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:16:42Z"
    - latency: 1.038909ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:15:42Z"
    - latency: 1.017554ms
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:14:42Z"
    - latency: 944.748µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:13:42Z"
    - latency: 906.654µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:12:42Z"
    - latency: 952.71µs
      message: 'network-check-target-ip-10-0-131-144: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T15:59:41Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-144.ec2.internal
      uid: 79321ad6-f4ab-4202-911a-627e80e1487f
    resourceVersion: "24727"
    uid: dfddaec7-5f98-4ef4-b683-b19c341631c8
  spec:
    sourcePod: network-check-source-7cbc45fddc-zfb4v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T16:05:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 990.153µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:23:42Z"
    - latency: 2.005055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:23:42Z"
    - latency: 953.15µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:22:42Z"
    - latency: 1.735161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:22:42Z"
    - latency: 951.128µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:21:42Z"
    - latency: 1.900062ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:21:42Z"
    - latency: 1.017683ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 1.819056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:20:42Z"
    - latency: 958.229µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T16:19:42Z"
    - latency: 2.327378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T16:19:42Z"
kind: List
metadata:
  resourceVersion: ""