apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "53440"
    uid: d358b923-91a8-42e4-96bc-3397f1f2e45c
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:25:09Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 829.318µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 874.531µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 860.483µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 1.042763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 929.655µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:09Z"
    - latency: 898.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:48:09Z"
    - latency: 923.943µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:47:09Z"
    - latency: 794.824µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:46:09Z"
    - latency: 1.014163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:45:09Z"
    - latency: 983.54µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "54354"
    uid: e676884a-02b4-4710-bf59-092283e77cde
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:24:09Z"
      message: 'load-balancer-api-external: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.680604ms
      message: 'load-balancer-api-external: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:09Z"
    - latency: 7.331668ms
      message: 'load-balancer-api-external: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:54:09Z"
    - latency: 4.985415ms
      message: 'load-balancer-api-external: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 7.001922ms
      message: 'load-balancer-api-external: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 4.547079ms
      message: 'load-balancer-api-external: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 7.30443ms
      message: 'load-balancer-api-external: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 4.814499ms
      message: 'load-balancer-api-external: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 6.203923ms
      message: 'load-balancer-api-external: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 4.312471ms
      message: 'load-balancer-api-external: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 7.004046ms
      message: 'load-balancer-api-external: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:50:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "54353"
    uid: 319fac3f-94ed-4293-b301-35142c9c5641
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:24:09Z"
      message: 'load-balancer-api-internal: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.652932ms
      message: 'load-balancer-api-internal: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:09Z"
    - latency: 7.419692ms
      message: 'load-balancer-api-internal: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:54:09Z"
    - latency: 4.962246ms
      message: 'load-balancer-api-internal: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 7.038129ms
      message: 'load-balancer-api-internal: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 4.746229ms
      message: 'load-balancer-api-internal: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 7.416309ms
      message: 'load-balancer-api-internal: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 4.802414ms
      message: 'load-balancer-api-internal: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 6.147818ms
      message: 'load-balancer-api-internal: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 4.292449ms
      message: 'load-balancer-api-internal: tcp connection to a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 7.096618ms
      message: 'load-balancer-api-internal: resolved host name a4eb272de0a2248469b8f2da7f5e4821-575a297ea4b4f539.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:50:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-network-check-target-ip-10-0-128-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "53437"
    uid: cea54e84-a7c5-49ec-af02-4126ac335040
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:25:09Z"
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.27µs
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 929.979µs
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 1.030101ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 1.193375ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 699.027µs
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:09Z"
    - latency: 967.875µs
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:48:09Z"
    - latency: 812.266µs
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:47:09Z"
    - latency: 1.187726ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:46:09Z"
    - latency: 1.282931ms
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:45:09Z"
    - latency: 746.495µs
      message: 'network-check-target-ip-10-0-128-47: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-network-check-target-ip-10-0-131-65
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "53439"
    uid: 14d159be-08e3-41c3-892c-cf385e7c396e
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:25:09Z"
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.261313ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 2.074815ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 2.152569ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 2.283863ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 2.305728ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:09Z"
    - latency: 2.301278ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:48:09Z"
    - latency: 2.208355ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:47:09Z"
    - latency: 2.33158ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:46:09Z"
    - latency: 2.006329ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:45:09Z"
    - latency: 1.610768ms
      message: 'network-check-target-ip-10-0-131-65: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-network-check-target-ip-10-0-139-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "53438"
    uid: 5f51e4eb-dd99-4f58-8ffb-7e74cbba6e61
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:25:09Z"
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.331638ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 2.12705ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 2.293928ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 1.974011ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 2.330588ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:09Z"
    - latency: 2.289037ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:48:09Z"
    - latency: 2.273841ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:47:09Z"
    - latency: 2.391114ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:46:09Z"
    - latency: 2.034302ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:45:09Z"
    - latency: 1.972422ms
      message: 'network-check-target-ip-10-0-139-175: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:44:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:18:08Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-47-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-47.ec2.internal
      uid: 32f87b0c-0caf-4126-953b-b3d09633f1b5
    resourceVersion: "54352"
    uid: 54688f35-eb45-436c-a99f-be53010d74a1
  spec:
    sourcePod: network-check-source-989f8b8dc-k9pcs
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:24:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.232µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:09Z"
    - latency: 2.013585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:54:09Z"
    - latency: 923.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 1.938365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:53:09Z"
    - latency: 744.21µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 2.197737ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:52:09Z"
    - latency: 948.059µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 1.47249ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:51:09Z"
    - latency: 790.569µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:09Z"
    - latency: 1.859673ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:50:09Z"
kind: List
metadata:
  resourceVersion: ""