mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
cleaning up old files in global config section
This commit is contained in:
@@ -2,7 +2,8 @@
|
||||
title: Admin Settings
|
||||
weight: 1100
|
||||
aliases:
|
||||
- /rancher/v2.x/en/concepts/global-configuration
|
||||
- /rancher/v2.x/en/concepts/global-configuration/
|
||||
- /rancher/v2.x/en/tasks/global-configuration/
|
||||
---
|
||||
|
||||
After installing Rancher 2.0, you should
|
||||
@@ -11,4 +12,4 @@ After installing Rancher 2.0, you should
|
||||
|
||||
2. Set up external user authentication and permissions so that your organization can log into Rancher.
|
||||
|
||||
After making these initial configurations, you might also want to configure one or more _pod security policies_, which are sets of conditions that your pods must meet for Kubernetes to allow them to run.
|
||||
After making these initial configurations, you might also want to configure one or more _pod security policies_, which are sets of conditions that your pods must meet for Kubernetes to allow them to run.
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
---
|
||||
title: Catalogs and Charts
|
||||
title: Launching Catalog Applications
|
||||
weight: 4010
|
||||
---
|
||||
|
||||
@@ -1,5 +0,0 @@
|
||||
---
|
||||
title: Global Configuration
|
||||
weight: 3025
|
||||
---
|
||||
This section contains step-by-step instruction for configuring Rancher to work in your environment.
|
||||
@@ -1,27 +0,0 @@
|
||||
---
|
||||
title: Node Drivers
|
||||
weight: 150
|
||||
---
|
||||
|
||||
>**Prerequisites:** To create, edit, or delete drivers, you need _one_ of the following permissions:
|
||||
>
|
||||
>- [Administrator Global Permissions]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#global-permissions)
|
||||
>- [Custom Global Permissions]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#custom-global-permissions) with the [Manage Node Drivers]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/#global-permissions-reference) role assigned.
|
||||
|
||||
## Adding Custom Node Drivers
|
||||
|
||||
If you create a cluster using a cloud provider that {{< product >}} doesn't support out-of-the-box, you may need to add the provider's drivers (or create them yourself) so that your nodes function properly.
|
||||
|
||||
1. From the **Global** view, select **Node Drivers** from the main menu.
|
||||
|
||||
2. Click **Add Node Driver**.
|
||||
|
||||
3. Complete the **Add Node Driver** form. Then click **Create**.
|
||||
|
||||
## Activating Node Drivers
|
||||
|
||||
Using the **Custom** option, you can create a cluster using virtually any cloud provider. However, by default, {{< product >}} only activates drivers for the most popular cloud providers. If you want to use another provider, you'll have to activate their drivers.
|
||||
|
||||
1. From the **Global** view, select **Node Drivers** from the main menu.
|
||||
|
||||
2. Select the inactive drivers that you want to use. Then click **Add Node Driver**.
|
||||
@@ -1,7 +0,0 @@
|
||||
---
|
||||
title: Password Reset
|
||||
weight: 75
|
||||
draft: true
|
||||
---
|
||||
|
||||
Content here.
|
||||
Reference in New Issue
Block a user