From 5023231b5060e62602d993168e7583a0c165aa8e Mon Sep 17 00:00:00 2001 From: Nathan Jenan Date: Wed, 17 Oct 2018 17:12:06 -0700 Subject: [PATCH 1/7] Adding info on EKS Public IP options --- .../hosted-kubernetes-clusters/eks/_index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index f80f354049c..69e2e113bca 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -59,4 +59,9 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. 8. Specify any additional options (such as instance type or minimum and maximum number of nodes). Then click **Create**. +# Note on Public IP for Worker Notes +If you are specifying `Public IP for Worker Nodes` as `false`, be aware that you must specify a properly configured VPC and subnets (instances in the subnets must have a route to the internet in order to connect to the control plane). + +For example, a VPC could be constructed with 2 pairs of subnets, a private set and a public set. The private set would have their route tables set up to point to a NAT set up in their public counterpart. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html). + {{< result_create-cluster >}} From 70561348acfc7a2c358c9081a7ff60d12720bffb Mon Sep 17 00:00:00 2001 From: Nathan Jenan Date: Wed, 17 Oct 2018 17:12:17 -0700 Subject: [PATCH 2/7] Fixing typo --- layouts/shortcodes/step_create-cluster_cluster-options.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/layouts/shortcodes/step_create-cluster_cluster-options.html b/layouts/shortcodes/step_create-cluster_cluster-options.html index 5e15db10ed1..23084666e66 100644 --- a/layouts/shortcodes/step_create-cluster_cluster-options.html +++ b/layouts/shortcodes/step_create-cluster_cluster-options.html @@ -1 +1 @@ -

Use Cluster Options to choose the version of Kubernetes, what network provider will be used, if you want to enable Pod Security Policies and wether the nodes added to this cluster need to have a supported Docker version installed. +

Use Cluster Options to choose the version of Kubernetes, what network provider will be used, if you want to enable Pod Security Policies and whether the nodes added to this cluster need to have a supported Docker version installed. From c4f6e91694b7ac50d127dc8eb9d763438cad7c9a Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 18 Oct 2018 19:12:00 -0700 Subject: [PATCH 3/7] editing nate's note --- .../hosted-kubernetes-clusters/eks/_index.md | 31 +++++++++---------- 1 file changed, 15 insertions(+), 16 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index 69e2e113bca..ae2cc49c9d0 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -7,23 +7,20 @@ aliases: --- ## Objectives -1. [Create an account with appropriate permissions](#give-appropriate-permissions) + - Create (or give an existing) user appropriate permissions to create an EKS cluster. +- [1. Give Appropriate Permissions](#1-give-appropriate-permissions) +- [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key) +- [3. Create the EKS Cluster](#3-create-the-eks-cluster) -2. [Create an access key and secret key](#create-access-key-and-secret-key) - Create an access key and secret key to access Amazon Web Services (AWS) resources from Rancher. + -3. [Create the EKS Cluster](#create-the-eks-cluster) - - Using the AWS account, create your Amazon Elastic Container Service for Kubernetes (EKS) cluster in Rancher. - -## Give Appropriate Permissions +## 1. Give Appropriate Permissions Make sure that the account you will be using to create the EKS cluster has the appropriate permissions. Referring to the official [EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/IAM_policies.html) for details. -## Create Access Key and Secret Key +## 2. Create Access Key and Secret Key Use AWS to create an access key and client secret. @@ -39,7 +36,7 @@ Use AWS to create an access key and client secret. 6. Record the **Access key ID** and **Secret access key**. You will need to use these in Rancher to create your EKS cluster. -## Create the EKS Cluster +## 3. Create the EKS Cluster Use {{< product >}} to set up and configure your Kubernetes cluster. @@ -59,9 +56,11 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. 8. Specify any additional options (such as instance type or minimum and maximum number of nodes). Then click **Create**. -# Note on Public IP for Worker Notes -If you are specifying `Public IP for Worker Nodes` as `false`, be aware that you must specify a properly configured VPC and subnets (instances in the subnets must have a route to the internet in order to connect to the control plane). - -For example, a VPC could be constructed with 2 pairs of subnets, a private set and a public set. The private set would have their route tables set up to point to a NAT set up in their public counterpart. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html). - {{< result_create-cluster >}} + +# Note on Public IP for Worker Notes + +If you specify `Public IP for Worker Nodes` as `false`, you must also specify a VPC with subnets that allow your instances to access the internet. This access is required so that your worker nodes can connect to the Kubernetes control plane. + +One possible configuration solution is a VPC constructed with two subnets, a private set and a public set. The private set should have its route tables configured to point toward a NAT in the public set. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html). + From fe98b045c619331aeca211b4392db7b6c2f23a4a Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 19 Oct 2018 14:00:04 -0700 Subject: [PATCH 4/7] making big edits --- .../hosted-kubernetes-clusters/eks/_index.md | 80 ++++++++++++++++--- 1 file changed, 70 insertions(+), 10 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index ae2cc49c9d0..7193162ff62 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -48,19 +48,79 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. 4. {{< step_create-cluster_member-roles >}} -5. Enter your **Access Key**. +1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field. -6. Enter your **Secret Key** + | Setting | Description | + | ---------- | -------------------------------------------------------------------------------------------------------------------- | + | Region | From the drop-down choose the geographical region in which to build your cluster. | + | Access Key | Enter the access key that you created in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | + | Secret Key | Enter the secret key that you created in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | + +1. Click **Next: Select Service Role**. Then choose a service role. -7. Click **Next: Authenticate & configure nodes**. + Service Role | Description + -------------|--------------------------- + Standard: Rancher generated service role | placeholder + Custom: Choose from your existing service roles | placeholder -8. Specify any additional options (such as instance type or minimum and maximum number of nodes). Then click **Create**. +1. Click **Next: Select VPC and Subnet**. + +1. Choose an option for **Public IP for Worker Nodes**. Your selection for this option determines what options are available for **VPC & Subnet**. + + Option | Description + -------|------------ + Yes | When your cluster nodes are provisioned, they're assigned a both a private and public IP address. + No: Private IPs only | When your cluster nodes are provisioned, they're assigned only a private IP address.

If you choose this option, you must also choose a **VPC & Subnet** that allow your instances to access the internet. This access is required so that your worker nodes can connect to the Kubernetes control plane. + +1. Now choose a **VPC & Subnet**. Follow one of the sets of instructions below based on your selection from the previous step. + + + {{% accordion id="yes" label="Public IP for Worker Nodes—Yes" %}} +If you choose to assign a public IP address to your cluster's worker nodes, you have the option of choosing between a VPC that's automatically generated by Rancher (i.e., **Standard: Rancher generated VPC and Subnet**), or a VPC that you're already created with AWS (i.e., **Custom: Choose from your existing VPC and Subnets**). Choose the option that best fits your use case. + +1. Choose a **VPC and Subnet** option. + + Option | Description + -------|------------ + Standard: Rancher generated VPC and Subnet | While provisioning your cluster, Rancher generates a new VPC and Subnet. + Custom: Choose from your exiting VPC and Subnets | While provisioning your cluster, Rancher configures your nodes to use a VPC and Subnet that you've already created in AWS. If you choose this option, complete the remaining steps below. + +1. If you're using **Custom: Choose from your existing VPC and Subnets**: + + (If you're using **Standard**, skip to [step 10](#security-group)) + + 1. Make sure **Custom: Choose from your existing VPC and Subnets** is selected. + + 1. From the drop-down that displays, choose a VPC. + + 1. Click **Next: Select Subnets**. Then choose one of the **Subnets** that displays. + + 1. Click **Next: Select Security Group**. + {{% /accordion %}} + {{% accordion id="no" label="Public IP for Worker Nodes—No: Private IPs only" %}} +If you chose this option, you must also choose a **VPC & Subnet** that allow your instances to access the internet. This access is required so that your worker nodes can connect to the Kubernetes control plane. Follow the steps below. + +>**Tip:** When using only private IP addresses, you can provide your nodes internet access by creating a VPC constructed with two subnets, a private set and a public set. The private set should have its route tables configured to point toward a NAT in the public set. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html). + + 1. From the drop-down that displays, choose a VPC. + + 1. Click **Next: Select Subnets**. Then choose one of the **Subnets** that displays. + + 1. Click **Next: Select Security Group**. + {{% /accordion %}} + +1. Choose a **Security Group**. + +1. Click **Select Instance Options**, and then edit the node options available. + + Option | Description + -------|------------ + Instance Type | placeholder + Custom AMI Override | placeholder + Minimum ASG Size | placeholder + Maximum ASG Size | placeholder + +1. Click **Create**. {{< result_create-cluster >}} -# Note on Public IP for Worker Notes - -If you specify `Public IP for Worker Nodes` as `false`, you must also specify a VPC with subnets that allow your instances to access the internet. This access is required so that your worker nodes can connect to the Kubernetes control plane. - -One possible configuration solution is a VPC constructed with two subnets, a private set and a public set. The private set should have its route tables configured to point toward a NAT in the public set. For more information on routing traffic from private subnets, please see the [official AWS documentation](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html). - From 9b3cee4da5b4d762b5940acf8e0c5d3cda4a7c1c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 19 Oct 2018 16:26:44 -0700 Subject: [PATCH 5/7] rewrite for amazon eks cluster provisioning. --- .../hosted-kubernetes-clusters/eks/_index.md | 55 +++++++++---------- 1 file changed, 27 insertions(+), 28 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md index 7193162ff62..5534f6c5f0b 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks/_index.md @@ -22,33 +22,23 @@ Make sure that the account you will be using to create the EKS cluster has the a ## 2. Create Access Key and Secret Key -Use AWS to create an access key and client secret. +Use AWS to create an access key and client secret for the IAM account used in [1. Give Appropriate Permissions](#1-give-appropriate-permissions). -1. In the AWS Console, go to the **IAM** service. - -2. Select **Users**. - -3. Find the user you wish to create the EKS cluster with. Select the user. - -4. Click **Security Credentials**. - -5. Click **Create access key**. - -6. Record the **Access key ID** and **Secret access key**. You will need to use these in Rancher to create your EKS cluster. +For instructions on how to create these keys, see the AWS documentation [Managing Access Keys: To create, modify, or delete a user's access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html#Using_CreateAccessKey). ## 3. Create the EKS Cluster -Use {{< product >}} to set up and configure your Kubernetes cluster. +Use Rancher to set up and configure your Kubernetes cluster. 1. From the **Clusters** page, click **Add Cluster**. -2. Choose **Amazon EKS**. +1. Choose **Amazon EKS**. -3. Enter a **Cluster Name**. +1. Enter a **Cluster Name**. -4. {{< step_create-cluster_member-roles >}} +1. {{< step_create-cluster_member-roles >}} -1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field. +1. Configure **Account Access** for the EKS cluster. Complete each drop-down and field using the information obtained in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | Setting | Description | | ---------- | -------------------------------------------------------------------------------------------------------------------- | @@ -56,12 +46,12 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. | Access Key | Enter the access key that you created in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | | Secret Key | Enter the secret key that you created in [2. Create Access Key and Secret Key](#2-create-access-key-and-secret-key). | -1. Click **Next: Select Service Role**. Then choose a service role. +1. Click **Next: Select Service Role**. Then choose a [service role](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html). Service Role | Description -------------|--------------------------- - Standard: Rancher generated service role | placeholder - Custom: Choose from your existing service roles | placeholder + Standard: Rancher generated service role | If you choose this role, Rancher automatically adds a service role for use with the cluster. + Custom: Choose from your existing service roles | If you choose this role, Rancher lets you choose from service roles that you're already created within AWS. For more information on creating a custom service role in AWS, see the [Amazon documentation](https://docs.aws.amazon.com/IAM/latest/UserGuide/using-service-linked-roles.html#create-service-linked-role). 1. Click **Next: Select VPC and Subnet**. @@ -74,6 +64,10 @@ Use {{< product >}} to set up and configure your Kubernetes cluster. 1. Now choose a **VPC & Subnet**. Follow one of the sets of instructions below based on your selection from the previous step. + Amazon Documentation: + + - [What Is Amazon VPC?](https://docs.aws.amazon.com/vpc/latest/userguide/what-is-amazon-vpc.html) + - [VPCs and Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html) {{% accordion id="yes" label="Public IP for Worker Nodes—Yes" %}} If you choose to assign a public IP address to your cluster's worker nodes, you have the option of choosing between a VPC that's automatically generated by Rancher (i.e., **Standard: Rancher generated VPC and Subnet**), or a VPC that you're already created with AWS (i.e., **Custom: Choose from your existing VPC and Subnets**). Choose the option that best fits your use case. @@ -83,11 +77,11 @@ If you choose to assign a public IP address to your cluster's worker nodes, you Option | Description -------|------------ Standard: Rancher generated VPC and Subnet | While provisioning your cluster, Rancher generates a new VPC and Subnet. - Custom: Choose from your exiting VPC and Subnets | While provisioning your cluster, Rancher configures your nodes to use a VPC and Subnet that you've already created in AWS. If you choose this option, complete the remaining steps below. + Custom: Choose from your exiting VPC and Subnets | While provisioning your cluster, Rancher configures your nodes to use a VPC and Subnet that you've already [created in AWS](https://docs.aws.amazon.com/vpc/latest/userguide/getting-started-ipv4.html). If you choose this option, complete the remaining steps below. 1. If you're using **Custom: Choose from your existing VPC and Subnets**: - (If you're using **Standard**, skip to [step 10](#security-group)) + (If you're using **Standard**, skip to [step 11](#select-instance-options)) 1. Make sure **Custom: Choose from your existing VPC and Subnets** is selected. @@ -109,16 +103,21 @@ If you chose this option, you must also choose a **VPC & Subnet** that allow you 1. Click **Next: Select Security Group**. {{% /accordion %}} -1. Choose a **Security Group**. +1. Choose a **Security Group**. See the documentation below on how to create one. -1. Click **Select Instance Options**, and then edit the node options available. + Amazon Documentation: + + - [Security Groups for Your VPC](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html) + - [Create a Security Group](https://docs.aws.amazon.com/vpc/latest/userguide/getting-started-ipv4.html#getting-started-create-security-group) + +1. Click **Select Instance Options**, and then edit the node options available. Option | Description -------|------------ - Instance Type | placeholder - Custom AMI Override | placeholder - Minimum ASG Size | placeholder - Maximum ASG Size | placeholder + Instance Type | Choose the [hardware specs](https://aws.amazon.com/ec2/instance-types/) for the instance you're provisioning. + Custom AMI Override | If you want to use a custom [Amazon Machine Image](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html#creating-an-ami) (AMI), specify it here. + Minimum ASG Size | The minimum number of instances that your cluster will scale to during low traffic, as controlled by [Amazon Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html). + Maximum ASG Size | The maximum number of instances that your cluster will scale to during high traffic, as controlled by [Amazon Auto Scaling](https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html). 1. Click **Create**. From 28daf4dc1645db495f1861eea04ab6f730dd9cb1 Mon Sep 17 00:00:00 2001 From: Sebastiaan van Steenis Date: Wed, 17 Oct 2018 16:35:16 +0200 Subject: [PATCH 6/7] Cleanup helm/tiller + added verification steps for helm/tiller --- .../rancher/v2.x/en/installation/ha/helm-init/_index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/rancher/v2.x/en/installation/ha/helm-init/_index.md b/content/rancher/v2.x/en/installation/ha/helm-init/_index.md index e3e9e566a66..ca03a9e1f1c 100644 --- a/content/rancher/v2.x/en/installation/ha/helm-init/_index.md +++ b/content/rancher/v2.x/en/installation/ha/helm-init/_index.md @@ -3,7 +3,11 @@ title: 3 - Initialize Helm (Install tiller) weight: 195 --- +<<<<<<< HEAD Helm is the package management tool of choice for Kubernetes. Helm charts provide templating syntax for Kubernetes YAML manifest documents. With Helm, we can create configurable deployments instead of just using static files. For more information about creating your own repository of deployments, check out the docs at [https://helm.sh/](https://helm.sh/). To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster. +======= +Helm is the package management tool of choice for Kubernetes. Helm "charts" provide templating syntax for Kubernetes YAML manifest documents. With Helm we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at [https://helm.sh/](https://helm.sh/). To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster. +>>>>>>> Cleanup helm/tiller + added verification steps for helm/tiller > **Note:** For systems without direct internet access see [Helm - Air Gap]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/#helm) for install details. @@ -12,7 +16,11 @@ Helm is the package management tool of choice for Kubernetes. Helm charts provid Helm installs the `tiller` service on your cluster to manage charts. Since RKE enables RBAC by default we will need to use `kubectl` to create a `serviceaccount` and `clusterrolebinding` so `tiller` has permission to deploy to the cluster. * Create the `ServiceAccount` in the `kube-system` namespace. +<<<<<<< HEAD * Create the `ClusterRoleBinding` to give the `tiller` service account access to the cluster. +======= +* Create the `ClusterRoleBinding` to give the `tiller` account access to the cluster. +>>>>>>> Cleanup helm/tiller + added verification steps for helm/tiller * Finally use `helm` to install the `tiller` service ```plain From b6c060861db986fe5ceb4857f81c927c2c5c45ee Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Thu, 18 Oct 2018 13:38:31 -0700 Subject: [PATCH 7/7] hiding upgrade for rke-add-on install --- .../rancher/v2.x/en/installation/ha/helm-init/_index.md | 9 +-------- content/rancher/v2.x/en/upgrades/upgrades/_index.md | 2 +- 2 files changed, 2 insertions(+), 9 deletions(-) diff --git a/content/rancher/v2.x/en/installation/ha/helm-init/_index.md b/content/rancher/v2.x/en/installation/ha/helm-init/_index.md index ca03a9e1f1c..02e45bb69d2 100644 --- a/content/rancher/v2.x/en/installation/ha/helm-init/_index.md +++ b/content/rancher/v2.x/en/installation/ha/helm-init/_index.md @@ -3,11 +3,8 @@ title: 3 - Initialize Helm (Install tiller) weight: 195 --- -<<<<<<< HEAD -Helm is the package management tool of choice for Kubernetes. Helm charts provide templating syntax for Kubernetes YAML manifest documents. With Helm, we can create configurable deployments instead of just using static files. For more information about creating your own repository of deployments, check out the docs at [https://helm.sh/](https://helm.sh/). To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster. -======= + Helm is the package management tool of choice for Kubernetes. Helm "charts" provide templating syntax for Kubernetes YAML manifest documents. With Helm we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at [https://helm.sh/](https://helm.sh/). To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster. ->>>>>>> Cleanup helm/tiller + added verification steps for helm/tiller > **Note:** For systems without direct internet access see [Helm - Air Gap]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/#helm) for install details. @@ -16,11 +13,7 @@ Helm is the package management tool of choice for Kubernetes. Helm "charts" prov Helm installs the `tiller` service on your cluster to manage charts. Since RKE enables RBAC by default we will need to use `kubectl` to create a `serviceaccount` and `clusterrolebinding` so `tiller` has permission to deploy to the cluster. * Create the `ServiceAccount` in the `kube-system` namespace. -<<<<<<< HEAD -* Create the `ClusterRoleBinding` to give the `tiller` service account access to the cluster. -======= * Create the `ClusterRoleBinding` to give the `tiller` account access to the cluster. ->>>>>>> Cleanup helm/tiller + added verification steps for helm/tiller * Finally use `helm` to install the `tiller` service ```plain diff --git a/content/rancher/v2.x/en/upgrades/upgrades/_index.md b/content/rancher/v2.x/en/upgrades/upgrades/_index.md index 1c24939f8b0..109c96c1bfa 100644 --- a/content/rancher/v2.x/en/upgrades/upgrades/_index.md +++ b/content/rancher/v2.x/en/upgrades/upgrades/_index.md @@ -19,4 +19,4 @@ This section contains information about how to upgrade your Rancher server to a > >Please use the Rancher helm chart to install HA Rancher. For details, see the [HA Install - Installation Outline]({{< baseurl >}}/rancher/v2.x/en/installation/ha/#installation-outline). > ->If you are currently using the RKE add-on install method, see [Migrating from a RKE add-on install]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using a Helm chart. +>If you are currently using the RKE add-on install method, see [Migrating from a RKE add-on install]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/migrating-from-rke-add-on/) for details on how to move to using the helm chart.