apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "19716"
    uid: 16a33635-323d-43c3-8d39-db3d2ac1f0ac
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:41: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.05576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 982.92µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 1.261428ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:53:44Z"
    - latency: 1.112215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:52:44Z"
    - latency: 1.058595ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:51:44Z"
    - latency: 921.898µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:50:44Z"
    - latency: 1.084734ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:49:44Z"
    - latency: 1.993926ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:48:44Z"
    - latency: 966.841µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:47:44Z"
    - latency: 939.197µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "20888"
    uid: 6cddb541-173d-4a06-8762-ab6daed9f034
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:40:44Z"
      message: 'load-balancer-api-external: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.828462ms
      message: 'load-balancer-api-external: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:58:44Z"
    - latency: 7.616688ms
      message: 'load-balancer-api-external: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:58:44Z"
    - latency: 4.293831ms
      message: 'load-balancer-api-external: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:57:44Z"
    - latency: 12.779184ms
      message: 'load-balancer-api-external: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:57:44Z"
    - latency: 4.159698ms
      message: 'load-balancer-api-external: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:56:44Z"
    - latency: 8.744866ms
      message: 'load-balancer-api-external: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:56:44Z"
    - latency: 5.210009ms
      message: 'load-balancer-api-external: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 8.885672ms
      message: 'load-balancer-api-external: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 5.136317ms
      message: 'load-balancer-api-external: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 8.808537ms
      message: 'load-balancer-api-external: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:54:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "20887"
    uid: 8c9a8d01-0edc-4c9c-98d7-571e54e41e09
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:40:44Z"
      message: 'load-balancer-api-internal: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.840861ms
      message: 'load-balancer-api-internal: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:58:44Z"
    - latency: 7.625642ms
      message: 'load-balancer-api-internal: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:58:44Z"
    - latency: 5.382047ms
      message: 'load-balancer-api-internal: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:57:44Z"
    - latency: 12.813485ms
      message: 'load-balancer-api-internal: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:57:44Z"
    - latency: 5.113905ms
      message: 'load-balancer-api-internal: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:56:44Z"
    - latency: 8.770816ms
      message: 'load-balancer-api-internal: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:56:44Z"
    - latency: 5.183603ms
      message: 'load-balancer-api-internal: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 8.951875ms
      message: 'load-balancer-api-internal: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 5.096832ms
      message: 'load-balancer-api-internal: tcp connection to af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 8.838339ms
      message: 'load-balancer-api-internal: resolved host name af4363f0a2d5a47cda860fce57ac428b-2d617a16fae08371.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:54:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-network-check-target-ip-10-0-128-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "19715"
    uid: f861745a-3d74-4577-80f0-ef5de33f5e9a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:41:44Z"
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.210155ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 2.235262ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 2.092408ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:53:44Z"
    - latency: 2.214161ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:52:44Z"
    - latency: 1.799537ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:51:44Z"
    - latency: 1.918571ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:50:44Z"
    - latency: 2.258978ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:49:44Z"
    - latency: 2.338665ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:48:44Z"
    - latency: 2.220541ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:47:44Z"
    - latency: 2.247825ms
      message: 'network-check-target-ip-10-0-128-249: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-network-check-target-ip-10-0-136-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "19714"
    uid: d33f3af5-bd5c-45ca-bb26-7c9a126ea731
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:41:44Z"
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.88718ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 1.887784ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 1.865487ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:53:44Z"
    - latency: 1.89787ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:52:44Z"
    - latency: 2.001765ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:51:44Z"
    - latency: 2.020346ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:50:44Z"
    - latency: 1.963301ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:49:44Z"
    - latency: 2.155925ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:48:44Z"
    - latency: 2.186248ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:47:44Z"
    - latency: 1.929978ms
      message: 'network-check-target-ip-10-0-136-34: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-network-check-target-ip-10-0-137-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "19713"
    uid: a83a5718-083e-4cb1-8668-fd5d55903479
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:41:44Z"
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 976.111µs
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 1.45582ms
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 1.304528ms
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:53:44Z"
    - latency: 833.342µs
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:52:44Z"
    - latency: 984.332µs
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:51:44Z"
    - latency: 798.23µs
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:50:44Z"
    - latency: 1.060961ms
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:49:44Z"
    - latency: 1.442891ms
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:48:44Z"
    - latency: 1.579056ms
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:47:44Z"
    - latency: 978.507µs
      message: 'network-check-target-ip-10-0-137-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T18:34:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-12.ec2.internal
      uid: cf29cee6-6b64-42d0-8965-f480b2c24777
    resourceVersion: "20886"
    uid: ae9e2cdb-6e20-4a11-bc2d-687c6086028d
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6psgp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T18:40:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.051714ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:58:44Z"
    - latency: 1.684773ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:58:44Z"
    - latency: 877.017µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:57:44Z"
    - latency: 1.754468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:57:44Z"
    - latency: 795.911µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:56:44Z"
    - latency: 1.615362ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:56:44Z"
    - latency: 978.424µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 1.938014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:55:44Z"
    - latency: 955.149µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:54:44Z"
    - latency: 1.815574ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:54:44Z"
kind: List
metadata:
  resourceVersion: ""