apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "71894"
    uid: 734b4850-b528-4fc4-9a63-54973835b01a
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 978.462µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 1.736409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 1.239346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 1.101416ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 1.795767ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:44:23Z"
    - latency: 1.115578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:43:23Z"
    - latency: 982.072µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:42:23Z"
    - latency: 1.121276ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:41:23Z"
    - latency: 910.396µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:40:23Z"
    - latency: 1.258483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:39:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "72698"
    uid: 9285455f-40d7-4819-ae1c-ed227f5c1185
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:23Z"
      message: 'load-balancer-api-external: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.4384ms
      message: 'load-balancer-api-external: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:49:23Z"
    - latency: 7.29657ms
      message: 'load-balancer-api-external: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:49:23Z"
    - latency: 53.25059ms
      message: 'load-balancer-api-external: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 8.043286ms
      message: 'load-balancer-api-external: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 54.258665ms
      message: 'load-balancer-api-external: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 8.092526ms
      message: 'load-balancer-api-external: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 55.439836ms
      message: 'load-balancer-api-external: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 7.156891ms
      message: 'load-balancer-api-external: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 53.004579ms
      message: 'load-balancer-api-external: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 8.280132ms
      message: 'load-balancer-api-external: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:45:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "72699"
    uid: bb4bfeee-2446-4dfe-8ddb-896e7e58df91
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:23Z"
      message: 'load-balancer-api-internal: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.465313ms
      message: 'load-balancer-api-internal: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:49:23Z"
    - latency: 7.346666ms
      message: 'load-balancer-api-internal: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:49:23Z"
    - latency: 53.314078ms
      message: 'load-balancer-api-internal: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 8.08621ms
      message: 'load-balancer-api-internal: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 55.129458ms
      message: 'load-balancer-api-internal: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 8.07173ms
      message: 'load-balancer-api-internal: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 55.510841ms
      message: 'load-balancer-api-internal: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 7.137045ms
      message: 'load-balancer-api-internal: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 52.998001ms
      message: 'load-balancer-api-internal: tcp connection to adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 8.244965ms
      message: 'load-balancer-api-internal: resolved host name adf9bd3603f5d4feb94c1d7340fbfba2-7a76273f21d70fcd.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:45:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-network-check-target-ip-10-0-133-50
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "71891"
    uid: f0de9bbf-465e-41af-a020-de5836f96234
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:23Z"
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.153533ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 2.256161ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 2.134776ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 2.05613ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 2.276022ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:44:23Z"
    - latency: 2.094746ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:43:23Z"
    - latency: 2.140683ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:42:23Z"
    - latency: 2.991716ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:41:23Z"
    - latency: 2.098572ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:40:23Z"
    - latency: 2.362726ms
      message: 'network-check-target-ip-10-0-133-50: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:39:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-network-check-target-ip-10-0-139-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "71892"
    uid: d7da46fd-829c-4c87-9b96-7654dc8a3844
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:23Z"
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 857.032µs
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 1.027383ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 962.957µs
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 956.236µs
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 917.128µs
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:44:23Z"
    - latency: 1.388591ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:43:23Z"
    - latency: 1.515833ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:42:23Z"
    - latency: 1.021727ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:41:23Z"
    - latency: 919.578µs
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:40:23Z"
    - latency: 989.974µs
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:39:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-network-check-target-ip-10-0-140-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "71893"
    uid: 5bab6cf7-e76a-4f3f-a907-433bb19f2301
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:38:23Z"
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.132669ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 1.952974ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 2.289959ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 2.221083ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 2.444263ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:44:23Z"
    - latency: 2.39411ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:43:23Z"
    - latency: 2.009945ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:42:23Z"
    - latency: 2.481108ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:41:23Z"
    - latency: 2.488496ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:40:23Z"
    - latency: 2.067373ms
      message: 'network-check-target-ip-10-0-140-145: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:39:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T07:31:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-83-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-83.us-west-1.compute.internal
      uid: 50612cd5-5b65-4319-848f-0a9e6d4b942f
    resourceVersion: "72696"
    uid: b05f05b2-0dda-46dd-943a-8b067d8702ab
  spec:
    sourcePod: network-check-source-6f78d59f99-fqhzf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T07:37:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 834.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:49:23Z"
    - latency: 1.492878ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:49:23Z"
    - latency: 862.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 1.856094ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:48:23Z"
    - latency: 853.792µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 2.075245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:47:23Z"
    - latency: 918.91µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 1.690153ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:46:23Z"
    - latency: 817.623µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T08:45:23Z"
    - latency: 2.377334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T08:45:23Z"
kind: List
metadata:
  resourceVersion: ""