apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "18156"
    uid: fcaccd09-ce72-4088-a817-279e661ef577
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:11:03Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.099829ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:03Z"
    - latency: 1.090184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:03Z"
    - latency: 848.698µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 905.851µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 939.59µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 929.656µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 1.105904ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 836.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:03Z"
    - latency: 964.343µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:03Z"
    - latency: 1.361146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "17401"
    uid: 2586b6ff-83c8-434d-9f9c-a158453235c4
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:10:03Z"
      message: 'load-balancer-api-external: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.17887ms
      message: 'load-balancer-api-external: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 9.872621ms
      message: 'load-balancer-api-external: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 5.052316ms
      message: 'load-balancer-api-external: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 7.425942ms
      message: 'load-balancer-api-external: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 4.980399ms
      message: 'load-balancer-api-external: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 8.19694ms
      message: 'load-balancer-api-external: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 5.539143ms
      message: 'load-balancer-api-external: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 8.335371ms
      message: 'load-balancer-api-external: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 5.578462ms
      message: 'load-balancer-api-external: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 7.959177ms
      message: 'load-balancer-api-external: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "17402"
    uid: 4af79db3-e246-49b7-859c-d5f5dcecd51b
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:10:03Z"
      message: 'load-balancer-api-internal: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.184239ms
      message: 'load-balancer-api-internal: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 9.901715ms
      message: 'load-balancer-api-internal: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 5.02793ms
      message: 'load-balancer-api-internal: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 7.490276ms
      message: 'load-balancer-api-internal: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 4.969028ms
      message: 'load-balancer-api-internal: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 8.254376ms
      message: 'load-balancer-api-internal: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 5.553507ms
      message: 'load-balancer-api-internal: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 8.366905ms
      message: 'load-balancer-api-internal: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 5.568888ms
      message: 'load-balancer-api-internal: tcp connection to ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 7.988216ms
      message: 'load-balancer-api-internal: resolved host name ae4855d715a0a40d68d1f9c845382d41-31b27c3a71d7c86d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:12:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-128-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "18153"
    uid: 83da0b84-88a3-4e6e-a24e-a835320c5477
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:11:03Z"
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.638µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:03Z"
    - latency: 824.403µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:03Z"
    - latency: 724.932µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 795.404µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 899.289µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 924.094µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 847.364µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 710.372µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:03Z"
    - latency: 835.699µs
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:03Z"
    - latency: 1.544843ms
      message: 'network-check-target-ip-10-0-128-234: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-137-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "18155"
    uid: fb9c48bd-3452-40b5-b411-e60f766513b9
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:11:03Z"
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.435066ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:03Z"
    - latency: 2.2218ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:03Z"
    - latency: 2.27281ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 2.147725ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 3.026826ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 2.348485ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 2.442088ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 2.290501ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:03Z"
    - latency: 2.315369ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:03Z"
    - latency: 2.18611ms
      message: 'network-check-target-ip-10-0-137-211: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-ip-10-0-143-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "18154"
    uid: fa1000d4-3fb4-464e-9fcc-1b6a36dea783
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:11:03Z"
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.235929ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:18:03Z"
    - latency: 1.936431ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:17:03Z"
    - latency: 1.990145ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 2.495816ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 2.089268ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 2.147837ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 2.10471ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 2.318177ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:11:03Z"
    - latency: 2.189718ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:10:03Z"
    - latency: 2.083456ms
      message: 'network-check-target-ip-10-0-143-127: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:09:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T18:04:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-234-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-234.ec2.internal
      uid: 241ec875-fcfe-46fa-bc4e-3d8029cd0133
    resourceVersion: "17400"
    uid: fd460bda-2b92-472c-8a9f-f89bbb893dc4
  spec:
    sourcePod: network-check-source-989f8b8dc-dbnrk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T18:10:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.10338ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 1.657593ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:16:03Z"
    - latency: 1.12164ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 1.577455ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:15:03Z"
    - latency: 863.591µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 1.686211ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:14:03Z"
    - latency: 968.03µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 1.651088ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:13:03Z"
    - latency: 875.26µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T18:12:03Z"
    - latency: 1.925166ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T18:12:03Z"
kind: List
metadata:
  resourceVersion: ""