apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67142"
    uid: 22a81750-ec3b-4b46-ae25-52452cff8b8f
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:50:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.743µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 1.024291ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 836.347µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 1.388148ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 880.25µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:14:57Z"
    - latency: 911.479µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:13:57Z"
    - latency: 876.263µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:12:57Z"
    - latency: 860.836µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:11:57Z"
    - latency: 1.157217ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:10:57Z"
    - latency: 799.955µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67922"
    uid: 40a195f4-f5b6-4357-880c-1414438f3661
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:49:57Z"
      message: 'load-balancer-api-external: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.659718ms
      message: 'load-balancer-api-external: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:19:57Z"
    - latency: 8.753083ms
      message: 'load-balancer-api-external: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:19:57Z"
    - latency: 5.569424ms
      message: 'load-balancer-api-external: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 7.684678ms
      message: 'load-balancer-api-external: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 3.618266ms
      message: 'load-balancer-api-external: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 6.709438ms
      message: 'load-balancer-api-external: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 6.121303ms
      message: 'load-balancer-api-external: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 7.6408ms
      message: 'load-balancer-api-external: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 4.242488ms
      message: 'load-balancer-api-external: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 7.200687ms
      message: 'load-balancer-api-external: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67923"
    uid: 995f2e7a-1081-46a6-9b62-ed0f5fcfd7b3
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:49:57Z"
      message: 'load-balancer-api-internal: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.691805ms
      message: 'load-balancer-api-internal: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:19:57Z"
    - latency: 8.653826ms
      message: 'load-balancer-api-internal: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:19:57Z"
    - latency: 5.530224ms
      message: 'load-balancer-api-internal: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 7.738432ms
      message: 'load-balancer-api-internal: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 3.615977ms
      message: 'load-balancer-api-internal: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 6.579366ms
      message: 'load-balancer-api-internal: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 5.924925ms
      message: 'load-balancer-api-internal: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 7.694649ms
      message: 'load-balancer-api-internal: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 4.25023ms
      message: 'load-balancer-api-internal: tcp connection to a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 7.131794ms
      message: 'load-balancer-api-internal: resolved host name a649b4ae7478e45d885e4645c81a90cb-d7e4a185d46e1b3e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:15:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-ip-10-0-131-202
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67141"
    uid: 43e7654b-8789-4d4d-a539-3275121519f2
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:50:57Z"
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.223289ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 2.125188ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 2.499514ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 2.092042ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 2.143894ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:14:57Z"
    - latency: 2.163526ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:13:57Z"
    - latency: 2.233959ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:12:57Z"
    - latency: 2.01487ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:11:57Z"
    - latency: 2.071898ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:10:57Z"
    - latency: 2.236318ms
      message: 'network-check-target-ip-10-0-131-202: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-ip-10-0-139-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67139"
    uid: 01abebbc-4439-43d8-b802-b258b30b4631
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:50:57Z"
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.578µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 919.828µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 861.125µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 1.02596ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 866.541µs
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:14:57Z"
    - latency: 1.165683ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:13:57Z"
    - latency: 1.138637ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:12:57Z"
    - latency: 1.274572ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:11:57Z"
    - latency: 1.08269ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:10:57Z"
    - latency: 1.01446ms
      message: 'network-check-target-ip-10-0-139-144: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-ip-10-0-142-57
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67140"
    uid: a403f143-1574-4341-9d1b-6e0c0d28b1f2
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:50:57Z"
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.019401ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 1.952505ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 2.0568ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 2.268429ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 1.946391ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:14:57Z"
    - latency: 1.95528ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:13:57Z"
    - latency: 2.265134ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:12:57Z"
    - latency: 2.030719ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:11:57Z"
    - latency: 1.844363ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:10:57Z"
    - latency: 1.937022ms
      message: 'network-check-target-ip-10-0-142-57: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:09:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T05:43:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-144.ec2.internal
      uid: a9097ded-2a4e-4205-8402-ee3b9b39af52
    resourceVersion: "67921"
    uid: 52883161-fd68-43c4-93e3-3f4189b21c3b
  spec:
    sourcePod: network-check-source-7cbc45fddc-gvxmv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T05:49:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.564µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:19:57Z"
    - latency: 1.874581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:19:57Z"
    - latency: 986.154µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 2.071493ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:18:57Z"
    - latency: 915.778µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 1.563757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:17:57Z"
    - latency: 1.037259ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 1.734671ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:16:57Z"
    - latency: 861.082µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T06:15:57Z"
    - latency: 2.016784ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T06:15:57Z"
kind: List
metadata:
  resourceVersion: ""