Remove unsupported front matter fields

2026-09-28 05:59:03 +00:00 · 2022-09-23 10:11:24 -07:00
parent 5b064e6548
commit c390289797
1553 changed files with 871 additions and 4500 deletions
@@ -1,10 +1,5 @@
 ---
 title: API Keys
-weight: 7005
-aliases:
-  - /rancher/v2.5/en/concepts/api-keys/
-  - /rancher/v2.5/en/tasks/user-settings/api-keys/
-  - /rancher/v2.x/en/user-settings/api-keys/
 ---

 ## API Keys and User Authentication
@@ -31,7 +26,7 @@ API Keys are composed of four components:
    The API key won't be valid after expiration. Shorter expiration periods are more secure.

    Expiration period will be bound by `v3/settings/auth-token-max-ttl-minutes`. If it exceeds the max-ttl, API key will be created with max-ttl as the expiration period.
-    
+
    A scope will limit the API key so that it will only work against the Kubernetes API of the specified cluster. If the cluster is configured with an Authorized Cluster Endpoint, you will be able to use a scoped token directly against the cluster's API without proxying through the Rancher server. See [Authorized Cluster Endpoints](../../pages-for-subheaders/rancher-manager-architecture.md#4-authorized-cluster-endpoint) for more information.

 4. Click **Create**.
@@ -1,8 +1,5 @@
 ---
 title: Managing Cloud Credentials
-weight: 7011
-aliases:
-  - /rancher/v2.x/en/user-settings/cloud-credentials/
 ---

 When you create a cluster [hosted by an infrastructure provider](../../pages-for-subheaders/use-new-nodes-in-an-infra-provider.md), [node templates](../../pages-for-subheaders/use-new-nodes-in-an-infra-provider.md#node-templates) are used to provision the cluster nodes. These templates use Docker Machine configuration options to define an operating system image and settings/parameters for the node.
@@ -31,7 +28,7 @@ All cloud credentials are bound to the user profile of who created it. They **ca

 ## Updating a Cloud Credential

-When access credentials are changed or compromised, updating a cloud credential allows you to rotate those credentials while keeping the same node template.  
+When access credentials are changed or compromised, updating a cloud credential allows you to rotate those credentials while keeping the same node template.

 1. From your user settings, select **User Avatar > Cloud Credentials**.
 1. Choose the cloud credential you want to edit and click the **&#8942; > Edit**.
@@ -1,8 +1,5 @@
 ---
 title: Managing Node Templates
-weight: 7010
-aliases:
-  - /rancher/v2.x/en/user-settings/node-templates/
 ---

 When you provision a cluster [hosted by an infrastructure provider](../../pages-for-subheaders/use-new-nodes-in-an-infra-provider.md), [node templates](../../pages-for-subheaders/use-new-nodes-in-an-infra-provider.md#node-templates) are used to provision the cluster nodes. These templates use Docker Machine configuration options to define an operating system image and settings/parameters for the node. You can create node templates in two contexts:
@@ -26,7 +23,7 @@ When you create a node template, it is bound to your user profile. Node template
 1. Choose the node template that you want to edit and click the **&#8942; > Edit**.

    :::note
-    
+
    As of v2.2.0, the default `active` [node drivers](../../how-to-guides/advanced-user-guides/authentication-permissions-and-global-configuration/about-provisioning-drivers/manage-node-drivers.md) and any node driver, that has fields marked as `password`, are required to use [cloud credentials](../../pages-for-subheaders/use-new-nodes-in-an-infra-provider.md#cloud-credentials). If you have upgraded to v2.2.0, existing node templates will continue to work with the previous account access  information, but when you edit the node template, you will be required to create a cloud credential and the node template will start using it.
    :::

@@ -1,8 +1,5 @@
 ---
 title: User Preferences
-weight: 7012
-aliases:
-  - /rancher/v2.x/en/user-settings/preferences/
 ---

 import Tabs from '@theme/Tabs';