apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64793"
    uid: 8b1df55a-80f9-44a2-87a9-f7dbf11ff851
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:27:31Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 945.549µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 883.401µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 1.527206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 1.128807ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 1.407401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 1.020458ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:57:31Z"
    - latency: 1.338292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:56:31Z"
    - latency: 1.509631ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:55:31Z"
    - latency: 857.025µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:54:31Z"
    - latency: 1.027417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:53:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64794"
    uid: 30079f28-445a-4634-b2db-37a9a169135f
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26:31Z"
      message: 'load-balancer-api-external: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.968058ms
      message: 'load-balancer-api-external: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 6.71815ms
      message: 'load-balancer-api-external: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 5.496973ms
      message: 'load-balancer-api-external: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 6.158222ms
      message: 'load-balancer-api-external: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 11.085009ms
      message: 'load-balancer-api-external: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 6.44644ms
      message: 'load-balancer-api-external: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 3.997108ms
      message: 'load-balancer-api-external: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 6.413251ms
      message: 'load-balancer-api-external: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 4.479964ms
      message: 'load-balancer-api-external: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 6.811245ms
      message: 'load-balancer-api-external: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:58:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64795"
    uid: 1cf0fb0a-ba94-455d-b1aa-8b636cb442c6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26:31Z"
      message: 'load-balancer-api-internal: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.012084ms
      message: 'load-balancer-api-internal: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 6.694442ms
      message: 'load-balancer-api-internal: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 5.455643ms
      message: 'load-balancer-api-internal: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 6.210591ms
      message: 'load-balancer-api-internal: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 11.036597ms
      message: 'load-balancer-api-internal: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 6.249378ms
      message: 'load-balancer-api-internal: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 3.043822ms
      message: 'load-balancer-api-internal: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 6.370963ms
      message: 'load-balancer-api-internal: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 3.729223ms
      message: 'load-balancer-api-internal: tcp connection to ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 6.887088ms
      message: 'load-balancer-api-internal: resolved host name ad848a74b9e114266a6c71303cc245e8-c607d196650b7193.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:58:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-ip-10-0-132-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64789"
    uid: 5452dfc6-a3f7-4749-97ae-0339630ec45a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:27:31Z"
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.139964ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 846.883µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 1.81963ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 1.079641ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 817.595µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 932.126µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:57:31Z"
    - latency: 849.445µs
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:56:31Z"
    - latency: 1.0498ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:55:31Z"
    - latency: 1.267246ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:54:31Z"
    - latency: 1.49028ms
      message: 'network-check-target-ip-10-0-132-127: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:53:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-ip-10-0-133-196
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64792"
    uid: 7f47a517-90b0-48c4-94c7-852a27f69525
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:27:31Z"
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.309139ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 2.362682ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 3.034278ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 2.33264ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 2.357127ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 2.282133ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:57:31Z"
    - latency: 2.201717ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:56:31Z"
    - latency: 2.76177ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:55:31Z"
    - latency: 2.235315ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:54:31Z"
    - latency: 2.450254ms
      message: 'network-check-target-ip-10-0-133-196: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:53:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-ip-10-0-141-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64791"
    uid: e6f6cc7c-c7b3-4370-9093-508b31da8a53
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:27:31Z"
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376989ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 2.251833ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 2.352411ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 2.194235ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 2.300231ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 2.23671ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:57:31Z"
    - latency: 2.953496ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:56:31Z"
    - latency: 2.334757ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:55:31Z"
    - latency: 2.05539ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:54:31Z"
    - latency: 2.137296ms
      message: 'network-check-target-ip-10-0-141-47: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:53:31Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:20:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-127-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-127.ec2.internal
      uid: 2b69c89a-3b2d-42f2-99f0-de06d295f5ea
    resourceVersion: "64790"
    uid: b74c1642-9e9d-48c1-a1d7-ecd234ba5622
  spec:
    sourcePod: network-check-source-7bc5b6bf85-qjbft
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:26:31Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 915.581µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 1.884642ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:02:31Z"
    - latency: 1.048077ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 1.611257ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:01:31Z"
    - latency: 884.69µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 1.826382ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:00:31Z"
    - latency: 794.3µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 1.986006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:59:31Z"
    - latency: 963.462µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T22:58:31Z"
    - latency: 1.782098ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T22:58:31Z"
kind: List
metadata:
  resourceVersion: ""