apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "49037"
    uid: 60fea7de-d7b6-4374-802f-0d6650d9c0e2
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:28:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.10531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 2.363225ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 1.17059ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 1.235454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:46:27Z"
    - latency: 1.451647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:45:27Z"
    - latency: 1.40699ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:44:27Z"
    - latency: 1.178491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:43:27Z"
    - latency: 2.033682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:42:27Z"
    - latency: 1.030264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:41:27Z"
    - latency: 1.132479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:40:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "51786"
    uid: 43a54a11-d91d-4854-af70-25b45988dff8
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:27:27Z"
      message: 'load-balancer-api-external: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.330208ms
      message: 'load-balancer-api-external: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:51:27Z"
    - latency: 6.888547ms
      message: 'load-balancer-api-external: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:51:27Z"
    - latency: 4.325911ms
      message: 'load-balancer-api-external: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:50:27Z"
    - latency: 7.995572ms
      message: 'load-balancer-api-external: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:50:27Z"
    - latency: 4.733579ms
      message: 'load-balancer-api-external: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 8.63502ms
      message: 'load-balancer-api-external: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 4.378915ms
      message: 'load-balancer-api-external: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 17.452559ms
      message: 'load-balancer-api-external: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 4.104142ms
      message: 'load-balancer-api-external: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 7.482433ms
      message: 'load-balancer-api-external: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:47:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "51785"
    uid: ae09b900-f8ff-4664-a934-5ad24dc13d5e
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:27:27Z"
      message: 'load-balancer-api-internal: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.329565ms
      message: 'load-balancer-api-internal: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:51:27Z"
    - latency: 6.850006ms
      message: 'load-balancer-api-internal: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:51:27Z"
    - latency: 4.323983ms
      message: 'load-balancer-api-internal: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:50:27Z"
    - latency: 7.891676ms
      message: 'load-balancer-api-internal: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:50:27Z"
    - latency: 4.779543ms
      message: 'load-balancer-api-internal: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 8.497225ms
      message: 'load-balancer-api-internal: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 4.395355ms
      message: 'load-balancer-api-internal: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 17.249642ms
      message: 'load-balancer-api-internal: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 4.325795ms
      message: 'load-balancer-api-internal: tcp connection to a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 7.446546ms
      message: 'load-balancer-api-internal: resolved host name a659bf37524344a3f96a3f44e97adbd1-9bd4cbbc548fe755.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:47:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-ip-10-0-139-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "49036"
    uid: 66e3ca3f-4c39-4ff2-8a47-6a61465db844
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:28:27Z"
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.546677ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 2.424771ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 2.266618ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 2.139658ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:46:27Z"
    - latency: 2.942174ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:45:27Z"
    - latency: 2.478026ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:44:27Z"
    - latency: 2.247124ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:43:27Z"
    - latency: 2.222846ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:42:27Z"
    - latency: 2.254771ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:41:27Z"
    - latency: 1.988769ms
      message: 'network-check-target-ip-10-0-139-193: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:40:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-ip-10-0-140-148
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "49035"
    uid: 91e6ebb9-2c35-4e72-ba9f-2c2822991cb1
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:28:27Z"
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.376461ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 995.965µs
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 837.599µs
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 1.672825ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:46:27Z"
    - latency: 1.311147ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:45:27Z"
    - latency: 991.639µs
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:44:27Z"
    - latency: 1.476227ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:43:27Z"
    - latency: 1.532743ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:42:27Z"
    - latency: 1.30142ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:41:27Z"
    - latency: 1.500374ms
      message: 'network-check-target-ip-10-0-140-148: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:40:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-ip-10-0-141-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "49034"
    uid: 6690272b-c253-4282-981d-2b22137dee92
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:28:27Z"
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.49847ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 1.79426ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 1.651808ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 1.66283ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:46:27Z"
    - latency: 2.044758ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:45:27Z"
    - latency: 2.321703ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:44:27Z"
    - latency: 2.133969ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:43:27Z"
    - latency: 2.014755ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:42:27Z"
    - latency: 1.800846ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:41:27Z"
    - latency: 1.753824ms
      message: 'network-check-target-ip-10-0-141-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:40:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-08T11:21:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-148-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-148.ec2.internal
      uid: a069d524-9c51-45f0-be01-dd947df37d78
    resourceVersion: "51784"
    uid: 2cc74f67-cfcb-4699-b992-73b8adf4ffcd
  spec:
    sourcePod: network-check-source-989f8b8dc-wm2sf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-08T11:27:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.457µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:51:27Z"
    - latency: 2.013657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:51:27Z"
    - latency: 769.776µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:50:27Z"
    - latency: 2.038968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:50:27Z"
    - latency: 1.031668ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 2.495677ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:49:27Z"
    - latency: 942.471µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 2.759724ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:48:27Z"
    - latency: 899.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-08T11:47:27Z"
    - latency: 2.503218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-08T11:47:27Z"
kind: List
metadata:
  resourceVersion: ""