apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "19242"
    uid: 820b2a38-edc9-47e3-bc8d-70e4b60f9336
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:22: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.458718ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 878.749µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 956.322µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:34:03Z"
    - latency: 1.320709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:33:03Z"
    - latency: 1.309334ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:32:03Z"
    - latency: 1.45977ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:31:03Z"
    - latency: 1.486212ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:30:03Z"
    - latency: 867.264µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:29:03Z"
    - latency: 788.64µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:28:03Z"
    - latency: 801.306µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:27:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "20384"
    uid: 4f214005-d6c5-4b2a-990b-d159f136e3fd
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:21:03Z"
      message: 'load-balancer-api-external: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.871805ms
      message: 'load-balancer-api-external: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:39:03Z"
    - latency: 7.993127ms
      message: 'load-balancer-api-external: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:39:03Z"
    - latency: 3.679614ms
      message: 'load-balancer-api-external: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:38:03Z"
    - latency: 10.926269ms
      message: 'load-balancer-api-external: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:38:03Z"
    - latency: 3.902173ms
      message: 'load-balancer-api-external: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:37:03Z"
    - latency: 8.274055ms
      message: 'load-balancer-api-external: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:37:03Z"
    - latency: 4.283046ms
      message: 'load-balancer-api-external: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 7.998207ms
      message: 'load-balancer-api-external: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 3.319016ms
      message: 'load-balancer-api-external: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 8.239132ms
      message: 'load-balancer-api-external: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:35:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "20383"
    uid: 70974bf4-d767-4425-8943-32398415d7a5
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:21:03Z"
      message: 'load-balancer-api-internal: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.845191ms
      message: 'load-balancer-api-internal: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:39:03Z"
    - latency: 7.924498ms
      message: 'load-balancer-api-internal: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:39:03Z"
    - latency: 4.306187ms
      message: 'load-balancer-api-internal: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:38:03Z"
    - latency: 10.864953ms
      message: 'load-balancer-api-internal: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:38:03Z"
    - latency: 4.393697ms
      message: 'load-balancer-api-internal: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:37:03Z"
    - latency: 8.26454ms
      message: 'load-balancer-api-internal: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:37:03Z"
    - latency: 4.712373ms
      message: 'load-balancer-api-internal: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 8.03926ms
      message: 'load-balancer-api-internal: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 3.620629ms
      message: 'load-balancer-api-internal: tcp connection to a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 8.17302ms
      message: 'load-balancer-api-internal: resolved host name a24162181516148fbba3532f32344abd-eb53aa4a7de525fa.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:35:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-128-223
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "19241"
    uid: 2b8ac0a1-dc34-4fbf-8009-25ebcaa999ca
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:22:03Z"
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.404377ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 2.595881ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 2.326593ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:34:03Z"
    - latency: 2.507657ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:33:03Z"
    - latency: 2.265006ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:32:03Z"
    - latency: 2.081771ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:31:03Z"
    - latency: 2.332041ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:30:03Z"
    - latency: 2.34558ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:29:03Z"
    - latency: 2.228024ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:28:03Z"
    - latency: 2.158537ms
      message: 'network-check-target-ip-10-0-128-223: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:27:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-136-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "19240"
    uid: 246e665a-f0b8-4b65-bdc0-b0a04706d6bd
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:22:03Z"
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.901037ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 2.335329ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 2.148888ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:34:03Z"
    - latency: 2.112348ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:33:03Z"
    - latency: 1.967125ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:32:03Z"
    - latency: 2.215545ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:31:03Z"
    - latency: 2.061696ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:30:03Z"
    - latency: 2.13787ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:29:03Z"
    - latency: 2.210142ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:28:03Z"
    - latency: 2.052886ms
      message: 'network-check-target-ip-10-0-136-119: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:27:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-ip-10-0-143-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "19239"
    uid: 4c26bda4-7ec6-46aa-b41b-ced13fac5caf
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:22:03Z"
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072855ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 873.249µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 1.02693ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:34:03Z"
    - latency: 1.445253ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:33:03Z"
    - latency: 949.335µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:32:03Z"
    - latency: 1.741831ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:31:03Z"
    - latency: 870.343µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:30:03Z"
    - latency: 754.313µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:29:03Z"
    - latency: 733.31µs
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:28:03Z"
    - latency: 1.215686ms
      message: 'network-check-target-ip-10-0-143-99: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:27:03Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-30T08:15:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-99.ec2.internal
      uid: 2824d531-2d45-4e70-9d6d-4cb1886e89ec
    resourceVersion: "20382"
    uid: 969b870b-19f0-46da-a999-a0ed52407343
  spec:
    sourcePod: network-check-source-7d88cb55d8-4xr9k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-30T08:21:03Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 805.975µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:39:03Z"
    - latency: 2.589759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:39:03Z"
    - latency: 1.109273ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:38:03Z"
    - latency: 1.56261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:38:03Z"
    - latency: 875.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:37:03Z"
    - latency: 1.952399ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:37:03Z"
    - latency: 779.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 1.712128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:36:03Z"
    - latency: 1.226272ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-30T08:35:03Z"
    - latency: 1.781933ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-30T08:35:03Z"
kind: List
metadata:
  resourceVersion: ""