apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63570"
    uid: baea7798-817e-4c62-9cf4-1b9aaea9ae89
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:54:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.100704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 1.134646ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 886.726µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 910.924µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 1.162141ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 1.024437ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:24:30Z"
    - latency: 1.047503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:23:30Z"
    - latency: 1.047877ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:22:30Z"
    - latency: 1.001899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:21:30Z"
    - latency: 1.049583ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:20:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63101"
    uid: b7d2539e-6587-4186-8fd4-320dfb7226b0
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:53:30Z"
      message: 'load-balancer-api-external: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.047029ms
      message: 'load-balancer-api-external: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 7.115627ms
      message: 'load-balancer-api-external: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 3.845885ms
      message: 'load-balancer-api-external: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 6.827346ms
      message: 'load-balancer-api-external: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 8.5804ms
      message: 'load-balancer-api-external: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 7.360358ms
      message: 'load-balancer-api-external: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 5.075514ms
      message: 'load-balancer-api-external: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 6.535989ms
      message: 'load-balancer-api-external: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 4.21507ms
      message: 'load-balancer-api-external: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 7.853591ms
      message: 'load-balancer-api-external: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:25:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63100"
    uid: 7814ea09-6052-4287-bbf6-62eb0f2caaca
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:53:30Z"
      message: 'load-balancer-api-internal: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.159778ms
      message: 'load-balancer-api-internal: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 7.183629ms
      message: 'load-balancer-api-internal: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 3.362999ms
      message: 'load-balancer-api-internal: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 6.902791ms
      message: 'load-balancer-api-internal: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 6.62621ms
      message: 'load-balancer-api-internal: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 7.328082ms
      message: 'load-balancer-api-internal: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 5.116553ms
      message: 'load-balancer-api-internal: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 6.566847ms
      message: 'load-balancer-api-internal: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 4.823795ms
      message: 'load-balancer-api-internal: tcp connection to a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 7.833626ms
      message: 'load-balancer-api-internal: resolved host name a7acddea5be064c18898633e6470564d-2bd8e0515a20b7ff.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:25:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-network-check-target-ip-10-0-139-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63096"
    uid: 1ca0d488-5770-4270-a635-1119508cd4aa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:54:30Z"
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.526374ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 2.490353ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 2.524884ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 2.785338ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 2.454515ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 2.514865ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:24:30Z"
    - latency: 2.835638ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:23:30Z"
    - latency: 2.576283ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:22:30Z"
    - latency: 2.81164ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:21:30Z"
    - latency: 2.3691ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:20:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-network-check-target-ip-10-0-141-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63095"
    uid: 49c30b3d-fa0e-4acb-a787-a69c9e3851e4
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:54:30Z"
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 992.241µs
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 1.361157ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 982.659µs
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 956.145µs
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 1.139831ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 1.245071ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:24:30Z"
    - latency: 1.440227ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:23:30Z"
    - latency: 1.490322ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:22:30Z"
    - latency: 976.336µs
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:21:30Z"
    - latency: 1.034585ms
      message: 'network-check-target-ip-10-0-141-229: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:20:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-network-check-target-ip-10-0-141-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63098"
    uid: 47d6a4ff-192e-45c3-8546-4da25f3b4afa
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:54:30Z"
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376313ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 2.568116ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 2.555644ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 2.463273ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 2.516509ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 2.294372ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:24:30Z"
    - latency: 3.094423ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:23:30Z"
    - latency: 2.615163ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:22:30Z"
    - latency: 2.319135ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:21:30Z"
    - latency: 1.879902ms
      message: 'network-check-target-ip-10-0-141-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:20:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-20T12:47:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-229-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-229.ec2.internal
      uid: 2d639a33-60f9-4f9c-b084-d529513bd788
    resourceVersion: "63097"
    uid: a2d0f7c8-aa1c-44b8-87a6-5b72ad6c87e1
  spec:
    sourcePod: network-check-source-7bc5b6bf85-xkbwk
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-20T12:53:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 968.382µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 2.042029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:29:30Z"
    - latency: 1.161046ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 1.950282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:28:30Z"
    - latency: 1.096006ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 1.965514ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:27:30Z"
    - latency: 868.078µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 1.826206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:26:30Z"
    - latency: 906.408µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-20T13:25:30Z"
    - latency: 1.872268ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-20T13:25:30Z"
kind: List
metadata:
  resourceVersion: ""