apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "63967"
    uid: 1a4bc6f0-3aa0-4ae8-a573-403df6c85076
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:19:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.862276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:54:11Z"
    - latency: 1.287967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:53:11Z"
    - latency: 773.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:52:11Z"
    - latency: 929.429µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:51:11Z"
    - latency: 968.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:50:11Z"
    - latency: 1.288105ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:49:11Z"
    - latency: 1.10586ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:48:11Z"
    - latency: 1.205094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:47:11Z"
    - latency: 1.401181ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:11Z"
    - latency: 1.315322ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "73387"
    uid: 2d318806-938f-4fd5-af6e-a261afc4a23d
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:18:11Z"
      message: 'load-balancer-api-external: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.777608ms
      message: 'load-balancer-api-external: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:00:11Z"
    - latency: 8.277349ms
      message: 'load-balancer-api-external: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:00:11Z"
    - latency: 5.739673ms
      message: 'load-balancer-api-external: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:59:11Z"
    - latency: 10.386097ms
      message: 'load-balancer-api-external: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:59:11Z"
    - latency: 5.796629ms
      message: 'load-balancer-api-external: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:58:11Z"
    - latency: 9.146711ms
      message: 'load-balancer-api-external: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:58:11Z"
    - latency: 5.506281ms
      message: 'load-balancer-api-external: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:57:11Z"
    - latency: 9.456065ms
      message: 'load-balancer-api-external: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:57:11Z"
    - latency: 5.629085ms
      message: 'load-balancer-api-external: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:56:11Z"
    - latency: 7.698497ms
      message: 'load-balancer-api-external: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:56:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "73386"
    uid: 85a7aae6-e3a5-4a7e-a308-c2802d7f8e4b
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:18:11Z"
      message: 'load-balancer-api-internal: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.468017ms
      message: 'load-balancer-api-internal: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:00:11Z"
    - latency: 8.165651ms
      message: 'load-balancer-api-internal: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:00:11Z"
    - latency: 5.754255ms
      message: 'load-balancer-api-internal: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:59:11Z"
    - latency: 10.287675ms
      message: 'load-balancer-api-internal: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:59:11Z"
    - latency: 7.123ms
      message: 'load-balancer-api-internal: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:58:11Z"
    - latency: 9.043364ms
      message: 'load-balancer-api-internal: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:58:11Z"
    - latency: 5.524139ms
      message: 'load-balancer-api-internal: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:57:11Z"
    - latency: 9.372111ms
      message: 'load-balancer-api-internal: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:57:11Z"
    - latency: 5.868447ms
      message: 'load-balancer-api-internal: tcp connection to abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:56:11Z"
    - latency: 8.142039ms
      message: 'load-balancer-api-internal: resolved host name abdd0f41fc2e540aab803eaaf0abe998-b18984b4e8bbc218.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:56:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-network-check-target-ip-10-0-136-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "63965"
    uid: c813f3e1-3516-4fbf-b581-9304cdf1dd53
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:19:11Z"
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.208218ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:54:11Z"
    - latency: 2.156652ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:53:11Z"
    - latency: 2.684236ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:52:11Z"
    - latency: 1.995577ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:51:11Z"
    - latency: 2.336942ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:50:11Z"
    - latency: 2.447309ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:49:11Z"
    - latency: 2.314132ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:48:11Z"
    - latency: 2.246409ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:47:11Z"
    - latency: 2.207129ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:11Z"
    - latency: 2.263981ms
      message: 'network-check-target-ip-10-0-136-14: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-network-check-target-ip-10-0-137-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "63964"
    uid: be1cdef1-47c8-444d-bf24-1f7732ab980f
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:19:11Z"
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.371194ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:54:11Z"
    - latency: 2.137105ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:53:11Z"
    - latency: 2.584522ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:52:11Z"
    - latency: 2.105012ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:51:11Z"
    - latency: 2.464893ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:50:11Z"
    - latency: 2.280601ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:49:11Z"
    - latency: 2.14329ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:48:11Z"
    - latency: 2.465653ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:47:11Z"
    - latency: 2.199001ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:11Z"
    - latency: 1.982775ms
      message: 'network-check-target-ip-10-0-137-131: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-network-check-target-ip-10-0-139-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "63963"
    uid: a86f3948-d682-4193-8cdf-bccfc547d3de
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:19:11Z"
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.092009ms
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:54:11Z"
    - latency: 898.608µs
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:53:11Z"
    - latency: 1.078929ms
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:52:11Z"
    - latency: 920.355µs
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:51:11Z"
    - latency: 1.157415ms
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:50:11Z"
    - latency: 1.492713ms
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:49:11Z"
    - latency: 1.043601ms
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:48:11Z"
    - latency: 922.012µs
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:47:11Z"
    - latency: 1.53398ms
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:46:11Z"
    - latency: 911.625µs
      message: 'network-check-target-ip-10-0-139-210: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:45:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:12:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-210.ec2.internal
      uid: f4e04446-18d6-425f-a765-8825b97a19fb
    resourceVersion: "73385"
    uid: 3dcb68ec-9539-488b-8657-f3fa917a274b
  spec:
    sourcePod: network-check-source-7d88cb55d8-59zm2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:18:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.365µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:00:11Z"
    - latency: 1.950154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:00:11Z"
    - latency: 881.813µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:59:11Z"
    - latency: 2.605141ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:59:11Z"
    - latency: 969.592µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:58:11Z"
    - latency: 1.802723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:58:11Z"
    - latency: 1.043499ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:57:11Z"
    - latency: 2.316582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:57:11Z"
    - latency: 1.057463ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:56:11Z"
    - latency: 1.769499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:56:11Z"
kind: List
metadata:
  resourceVersion: ""