diff --git a/calico-enterprise/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise/getting-started/install-on-clusters/rancher.mdx index 66cd93034a..983d160942 100644 --- a/calico-enterprise/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/rancher.mdx @@ -25,11 +25,11 @@ The geeky details of what you get: - A [compatible RKE cluster](../compatibility.mdx#rke) - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). + For help, see [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). - Configure your cluster for $[prodname] CNI - - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) to `plugin: none`. + - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) to `plugin: none`. :::note @@ -43,7 +43,7 @@ The geeky details of what you get: - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). ## How to diff --git a/calico-enterprise/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise/getting-started/install-on-clusters/rke2.mdx index b086d66c8d..fdb754b939 100644 --- a/calico-enterprise/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/rke2.mdx @@ -25,7 +25,7 @@ The geeky details of what you get: - A [compatible RKE2 cluster](../compatibility.mdx#rke2) with 2.6.5 or later - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). + For help, see [RKE2 quick start](https://docs.rke2.io/install/quickstart). - [Configure cluster with no CNI plugin](https://docs.rke2.io/install/configuration) using any of these methods: diff --git a/calico-enterprise/getting-started/install-on-clusters/windows-calico/rancher.mdx b/calico-enterprise/getting-started/install-on-clusters/windows-calico/rancher.mdx index f08cf5333e..25d0804eb5 100644 --- a/calico-enterprise/getting-started/install-on-clusters/windows-calico/rancher.mdx +++ b/calico-enterprise/getting-started/install-on-clusters/windows-calico/rancher.mdx @@ -19,7 +19,7 @@ Install $[prodnameWindows] on Rancher Kubernetes Engine (RKE). - A [compatible RKE cluster](../../compatibility.mdx#rke) -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -112,7 +112,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx index 88988c15c8..64ce4e509f 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rancher.mdx @@ -25,11 +25,11 @@ The geeky details of what you get: - A [compatible RKE cluster](../compatibility.mdx#rke) - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). + For help, see [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). - Configure your cluster for $[prodname] CNI - - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) to `plugin: none`. + - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) to `plugin: none`. :::note @@ -43,7 +43,7 @@ The geeky details of what you get: - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). ## How to diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx index 70968a4934..267a014b2d 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/rke2.mdx @@ -25,7 +25,7 @@ The geeky details of what you get: - A [compatible RKE2 cluster](../compatibility.mdx#rke2) with 2.6.5 or later - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). + For help, see [RKE2 quick start](https://docs.rke2.io/install/quickstart). - [Configure cluster with no CNI plugin](https://docs.rke2.io/install/configuration) using any of these methods: diff --git a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/windows-calico/rancher.mdx b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/windows-calico/rancher.mdx index 505a8a2e88..4852185902 100644 --- a/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/windows-calico/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.21-2/getting-started/install-on-clusters/windows-calico/rancher.mdx @@ -19,7 +19,7 @@ Install $[prodnameWindows] on Rancher Kubernetes Engine (RKE). - A [compatible RKE cluster](../../compatibility.mdx#rke) -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -103,7 +103,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx index fd4e09d231..8784a715ad 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rancher.mdx @@ -25,11 +25,11 @@ The geeky details of what you get: - A [compatible RKE cluster](../compatibility.mdx#rke) - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). + For help, see [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). - Configure your cluster for $[prodname] CNI - - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) to `plugin: none`. + - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) to `plugin: none`. :::note @@ -43,7 +43,7 @@ The geeky details of what you get: - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). ## How to diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx index a535cd9996..cb6fee5eab 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/rke2.mdx @@ -25,7 +25,7 @@ The geeky details of what you get: - A [compatible RKE2 cluster](../compatibility.mdx#rke2) with 2.6.5 or later - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). + For help, see [RKE2 quick start](https://docs.rke2.io/install/quickstart). - [Configure cluster with no CNI plugin](https://docs.rke2.io/install/configuration) using any of these methods: diff --git a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/windows-calico/rancher.mdx b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/windows-calico/rancher.mdx index ee5bb95d2a..f26b7e955b 100644 --- a/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/windows-calico/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.22-2/getting-started/install-on-clusters/windows-calico/rancher.mdx @@ -19,7 +19,7 @@ Install $[prodnameWindows] on Rancher Kubernetes Engine (RKE). - A [compatible RKE cluster](../../compatibility.mdx#rke) -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -103,7 +103,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx index fd4e09d231..8784a715ad 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rancher.mdx @@ -25,11 +25,11 @@ The geeky details of what you get: - A [compatible RKE cluster](../compatibility.mdx#rke) - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). + For help, see [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). - Configure your cluster for $[prodname] CNI - - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) to `plugin: none`. + - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) to `plugin: none`. :::note @@ -43,7 +43,7 @@ The geeky details of what you get: - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). ## How to diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx index a535cd9996..cb6fee5eab 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/rke2.mdx @@ -25,7 +25,7 @@ The geeky details of what you get: - A [compatible RKE2 cluster](../compatibility.mdx#rke2) with 2.6.5 or later - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). + For help, see [RKE2 quick start](https://docs.rke2.io/install/quickstart). - [Configure cluster with no CNI plugin](https://docs.rke2.io/install/configuration) using any of these methods: diff --git a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/windows-calico/rancher.mdx b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/windows-calico/rancher.mdx index ee5bb95d2a..f26b7e955b 100644 --- a/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/windows-calico/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.23-2/getting-started/install-on-clusters/windows-calico/rancher.mdx @@ -19,7 +19,7 @@ Install $[prodnameWindows] on Rancher Kubernetes Engine (RKE). - A [compatible RKE cluster](../../compatibility.mdx#rke) -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -103,7 +103,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx index d7b37e16ce..9bc7116257 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rancher.mdx @@ -25,11 +25,11 @@ The geeky details of what you get: - A [compatible RKE cluster](../compatibility.mdx#rke) - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). + For help, see [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). - Configure your cluster for $[prodname] CNI - - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) to `plugin: none`. + - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) to `plugin: none`. :::note @@ -43,7 +43,7 @@ The geeky details of what you get: - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). ## How to diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx index 1be901b5d2..87c8ada4d1 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/rke2.mdx @@ -25,7 +25,7 @@ The geeky details of what you get: - A [compatible RKE2 cluster](../compatibility.mdx#rke2) with 2.6.5 or later - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). + For help, see [RKE2 quick start](https://docs.rke2.io/install/quickstart). - [Configure cluster with no CNI plugin](https://docs.rke2.io/install/configuration) using any of these methods: diff --git a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/windows-calico/rancher.mdx b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/windows-calico/rancher.mdx index 5824927f2a..6db9aff150 100644 --- a/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/windows-calico/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/windows-calico/rancher.mdx @@ -19,7 +19,7 @@ Install $[prodnameWindows] on Rancher Kubernetes Engine (RKE). - A [compatible RKE cluster](../../compatibility.mdx#rke) -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -103,7 +103,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rancher.mdx b/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rancher.mdx index d7b37e16ce..9bc7116257 100644 --- a/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rancher.mdx @@ -25,11 +25,11 @@ The geeky details of what you get: - A [compatible RKE cluster](../compatibility.mdx#rke) - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). + For help, see [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/). Note that RKE2 is a different Kubernetes distribution and [documented separately](rke2.mdx). - Configure your cluster for $[prodname] CNI - - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) to `plugin: none`. + - Create a [Cluster Config File](https://rke.docs.rancher.com/example-yamls). In the config file under `network`, set the [network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) to `plugin: none`. :::note @@ -43,7 +43,7 @@ The geeky details of what you get: - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). ## How to diff --git a/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rke2.mdx b/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rke2.mdx index 1be901b5d2..87c8ada4d1 100644 --- a/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rke2.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/rke2.mdx @@ -25,7 +25,7 @@ The geeky details of what you get: - A [compatible RKE2 cluster](../compatibility.mdx#rke2) with 2.6.5 or later - For help, see [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/). + For help, see [RKE2 quick start](https://docs.rke2.io/install/quickstart). - [Configure cluster with no CNI plugin](https://docs.rke2.io/install/configuration) using any of these methods: diff --git a/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/windows-calico/rancher.mdx b/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/windows-calico/rancher.mdx index 5824927f2a..6db9aff150 100644 --- a/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/windows-calico/rancher.mdx +++ b/calico-enterprise_versioned_docs/version-3.24-2/getting-started/install-on-clusters/windows-calico/rancher.mdx @@ -19,7 +19,7 @@ Install $[prodnameWindows] on Rancher Kubernetes Engine (RKE). - A [compatible RKE cluster](../../compatibility.mdx#rke) -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -103,7 +103,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico/getting-started/kubernetes/k3s/multi-node-install.mdx b/calico/getting-started/kubernetes/k3s/multi-node-install.mdx index 955b861df5..059bdf230e 100644 --- a/calico/getting-started/kubernetes/k3s/multi-node-install.mdx +++ b/calico/getting-started/kubernetes/k3s/multi-node-install.mdx @@ -34,7 +34,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this tutorial was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: @@ -42,11 +42,11 @@ For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/ ### Initializing control plane instance -K3s installation script can be modified by [environment variables](https://rancher.com/docs/k3s/latest/en/installation/install-options/#options-for-installation-with-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. +K3s installation script can be modified by [environment variables](https://docs.k3s.io/installation/configuration#configuration-with-install-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. :::note -Full list of arguments can be viewed [at this link](https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/). +Full list of arguments can be viewed [at this link](https://docs.k3s.io/cli/server). ::: diff --git a/calico/getting-started/kubernetes/k3s/quickstart.mdx b/calico/getting-started/kubernetes/k3s/quickstart.mdx index 4840f15f0e..2fba356c97 100644 --- a/calico/getting-started/kubernetes/k3s/quickstart.mdx +++ b/calico/getting-started/kubernetes/k3s/quickstart.mdx @@ -36,7 +36,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this quickstart was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: diff --git a/calico/getting-started/kubernetes/rancher.mdx b/calico/getting-started/kubernetes/rancher.mdx index 0aefbc6ab8..d0dfb3416f 100644 --- a/calico/getting-started/kubernetes/rancher.mdx +++ b/calico/getting-started/kubernetes/rancher.mdx @@ -24,16 +24,16 @@ The geeky details of what you get: **Required** -- A compatible [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/) with version 1.3 +- A compatible [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/) with version 1.3 - - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) by setting `plugin: none` under `network` in your configuration file. + - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) by setting `plugin: none` under `network` in your configuration file. - RKE cluster meets the [$[prodname] requirements](requirements.mdx) - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). diff --git a/calico/getting-started/kubernetes/windows-calico/rancher.mdx b/calico/getting-started/kubernetes/windows-calico/rancher.mdx index e46baff2c2..13a5d446b2 100644 --- a/calico/getting-started/kubernetes/windows-calico/rancher.mdx +++ b/calico/getting-started/kubernetes/windows-calico/rancher.mdx @@ -25,7 +25,7 @@ Run Linux and Windows workloads on a RKE cluster with $[prodname]. **Required** -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) but which otherwise meets the $[prodnameWindows] Kubernetes [cluster requirements](requirements.mdx). This guide was tested with RKE v1.18.9. - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -122,7 +122,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/multi-node-install.mdx b/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/multi-node-install.mdx index 8bfc255a70..1dc5d46448 100644 --- a/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/multi-node-install.mdx +++ b/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/multi-node-install.mdx @@ -34,7 +34,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this tutorial was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: @@ -42,11 +42,11 @@ For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/ ### Initializing control plane instance -K3s installation script can be modified by [environment variables](https://rancher.com/docs/k3s/latest/en/installation/install-options/#options-for-installation-with-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. +K3s installation script can be modified by [environment variables](https://docs.k3s.io/installation/configuration#configuration-with-install-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. :::note -Full list of arguments can be viewed [at this link](https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/). +Full list of arguments can be viewed [at this link](https://docs.k3s.io/cli/server). ::: diff --git a/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/quickstart.mdx b/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/quickstart.mdx index a6c4a65032..0f9f8968ac 100644 --- a/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/quickstart.mdx +++ b/calico_versioned_docs/version-3.31/getting-started/kubernetes/k3s/quickstart.mdx @@ -36,7 +36,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this quickstart was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: diff --git a/calico_versioned_docs/version-3.31/getting-started/kubernetes/rancher.mdx b/calico_versioned_docs/version-3.31/getting-started/kubernetes/rancher.mdx index 747a96a315..b9b9b2eed8 100644 --- a/calico_versioned_docs/version-3.31/getting-started/kubernetes/rancher.mdx +++ b/calico_versioned_docs/version-3.31/getting-started/kubernetes/rancher.mdx @@ -24,16 +24,16 @@ The geeky details of what you get: **Required** -- A compatible [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/) with version 1.3 +- A compatible [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/) with version 1.3 - - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) by setting `plugin: none` under `network` in your configuration file. + - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) by setting `plugin: none` under `network` in your configuration file. - RKE cluster meets the [$[prodname] requirements](requirements.mdx) - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). diff --git a/calico_versioned_docs/version-3.31/getting-started/kubernetes/windows-calico/rancher.mdx b/calico_versioned_docs/version-3.31/getting-started/kubernetes/windows-calico/rancher.mdx index 4db91493f8..54fb265194 100644 --- a/calico_versioned_docs/version-3.31/getting-started/kubernetes/windows-calico/rancher.mdx +++ b/calico_versioned_docs/version-3.31/getting-started/kubernetes/windows-calico/rancher.mdx @@ -25,7 +25,7 @@ Run Linux and Windows workloads on a RKE cluster with $[prodname]. **Required** -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) but which otherwise meets the $[prodnameWindows] Kubernetes [cluster requirements](requirements.mdx). This guide was tested with RKE v1.18.9. - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -115,7 +115,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/multi-node-install.mdx b/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/multi-node-install.mdx index 4cdcc604f6..da0127b4a1 100644 --- a/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/multi-node-install.mdx +++ b/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/multi-node-install.mdx @@ -34,7 +34,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this tutorial was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: @@ -42,11 +42,11 @@ For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/ ### Initializing control plane instance -K3s installation script can be modified by [environment variables](https://rancher.com/docs/k3s/latest/en/installation/install-options/#options-for-installation-with-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. +K3s installation script can be modified by [environment variables](https://docs.k3s.io/installation/configuration#configuration-with-install-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. :::note -Full list of arguments can be viewed [at this link](https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/). +Full list of arguments can be viewed [at this link](https://docs.k3s.io/cli/server). ::: diff --git a/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/quickstart.mdx b/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/quickstart.mdx index 6e9ef72f8a..cc14399a45 100644 --- a/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/quickstart.mdx +++ b/calico_versioned_docs/version-3.32/getting-started/kubernetes/k3s/quickstart.mdx @@ -36,7 +36,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this quickstart was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: diff --git a/calico_versioned_docs/version-3.32/getting-started/kubernetes/rancher.mdx b/calico_versioned_docs/version-3.32/getting-started/kubernetes/rancher.mdx index cb7caf66d5..eec5d438ea 100644 --- a/calico_versioned_docs/version-3.32/getting-started/kubernetes/rancher.mdx +++ b/calico_versioned_docs/version-3.32/getting-started/kubernetes/rancher.mdx @@ -24,16 +24,16 @@ The geeky details of what you get: **Required** -- A compatible [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/) with version 1.3 +- A compatible [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/) with version 1.3 - - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) by setting `plugin: none` under `network` in your configuration file. + - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) by setting `plugin: none` under `network` in your configuration file. - RKE cluster meets the [$[prodname] requirements](requirements.mdx) - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). diff --git a/calico_versioned_docs/version-3.32/getting-started/kubernetes/windows-calico/rancher.mdx b/calico_versioned_docs/version-3.32/getting-started/kubernetes/windows-calico/rancher.mdx index cf9f7967d3..ebe9548bf4 100644 --- a/calico_versioned_docs/version-3.32/getting-started/kubernetes/windows-calico/rancher.mdx +++ b/calico_versioned_docs/version-3.32/getting-started/kubernetes/windows-calico/rancher.mdx @@ -25,7 +25,7 @@ Run Linux and Windows workloads on a RKE cluster with $[prodname]. **Required** -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) but which otherwise meets the $[prodnameWindows] Kubernetes [cluster requirements](requirements.mdx). This guide was tested with RKE v1.18.9. - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -115,7 +115,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). ::: diff --git a/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/multi-node-install.mdx b/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/multi-node-install.mdx index 955b861df5..059bdf230e 100644 --- a/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/multi-node-install.mdx +++ b/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/multi-node-install.mdx @@ -34,7 +34,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this tutorial was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: @@ -42,11 +42,11 @@ For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/ ### Initializing control plane instance -K3s installation script can be modified by [environment variables](https://rancher.com/docs/k3s/latest/en/installation/install-options/#options-for-installation-with-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. +K3s installation script can be modified by [environment variables](https://docs.k3s.io/installation/configuration#configuration-with-install-script). Here you are providing some extra arguments to disable `flannel`, disable k3s default network policy and change the pod ip CIDR. :::note -Full list of arguments can be viewed [at this link](https://rancher.com/docs/k3s/latest/en/installation/install-options/server-config/). +Full list of arguments can be viewed [at this link](https://docs.k3s.io/cli/server). ::: diff --git a/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/quickstart.mdx b/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/quickstart.mdx index 4840f15f0e..2fba356c97 100644 --- a/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/quickstart.mdx +++ b/calico_versioned_docs/version-3.33/getting-started/kubernetes/k3s/quickstart.mdx @@ -36,7 +36,7 @@ The geeky details of what you get: :::note K3s supports ARM processors too, this quickstart was tested against x86-64 processor environment. -For more detail please visit [this link](https://rancher.com/docs/k3s/latest/en/installation/installation-requirements/#operating-systems). +For more detail please visit [this link](https://docs.k3s.io/installation/requirements#operating-systems). ::: diff --git a/calico_versioned_docs/version-3.33/getting-started/kubernetes/rancher.mdx b/calico_versioned_docs/version-3.33/getting-started/kubernetes/rancher.mdx index 0aefbc6ab8..d0dfb3416f 100644 --- a/calico_versioned_docs/version-3.33/getting-started/kubernetes/rancher.mdx +++ b/calico_versioned_docs/version-3.33/getting-started/kubernetes/rancher.mdx @@ -24,16 +24,16 @@ The geeky details of what you get: **Required** -- A compatible [Rancher Kubernetes Engine cluster](https://rancher.com/docs/rke/latest/en/) with version 1.3 +- A compatible [Rancher Kubernetes Engine cluster](https://rke.docs.rancher.com/) with version 1.3 - - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins/) by setting `plugin: none` under `network` in your configuration file. + - Configure your cluster with a [Cluster Config File](https://rke.docs.rancher.com/installation#creating-the-cluster-configuration-file) and specify [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins) by setting `plugin: none` under `network` in your configuration file. - RKE cluster meets the [$[prodname] requirements](requirements.mdx) - A `kubectl` environment with access to your cluster - Use [Rancher kubectl Shell](https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig#accessing-clusters-with-kubectl-shell-in-the-rancher-ui) for access - - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rancher.com/docs/rke/latest/en/installation/#save-your-files). + - Ensure you have the [kubeconfig file that was generated when you created the cluster](https://rke.docs.rancher.com/installation#save-your-files). - If using a kubeconfig file locally, [install and set up the Kubectl CLI tool](https://kubernetes.io/docs/tasks/tools/install-kubectl/). diff --git a/calico_versioned_docs/version-3.33/getting-started/kubernetes/windows-calico/rancher.mdx b/calico_versioned_docs/version-3.33/getting-started/kubernetes/windows-calico/rancher.mdx index e46baff2c2..13a5d446b2 100644 --- a/calico_versioned_docs/version-3.33/getting-started/kubernetes/windows-calico/rancher.mdx +++ b/calico_versioned_docs/version-3.33/getting-started/kubernetes/windows-calico/rancher.mdx @@ -25,7 +25,7 @@ Run Linux and Windows workloads on a RKE cluster with $[prodname]. **Required** -- An RKE cluster provisioned with [no network plugin](https://rancher.com/docs/rke/latest/en/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) +- An RKE cluster provisioned with [no network plugin](https://rke.docs.rancher.com/config-options/add-ons/network-plugins#disabling-deployment-of-a-network-plug-in) but which otherwise meets the $[prodnameWindows] Kubernetes [cluster requirements](requirements.mdx). This guide was tested with RKE v1.18.9. - One or more Windows nodes that meet the [requirements](requirements.mdx). @@ -122,7 +122,7 @@ The following steps will outline the installation of $[prodname] networking on t :::note - For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rancher.com/docs/rke/latest/en/config-options/services/#kubernetes-api-server-options). + For Rancher default values for service CIDR and DNS cluster IP, see the [Rancher kube-api service options](https://rke.docs.rancher.com/config-options/services#kubernetes-api-server-options). :::