apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31431"
    uid: 5dd061a3-bbb9-4121-81ce-680fe5070534
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 1.239937ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 881.528µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 1.508112ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 1.015803ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 821.635µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:33:44Z"
    - latency: 979.223µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:32:44Z"
    - latency: 776.015µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:31:44Z"
    - latency: 1.044847ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:30:44Z"
    - latency: 1.216416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:29:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31432"
    uid: 5042b035-2051-469d-a1de-b34f0167f3a9
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:02:44Z"
      message: 'load-balancer-api-external: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.193427ms
      message: 'load-balancer-api-external: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 7.009853ms
      message: 'load-balancer-api-external: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 4.93441ms
      message: 'load-balancer-api-external: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 7.809497ms
      message: 'load-balancer-api-external: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 4.437888ms
      message: 'load-balancer-api-external: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 7.536809ms
      message: 'load-balancer-api-external: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 5.222784ms
      message: 'load-balancer-api-external: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 7.584009ms
      message: 'load-balancer-api-external: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 4.526258ms
      message: 'load-balancer-api-external: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 7.200709ms
      message: 'load-balancer-api-external: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:34:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31433"
    uid: 7743dbb8-4c0d-4cd3-acc6-893da22aaa62
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:02:44Z"
      message: 'load-balancer-api-internal: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.197354ms
      message: 'load-balancer-api-internal: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 7.147553ms
      message: 'load-balancer-api-internal: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 4.945878ms
      message: 'load-balancer-api-internal: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 7.887077ms
      message: 'load-balancer-api-internal: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 4.280706ms
      message: 'load-balancer-api-internal: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 7.588091ms
      message: 'load-balancer-api-internal: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 4.798952ms
      message: 'load-balancer-api-internal: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 7.637408ms
      message: 'load-balancer-api-internal: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 5.398917ms
      message: 'load-balancer-api-internal: tcp connection to aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 7.23541ms
      message: 'load-balancer-api-internal: resolved host name aed7d385c61204273b318f3d8999da70-9381f0977a2e1e1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:34:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-128-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31427"
    uid: bd2fa1b2-c25a-46dc-b8cb-2031f374d574
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:44Z"
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 801.215µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 880.984µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 747.194µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 1.353261ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 1.309134ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 781.644µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:33:44Z"
    - latency: 1.494607ms
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:32:44Z"
    - latency: 751.426µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:31:44Z"
    - latency: 834.025µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:30:44Z"
    - latency: 866.34µs
      message: 'network-check-target-ip-10-0-128-201: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:29:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-130-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31428"
    uid: dab7c063-0000-4daa-9525-546dc1829aba
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:44Z"
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.743756ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 1.86574ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 1.984615ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 1.901449ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 2.016752ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 1.891136ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:33:44Z"
    - latency: 1.99055ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:32:44Z"
    - latency: 1.749352ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:31:44Z"
    - latency: 1.837678ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:30:44Z"
    - latency: 1.960707ms
      message: 'network-check-target-ip-10-0-130-164: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:29:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-ip-10-0-140-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31429"
    uid: e880c776-ae9d-42b1-9b43-362fa3f46173
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:03:44Z"
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.049474ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 2.12596ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 1.958611ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 2.452236ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 2.081028ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 1.694191ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:33:44Z"
    - latency: 2.2412ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:32:44Z"
    - latency: 2.111052ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:31:44Z"
    - latency: 1.968684ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:30:44Z"
    - latency: 2.115888ms
      message: 'network-check-target-ip-10-0-140-191: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:29:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T19:56:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-201-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-201.ec2.internal
      uid: 19021234-7d13-4017-b5a5-04dc31670b0e
    resourceVersion: "31430"
    uid: 62f0bec9-9f8d-445e-b029-f17a75e486ce
  spec:
    sourcePod: network-check-source-8894fc9bd-sqd4v
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:02:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 899.871µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 1.841064ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:38:44Z"
    - latency: 1.028496ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 1.822704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:37:44Z"
    - latency: 707.492µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 2.306788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:36:44Z"
    - latency: 924.653µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 1.523199ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:35:44Z"
    - latency: 1.091938ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:34:44Z"
    - latency: 1.648589ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:34:44Z"
kind: List
metadata:
  resourceVersion: ""