fix links after move

content/en/docs/components/central-dash/overview.md

@@ -78,7 +78,7 @@ Port-forwarding typically does not work if any of the following are true:
     with the [CLI deployment](/docs/gke/deploy/deploy-cli/). (If you want to
     use port forwarding, you must deploy Kubeflow on an existing Kubernetes 
     cluster using the [`kfctl_k8s_istio` 
-    configuration](/docs/started/k8s/kfctl-k8s-istio/).)
+    configuration](/docs/methods/kfctl/deployment).)
 
   * You've configured the Istio ingress to only accept 
     HTTPS traffic on a specific domain or IP address.

content/en/docs/components/katib/experiment.md

@@ -755,7 +755,7 @@ kubectl apply -f <your-path/your-experiment-config.yaml>
 - (Optional) Katib's experiments don't work with
   [Istio sidecar injection](https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#automatic-sidecar-injection).
   If you install Kubeflow using
-  [Istio config](https://www.kubeflow.org/docs/started/k8s/kfctl-k8s-istio/),
+  [Istio config](https://www.kubeflow.org/docs/methods/kfctl/deployment),
   you have to disable sidecar injection. To do that, specify this annotation:
   `sidecar.istio.io/inject: "false"` in your experiment's trial template. For
   examples on how to do it for `Job`, `TFJob` (TensorFlow) or

content/en/docs/components/katib/hyperparameter.md

@@ -138,7 +138,7 @@ an experiment using the random algorithm example:
 1. (Optional) **Note:** Katib's experiments don't work with
    [Istio sidecar injection](https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#automatic-sidecar-injection).
    If you installed Kubeflow using
-   [Istio config](/docs/started/k8s/kfctl-k8s-istio/),
+   [Istio config](/docs/methods/kfctl/deployment),
    you have to disable sidecar injection. To do that, specify this annotation:
    `sidecar.istio.io/inject: "false"` in your experiment's trial template.
 
@@ -391,7 +391,7 @@ the Kubeflow's TensorFlow training job operator, TFJob:
 1. (Optional) **Note:** Katib's experiments don't work with
    [Istio sidecar injection](https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#automatic-sidecar-injection).
    If you installed Kubeflow using
-   [Istio config](/docs/started/k8s/kfctl-k8s-istio/),
+   [Istio config](/docs/methods/kfctl/deployment),
    you have to disable sidecar injection. To do that, specify this annotation:
    `sidecar.istio.io/inject: "false"` in your experiment's trial template.
    For the provided `TFJob` example check
@@ -435,7 +435,7 @@ using Kubeflow's PyTorch training job operator, PyTorchJob:
 1. (Optional) **Note:** Katib's experiments don't work with
    [Istio sidecar injection](https://istio.io/latest/docs/setup/additional-setup/sidecar-injection/#automatic-sidecar-injection).
    If you installed Kubeflow using
-   [Istio config](/docs/started/k8s/kfctl-k8s-istio/),
+   [Istio config](/docs/methods/kfctl/deployment),
    you have to disable sidecar injection. To do that, specify this annotation:
    `sidecar.istio.io/inject: "false"` in your experiment's trial template.
    For the provided `PyTorchJob` example setting the annotation should be similar to

content/en/docs/other-guides/usage-reporting.md

@@ -54,9 +54,9 @@ To prevent Spartakus from being deployed:
 
 1. Follow your chosen guide to deploying Kubeflow, but stop before you deploy
   Kubeflow. For example, see the guide to 
-  [deploying Kubeflow with kfctl_k8s_istio](/docs/started/k8s/kfctl-k8s-istio/).
+  [deploying Kubeflow with kfctl_k8s_istio](/docs/methods/kfctl/deployment).
 1. When you reach the 
-  [setup and deploy step](/docs/started/k8s/kfctl-k8s-istio/#alt-set-up-and-deploy),
+  [setup and deploy step](/docs/methods/kfctl/deployment#alt-set-up-and-deploy),
   **skip the `kfctl apply` command** and run the **`kfctl build`** command 
   instead, as  described in the above guide. Now you can edit the configuration
   files before deploying Kubeflow.

content/en/docs/started/getting-started.md

@@ -106,7 +106,7 @@ The matrix is therefore an alternative way of accessing the information in the
       <tr>
         <td><b>Existing Kubernetes cluster</b> using a standard Kubeflow
           installation</td>
-        <td><a href="/docs/started/k8s/kfctl-k8s-istio/">Docs</a></td>
+        <td><a href="/docs/methods/kfctl/deployment">Docs</a></td>
       </tr>
       <tr>
         <td><b>Existing Kubernetes cluster</b> using Dex for authentication</td>

content/en/docs/started/k8s/overview.md

@@ -32,7 +32,7 @@ Your Kubernetes cluster must meet the following minimum requirements:
   with a [dynamic volume
   provisioner](https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/).
   For more information, refer to [this
-  guide](https://www.kubeflow.org/docs/started/k8s/kfctl-k8s-istio/#before-you-start).
+  guide](https://www.kubeflow.org/docs/methods/kfctl/deployment/#before-you-start).
 
 <div class="table-responsive">
   <table class="table table-bordered">
@@ -147,7 +147,7 @@ governed by consensus within the Kubeflow community.
     <tbody>
       <tr>
         <td>kfctl_k8s_istio.yaml</td>
-        <td> This config creates a vanilla deployment of Kubeflow with all its core components without any external dependencies. The deployment can be customized based on your environment needs. <br />Follow instructions: <a href="/docs/started/k8s/kfctl-k8s-istio/">Kubeflow Deployment with kfctl_k8s_istio</a></td>
+        <td> This config creates a vanilla deployment of Kubeflow with all its core components without any external dependencies. The deployment can be customized based on your environment needs. <br />Follow instructions: <a href="/docs/methods/kfctl/deployment/">Kubeflow Deployment with kfctl_k8s_istio</a></td>
       </tr>
     </tbody>
     <tbody>