apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "26916"
    uid: ef33aaf8-097c-424d-9731-904ed625c8a4
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:46:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.670462ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:21:32Z"
    - latency: 1.820034ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:20:32Z"
    - latency: 1.216346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:19:32Z"
    - latency: 1.023911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:18:32Z"
    - latency: 887.378µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:17:32Z"
    - latency: 971.15µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:16:32Z"
    - latency: 1.156737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:15:32Z"
    - latency: 1.529355ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:14:32Z"
    - latency: 880.707µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:13:32Z"
    - latency: 812.186µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:12:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "29120"
    uid: 243845b2-fb38-479c-ad98-ea9867c407d5
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:45:32Z"
      message: 'load-balancer-api-external: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.685664ms
      message: 'load-balancer-api-external: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:27:32Z"
    - latency: 7.612241ms
      message: 'load-balancer-api-external: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:27:32Z"
    - latency: 4.765505ms
      message: 'load-balancer-api-external: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:26:32Z"
    - latency: 7.866997ms
      message: 'load-balancer-api-external: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:26:32Z"
    - latency: 4.754218ms
      message: 'load-balancer-api-external: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:25:32Z"
    - latency: 7.820069ms
      message: 'load-balancer-api-external: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:25:32Z"
    - latency: 5.213146ms
      message: 'load-balancer-api-external: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:24:32Z"
    - latency: 7.334536ms
      message: 'load-balancer-api-external: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:24:32Z"
    - latency: 4.576635ms
      message: 'load-balancer-api-external: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:23:32Z"
    - latency: 7.452703ms
      message: 'load-balancer-api-external: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:23:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "29121"
    uid: 1f55d708-41bb-4c4c-ab5f-6a7fb1203a62
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:45:32Z"
      message: 'load-balancer-api-internal: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.694913ms
      message: 'load-balancer-api-internal: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:27:32Z"
    - latency: 7.591988ms
      message: 'load-balancer-api-internal: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:27:32Z"
    - latency: 4.859723ms
      message: 'load-balancer-api-internal: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:26:32Z"
    - latency: 7.842728ms
      message: 'load-balancer-api-internal: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:26:32Z"
    - latency: 4.765988ms
      message: 'load-balancer-api-internal: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:25:32Z"
    - latency: 7.768568ms
      message: 'load-balancer-api-internal: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:25:32Z"
    - latency: 5.294235ms
      message: 'load-balancer-api-internal: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:24:32Z"
    - latency: 7.219574ms
      message: 'load-balancer-api-internal: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:24:32Z"
    - latency: 4.531683ms
      message: 'load-balancer-api-internal: tcp connection to a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:23:32Z"
    - latency: 7.638069ms
      message: 'load-balancer-api-internal: resolved host name a5aba199340a8407ab2a8b9ce1908086-2fc34e39f94b1425.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:23:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-ip-10-0-130-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "26913"
    uid: 50e35568-9e2a-4c56-a83d-0854f33b94c3
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:46:32Z"
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.289695ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:21:32Z"
    - latency: 2.071108ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:20:32Z"
    - latency: 1.856609ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:19:32Z"
    - latency: 2.038996ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:18:32Z"
    - latency: 2.020147ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:17:32Z"
    - latency: 1.920018ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:16:32Z"
    - latency: 1.89316ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:15:32Z"
    - latency: 1.849999ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:14:32Z"
    - latency: 2.030144ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:13:32Z"
    - latency: 1.83864ms
      message: 'network-check-target-ip-10-0-130-86: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:12:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-ip-10-0-143-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "26914"
    uid: 33889f60-0281-4c78-babc-445e46f5b4cd
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:46:32Z"
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.784059ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:21:32Z"
    - latency: 992.522µs
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:20:32Z"
    - latency: 1.415735ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:19:32Z"
    - latency: 975.81µs
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:18:32Z"
    - latency: 1.319921ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:17:32Z"
    - latency: 813.374µs
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:16:32Z"
    - latency: 1.418525ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:15:32Z"
    - latency: 795.127µs
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:14:32Z"
    - latency: 778.659µs
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:13:32Z"
    - latency: 1.138922ms
      message: 'network-check-target-ip-10-0-143-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:12:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-ip-10-0-143-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "26912"
    uid: 5fbbd790-3c4e-4655-a586-d9e92afacdd5
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:46:32Z"
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.190061ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:21:32Z"
    - latency: 2.347548ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:20:32Z"
    - latency: 1.955629ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:19:32Z"
    - latency: 2.308459ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:18:32Z"
    - latency: 1.772875ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:17:32Z"
    - latency: 1.966864ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:16:32Z"
    - latency: 2.190944ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:15:32Z"
    - latency: 2.393941ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:14:32Z"
    - latency: 2.210728ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:13:32Z"
    - latency: 2.038727ms
      message: 'network-check-target-ip-10-0-143-30: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:12:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T15:39:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-128.ec2.internal
      uid: ae2bae9f-bc81-4a4e-abed-b6874f531b59
    resourceVersion: "29119"
    uid: 96d590f3-a32a-4abb-8ab5-b93f3a5b436d
  spec:
    sourcePod: network-check-source-8894fc9bd-kgskm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T15:45:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.541µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:27:32Z"
    - latency: 1.912208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:27:32Z"
    - latency: 766.937µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:26:32Z"
    - latency: 2.122635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:26:32Z"
    - latency: 1.024913ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:25:32Z"
    - latency: 2.094545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:25:32Z"
    - latency: 902.848µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:24:32Z"
    - latency: 1.685109ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:24:32Z"
    - latency: 818.976µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T16:23:32Z"
    - latency: 2.039851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T16:23:32Z"
kind: List
metadata:
  resourceVersion: ""