Revert 2.6 nav changes applied to 2.5 files (#3541)

2026-05-19 11:25:15 +00:00 · 2021-09-23 09:17:52 -07:00
parent 2e4c034652
commit 366c751736
11 changed files with 52 additions and 70 deletions
@@ -115,9 +115,7 @@ To give role-based access to your service principal,

 Use Rancher to set up and configure your Kubernetes cluster.

-1. In the upper left corner, click **≡ > Cluster Management.**
-
-1. From the **Clusters** page, click **Create**.
+1. From the **Clusters** page, click **Add Cluster**.

 1. Choose **Azure AKS**.

@@ -125,7 +123,8 @@ Use Rancher to set up and configure your Kubernetes cluster.

 1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.

-1. Use your subscription ID, client ID, and client secret to give your cluster access to AKS. If you don't have all of that information, you can retrieve it using these instructions:
+1. Use your subscription ID, tenant ID, client ID, and client secret to give your cluster access to AKS. If you don't have all of that information, you can retrieve it using these instructions:
+  - **Tenant ID:** To get the Tenant ID, you can go to the Azure Portal, then click **Azure Active Directory**, then click **Properties** and find the **Tenant ID** field.
  - **Client ID:** To get the Client ID, you can go to the Azure Portal, then click **Azure Active Directory**, then click **Enterprise applications.** Click **All applications.** Select your application, click **Properties,** and copy the application ID.
  - **Client secret:** If you didn't copy the client secret when creating the service principal, you can get a new one if you go to the app registration detail page, then click **Certificates & secrets**, then click **New client secret.** 
  - **Subscription ID:** You can get the subscription ID is available in the portal from **All services > Subscriptions.**
@@ -50,9 +50,7 @@ For more detailed information on IAM policies for EKS, refer to the official [do

 Use Rancher to set up and configure your Kubernetes cluster.

-1. In the upper left corner, click **≡ > Cluster Management.**
-
-1. From the **Clusters** page, click **Create**.
+1. From the **Clusters** page, click **Add Cluster**.

 1. Choose **Amazon EKS**.

@@ -64,9 +64,8 @@ To get the project ID of an existing project, refer to the Google cloud document
 ### 2. Create the GKE Cluster
 Use Rancher to set up and configure your Kubernetes cluster.

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. From the **Clusters** page, click **Create**.
-1. Click **Google GKE**.
+1. From the **Clusters** page, click **Add Cluster**.
+1. Under **With a hosted Kubernetes provider,** click **Google GKE**.
 1. Enter a **Cluster Name**.
 1. Optional: Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.
 1. Optional: Add Kubernetes [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) or [annotations](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/) to the cluster.
@@ -38,9 +38,8 @@ If you are registering a K3s cluster, make sure the `cluster.yml` is readable. I

 # Registering a Cluster

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. From the **Clusters** page, click **Import Existing**.
-2. Click the type of Kubernetes cluster you want to import.
+1. From the **Clusters** page, click **Add Cluster**.
+2. Under **Register an existing Kubernetes cluster**, click the type of Kubernetes cluster you want to register.
 3. Enter a **Cluster Name**.
 4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.
 5. For Rancher v2.5.6+, use **Agent Environment Variables** under **Cluster Options** to set environment variables for [rancher cluster agent]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/rancher-agents/). The environment variables can be set using key value pairs. If rancher agent requires use of proxy to communicate with Rancher server, `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables can be set using agent environment variables.
@@ -25,10 +25,8 @@ The Cloud Provider Interface (CPI) should be installed first before installing t

 ### 1. Create a vSphere cluster

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. From the **Clusters** page, click **Create.**
-1. Click **VMWare vSphere.**
-1. Under **Cluster Options** in the **Cloud Provider** section, select **External (Out-of-tree)**. This sets the cloud provider option on the Kubernetes cluster to `external` which sets your Kubernetes cluster up to be configured with an out-of-tree cloud provider. 
+1. On the Clusters page, click on **Add Cluster** and select the **vSphere** option or **Existing Nodes** option.
+1. Under **Cluster Options** in the **Cloud Provider** section, select **External (Out-of-tree)**. This sets the cloud provider option on the Kubernetes cluster to `external` which sets your Kubernetes cluster up to be configured with an out-of-tree cloud provider.
 1. Finish creating your cluster.

 ### 2. Install the CPI plugin
@@ -45,40 +45,38 @@ Provision the host according to the [installation requirements]({{<baseurl>}}/ra

 Clusters won't begin provisioning until all three node roles (worker, etcd and controlplane) are present.

-1. In the upper left corner, click **≡ > Cluster Management.**
+1. From the **Clusters** page, click **Add Cluster**.

-1. From the **Clusters** page, click **Create.**
+2. Choose **Custom**.

-1. Click **Custom.**
+3. Enter a **Cluster Name**.

-1. Enter a **Cluster Name**.
+4. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.

-1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.
-
-1. Use **Cluster Options** to choose the version of Kubernetes, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options.**
+5. Use **Cluster Options** to choose the version of Kubernetes, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options.**

    >**Using Windows nodes as Kubernetes workers?**
    >
    >- See [Enable the Windows Support Option]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/windows-clusters/).
    >- The only Network Provider available for clusters with Windows support is Flannel.
-1.	<a id="step-6"></a>Click **Next**.
+6.	<a id="step-6"></a>Click **Next**.

-1.	From **Node Role**, choose the roles that you want filled by a cluster node. You must provision at least one node for each role: `etcd`, `worker`, and `control plane`. All three roles are required for a custom cluster to finish provisioning. For more information on roles, see [this section.]({{<baseurl>}}/rancher/v2.5/en/overview/concepts/#roles-for-nodes-in-kubernetes-clusters)
+7.	From **Node Role**, choose the roles that you want filled by a cluster node. You must provision at least one node for each role: `etcd`, `worker`, and `control plane`. All three roles are required for a custom cluster to finish provisioning. For more information on roles, see [this section.]({{<baseurl>}}/rancher/v2.5/en/overview/concepts/#roles-for-nodes-in-kubernetes-clusters)

 	>**Notes:**
 	>
    >- Using Windows nodes as Kubernetes workers? See [this section]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/windows-clusters/).
 	>- Bare-Metal Server Reminder: If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers).

-1.	<a id="step-8"></a>**Optional**: Click **[Show advanced options]({{<baseurl>}}/rancher/v2.5/en/admin-settings/agent-options/)** to specify IP address(es) to use when registering the node, override the hostname of the node, or to add [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) or [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) to the node.
+8.	<a id="step-8"></a>**Optional**: Click **[Show advanced options]({{<baseurl>}}/rancher/v2.5/en/admin-settings/agent-options/)** to specify IP address(es) to use when registering the node, override the hostname of the node, or to add [labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) or [taints](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/) to the node.

-1. Copy the command displayed on screen to your clipboard.
+9. Copy the command displayed on screen to your clipboard.

-1. Log in to your Linux host using your preferred shell, such as PuTTy or a remote Terminal connection. Run the command copied to your clipboard.
+10. Log in to your Linux host using your preferred shell, such as PuTTy or a remote Terminal connection. Run the command copied to your clipboard.

 	>**Note:** Repeat steps 7-10 if you want to dedicate specific hosts to specific node roles. Repeat the steps as many times as needed.

-1. When you finish running the command(s) on your Linux host(s), click **Done**.
+11. When you finish running the command(s) on your Linux host(s), click **Done**.

 **Result:** 

@@ -101,8 +101,8 @@ When you create the node pool, you can specify the amount of time in minutes tha

 You can also enable node auto-replace after the cluster is created with the following steps:

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the list of clusters, go to the cluster where you want to enable node auto-replace. Click the vertical &#8942; **(…)**, and click **Edit Config.**
+1. From the Global view, click the Clusters tab.
+1. Go to the cluster where you want to enable node auto-replace, click the vertical &#8942; **(…)**, and click **Edit.**
 1. In the **Node Pools** section, go to the node pool where you want to enable node auto-replace. In the **Recreate Unreachable After** field, enter the number of minutes that Rancher should wait for a node to respond before replacing the node.
 1. Click **Save.**

@@ -112,8 +112,8 @@ You can also enable node auto-replace after the cluster is created with the foll

 You can disable node auto-replace from the Rancher UI with the following steps:

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the list of clusters, go to the cluster where you want to enable node auto-replace. Click the vertical &#8942; **(…)**, and click **Edit Config.**
+1. From the Global view, click the Clusters tab.
+1. Go to the cluster where you want to enable node auto-replace, click the vertical &#8942; **(…)**, and click **Edit.**
 1. In the **Node Pools** section, go to the node pool where you want to enable node auto-replace. In the **Recreate Unreachable After** field, enter 0.
 1. Click **Save.**

@@ -46,11 +46,10 @@ The creation of this service principal returns three pieces of identification in
 
 ### 1. Create your cloud credentials

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Cloud Credentials.**
-1. Click **Create.**
-1. Click **Azure.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Cloud Credentials.**
+1. Click **Add Cloud Credential.**
 1. Enter a name for the cloud credential.
+1. In the **Cloud Credential Type** field, select **Azure**.
 1. Enter your Azure credentials.
 1. Click **Create.**

@@ -60,8 +59,7 @@ The creation of this service principal returns three pieces of identification in

 Creating a [node template]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for Azure will allow Rancher to provision new nodes in Azure. Node templates can be reused for other clusters.

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Node Templates.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Node Templates.**
 1. Click **Add Template.**
 1. Fill out a node template for Azure. For help filling out the form, refer to [Azure Node Template Configuration.](./azure-node-template-config)

@@ -71,8 +69,7 @@ Use Rancher to create a Kubernetes cluster in Azure.

 Clusters won't begin provisioning until all three node roles (worker, etcd and controlplane) are present.

-1. In the upper left corner, click **≡ > Cluster Management**.
-1. Click **Create**.
+1. From the **Clusters** page, click **Add Cluster**.
 1. Choose **Azure**.
 1. Enter a **Cluster Name**.
 1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.
@@ -19,11 +19,10 @@ Then you will create a DigitalOcean cluster in Rancher, and when configuring the

 ### 1. Create your cloud credentials

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Cloud Credentials.**
-1. Click **Create.**
-1. Click **Digital Ocean.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Cloud Credentials.**
+1. Click **Add Cloud Credential.**
 1. Enter a name for the cloud credential.
+1. In the **Cloud Credential Type** field, select **DigitalOcean**.
 1. Enter your Digital Ocean credentials.
 1. Click **Create.**

@@ -33,16 +32,15 @@ Then you will create a DigitalOcean cluster in Rancher, and when configuring the

 Creating a [node template]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for DigitalOcean will allow Rancher to provision new nodes in DigitalOcean. Node templates can be reused for other clusters.

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Node Templates.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Node Templates.**
+1. Click **Add Template.**
 1. Fill out a node template for DigitalOcean. For help filling out the form, refer to [DigitalOcean Node Template Configuration.](./do-node-template-config)

 ### 3. Create a cluster with node pools using the node template

 Clusters won't begin provisioning until all three node roles (worker, etcd and controlplane) are present.

-1. In the upper left corner, click **≡ > Cluster Management**.
-1. Click **Create**.
+1. From the **Clusters** page, click **Add Cluster**.
 1. Choose **DigitalOcean**.
 1. Enter a **Cluster Name**.
 1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.
@@ -31,13 +31,12 @@ The steps to create a cluster differ based on your Rancher version.

 ### 1. Create your cloud credentials

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Cloud Credentials.**
-1. Click **Create.**
-1. Click **Amazon.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Cloud Credentials.**
+1. Click **Add Cloud Credential.**
 1. Enter a name for the cloud credential.
+1. In the **Cloud Credential Type** field, select **Amazon.**
+1. In the **Region** field, select the AWS region where your cluster nodes will be located.
 1. Enter your AWS EC2 **Access Key** and **Secret Key.**
-1. In the **Default Region** field, select the AWS region where your cluster nodes will be located.
 1. Click **Create.**

 **Result:** You have created the cloud credentials that will be used to provision nodes in your cluster. You can reuse these credentials for other node templates, or in other clusters. 
@@ -46,8 +45,8 @@ The steps to create a cluster differ based on your Rancher version.

 Creating a [node template]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for EC2 will allow Rancher to provision new nodes in EC2. Node templates can be reused for other clusters.

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Node Templates.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Node Templates.**
+1. Click **Add Template.**
 1. Fill out a node template for EC2. For help filling out the form, refer to [EC2 Node Template Configuration.](./ec2-node-template-config)

 ### 3. Create a cluster with node pools using the node template
@@ -56,8 +55,7 @@ Add one or more node pools to your cluster. For more information about node pool

 Clusters won't begin provisioning until all three node roles (worker, etcd and controlplane) are present.

-1. In the upper left corner, click **≡ > Cluster Management**.
-1. Click **Create**.
+1. From the **Clusters** page, click **Add Cluster**.
 1. Choose **Amazon EC2**.
 1. Enter a **Cluster Name**.
 1. Create a node pool for each Kubernetes role. For each node pool, choose a node template that you created. For more information about node pools, including best practices for assigning Kubernetes roles to them, see [this section.]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools) 
@@ -75,7 +73,6 @@ You can access your cluster after its state is updated to **Active.**

 - `Default`, containing the `default` namespace
 - `System`, containing the `cattle-system`, `ingress-nginx`, `kube-public`, and `kube-system` namespaces
-
 ### Optional Next Steps

 After creating your cluster, you can access it through the Rancher UI. As a best practice, we recommend setting up these alternate ways of accessing your cluster:
@@ -58,10 +58,10 @@ The a vSphere cluster is created in Rancher depends on the Rancher version.

 ### 1. Create your cloud credentials

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Cloud Credentials.**
-1. Click **Create.**
-1. Click **VMware vSphere.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Cloud Credentials.**
+1. Click **Add Cloud Credential.**
+1. Enter a name for the cloud credential.
+1. In the **Cloud Credential Type** field, select **VMware vSphere**.
 1. Enter your vSphere credentials. For help, refer to **Account Access** in the [node template configuration reference.]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/)
 1. Click **Create.**

@@ -71,8 +71,8 @@ The a vSphere cluster is created in Rancher depends on the Rancher version.

 Creating a [node template]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) for vSphere will allow Rancher to provision new nodes in vSphere. Node templates can be reused for other clusters.

-1. In the upper left corner, click **≡ > Cluster Management.**
-1. In the left navigation menu, click **Node Templates.**
+1. In the Rancher UI, click the user profile button in the upper right corner, and click **Node Templates.**
+1. Click **Add Template.**
 1. Fill out a node template for vSphere. For help filling out the form, refer to the vSphere node template [configuration reference.]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/node-pools/vsphere/vsphere-node-template-config/).

 ### 3. Create a cluster with node pools using the node template
@@ -81,9 +81,8 @@ Use Rancher to create a Kubernetes cluster in vSphere.

 Clusters won't begin provisioning until all three node roles (worker, etcd and controlplane) are present.

-1. In the upper left corner, click **≡ > Cluster Management**.
-1. Click **Create**.
-1. Select the **VMware vSphere** infrastructure provider.
+1. Navigate to **Clusters** in the **Global** view.
+1. Click **Add Cluster** and select the **vSphere** infrastructure provider.
 1. Enter a **Cluster Name.**
 1. Use **Member Roles** to configure user authorization for the cluster. Click **Add Member** to add users that can access the cluster. Use the **Role** drop-down to set permissions for each user.
 1. Use **Cluster Options** to choose the version of Kubernetes that will be installed, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on **Show advanced options.** For help configuring the cluster, refer to the [RKE cluster configuration reference.]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/options)
@@ -109,4 +108,4 @@ After creating your cluster, you can access it through the Rancher UI. As a best

 - **Access your cluster with the kubectl CLI:** Follow [these steps]({{<baseurl>}}/rancher/v2.5/en/cluster-admin/cluster-access/kubectl/#accessing-clusters-with-kubectl-on-your-workstation) to access clusters with kubectl on your workstation. In this case, you will be authenticated through the Rancher server’s authentication proxy, then Rancher will connect you to the downstream cluster. This method lets you manage the cluster without the Rancher UI.
 - **Access your cluster with the kubectl CLI, using the authorized cluster endpoint:** Follow [these steps]({{<baseurl>}}/rancher/v2.5/en/cluster-admin/cluster-access/kubectl/#authenticating-directly-with-a-downstream-cluster) to access your cluster with kubectl directly, without authenticating through Rancher. We recommend setting up this alternative method to access your cluster so that in case you can’t connect to Rancher, you can still access the cluster.
- **Provision Storage:** For an example of how to provision storage in vSphere using Rancher, refer to [this section.]({{<baseurl>}}/rancher/v2.5/en/cluster-admin/volumes-and-storage/examples/vsphere) In order to dynamically provision storage in vSphere, the vSphere provider must be [enabled.]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere)
+- **Provision Storage:** For an example of how to provision storage in vSphere using Rancher, refer to [this section.]({{<baseurl>}}/rancher/v2.5/en/cluster-admin/volumes-and-storage/examples/vsphere) In order to dynamically provision storage in vSphere, the vSphere provider must be [enabled.]({{<baseurl>}}/rancher/v2.5/en/cluster-provisioning/rke-clusters/cloud-providers/vsphere)