apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "47263"
    uid: 51e67aa6-aac8-469a-9cc6-37f9a12100cd
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:13:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005468ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 932.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 982.223µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 789.485µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:31:49Z"
    - latency: 962.533µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:30:49Z"
    - latency: 1.582984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:29:49Z"
    - latency: 1.051655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:28:49Z"
    - latency: 991.885µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:27:49Z"
    - latency: 806.23µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:26:49Z"
    - latency: 958.239µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:25:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "49584"
    uid: 8bf10741-388d-4e5c-88b1-9d27cab4c530
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:12:49Z"
      message: 'load-balancer-api-external: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.965566ms
      message: 'load-balancer-api-external: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:36:49Z"
    - latency: 7.852337ms
      message: 'load-balancer-api-external: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:36:49Z"
    - latency: 4.880046ms
      message: 'load-balancer-api-external: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:35:49Z"
    - latency: 15.617046ms
      message: 'load-balancer-api-external: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:35:49Z"
    - latency: 5.289469ms
      message: 'load-balancer-api-external: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 8.438603ms
      message: 'load-balancer-api-external: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 4.724709ms
      message: 'load-balancer-api-external: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 8.374922ms
      message: 'load-balancer-api-external: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 5.667497ms
      message: 'load-balancer-api-external: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 7.902162ms
      message: 'load-balancer-api-external: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:32:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "49582"
    uid: 7c62ea60-c54e-4052-9481-862918868218
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:12:49Z"
      message: 'load-balancer-api-internal: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.343226ms
      message: 'load-balancer-api-internal: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:36:49Z"
    - latency: 7.888585ms
      message: 'load-balancer-api-internal: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:36:49Z"
    - latency: 4.027887ms
      message: 'load-balancer-api-internal: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:35:49Z"
    - latency: 15.520187ms
      message: 'load-balancer-api-internal: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:35:49Z"
    - latency: 5.157764ms
      message: 'load-balancer-api-internal: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 8.388095ms
      message: 'load-balancer-api-internal: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 4.701761ms
      message: 'load-balancer-api-internal: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 8.274547ms
      message: 'load-balancer-api-internal: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 2.945513ms
      message: 'load-balancer-api-internal: tcp connection to ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 7.915599ms
      message: 'load-balancer-api-internal: resolved host name ad5025478c7db4c85ac2a6ef8e49bf14-d8a4f31432075477.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:32:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-network-check-target-ip-10-0-137-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "47260"
    uid: ad567e1e-17bc-45e3-8043-52f3e373f843
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:13:49Z"
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 906.157µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 906.133µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 1.222275ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 831.827µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:31:49Z"
    - latency: 767.477µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:30:49Z"
    - latency: 940.999µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:29:49Z"
    - latency: 779.603µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:28:49Z"
    - latency: 1.25915ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:27:49Z"
    - latency: 975.475µs
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:26:49Z"
    - latency: 1.005228ms
      message: 'network-check-target-ip-10-0-137-118: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:25:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-network-check-target-ip-10-0-138-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "47262"
    uid: 27ca22a0-8f14-4cbc-9e61-fcff6396f1e5
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:13:49Z"
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96351ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 1.883822ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 1.950702ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 2.265478ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:31:49Z"
    - latency: 1.865447ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:30:49Z"
    - latency: 2.180421ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:29:49Z"
    - latency: 1.859851ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:28:49Z"
    - latency: 1.989862ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:27:49Z"
    - latency: 2.178905ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:26:49Z"
    - latency: 2.311716ms
      message: 'network-check-target-ip-10-0-138-0: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:25:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-network-check-target-ip-10-0-143-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "47261"
    uid: cca33846-765e-4e75-b34f-186a40de7d63
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:13:49Z"
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.286974ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 2.398629ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 2.210862ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 2.271366ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:31:49Z"
    - latency: 2.232085ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:30:49Z"
    - latency: 2.450129ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:29:49Z"
    - latency: 2.544432ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:28:49Z"
    - latency: 2.034687ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:27:49Z"
    - latency: 2.354498ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:26:49Z"
    - latency: 2.396175ms
      message: 'network-check-target-ip-10-0-143-42: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:25:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T07:06:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-118.ec2.internal
      uid: 69d83ef0-ce1e-4c7d-b445-e8f017401b9a
    resourceVersion: "49577"
    uid: 3d95dd22-c3c3-4a77-adc7-2e3b4a970e15
  spec:
    sourcePod: network-check-source-989f8b8dc-6xwd9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T07:12:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 846.26µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:36:49Z"
    - latency: 1.70186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:36:49Z"
    - latency: 1.035091ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:35:49Z"
    - latency: 1.482619ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:35:49Z"
    - latency: 1.084894ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 1.816402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:34:49Z"
    - latency: 830.31µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 1.557418ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:33:49Z"
    - latency: 1.127994ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T07:32:49Z"
    - latency: 1.670887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T07:32:49Z"
kind: List
metadata:
  resourceVersion: ""