public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

adding PR feedback

Browse Source
This commit is contained in:
Mark Bishop
2018-04-19 17:07:10 -07:00
committed by Denise Schannon
parent 5ce6c60152
commit 6639c041f1
4 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/concepts/users-and-roles.md
+1 -1
View File
@@ -1,6 +1,6 @@
# Users and Roles
Every user in {{< product >}} is assigned a _role_, which is a set of permissions that determine what Kubenetes API endpoints that the user can access. Let's use this metaphor: a user account is like getting access to an entire office building; however, the user's role determine what rooms the user can access within the building.
Every user in {{< product >}} is assigned a _role_, which is a set of permissions that determine what Kubernetes API endpoints that the user can access. Let's use this metaphor: a user account is like getting access to an entire office building; however, the user's role determine what rooms the user can access within the building.
Within {{< product >}} there are two types of user roles:
content/rancher/installation/requirements.md
+6 -3
View File
@@ -2,15 +2,18 @@
## Operating System Requirements
- Operating System: Ubuntu 16.04 (64-bit)
- Ubuntu 16.04 (64-bit)
- Red Hat Enterprise Linux 7.5 (64-bit)
- RancherOS
## Hardware Requirements
- Memory: 4GB
## Software Requirements
- Docker
## Software requirements
- Software: Docker
<a name="node-requirements"></a>**Supported Versions:**
content/rancher/tasks/clusters/creating-a-cluster/create-cluster-custom.md
+3 -1
View File
@@ -56,7 +56,9 @@ Use {{< product >}} to clone your Linux host and configure them as Kubernetes no
>
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).
8. **Optional**: Use **Labels** to add metadata so that you can find them later.
8. **Optional**: Add **Labels** to your cluster nodes to help schedule workloads later.
[Kubernetes Documentation: Labels](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/)
9. Copy the command displayed on screen to your clipboard.
content/rancher/tasks/global-configuration/authentication/configure-user-authentication.md
+3 -3
View File
@@ -1,12 +1,12 @@
# Configuring User Authentication
You have three options for user authentication in {{< product >}}:
You have three options for user authentication in {{< product >}}. We recommend using an external authentication method (i.e. Active Directory or GitHub) rather than local authentication. External authentication reduces upkeep of your users.
- **Active Directory**: Enterprises can use Active Directory (AD) for authentication, allowing users to sign in using their corporate credentials.
- **GitHub**: Open source projects or organizations that use GitHub for source control may prefer that users sign in using their GitHub accounts.
- **Basic Authentication**: If you don't want to use external authentication, you can always add users directly to {{< product >}}. We recommend using external authentication over basic authentication.
- **Local Authentication**: If you don't want to use external authentication, you can always add users directly to {{< product >}}. We recommend using external authentication over local authentication.
## Configure an Authentication Method
@@ -80,7 +80,7 @@ You have three options for user authentication in {{< product >}}:
- You are signed into Rancher with your GitHub account.
- Your GitHub account is added to Rancher as an administrator.
### To Configure Basic Authentication
### To Configure Local Authentication
1. From the **Global** view, select **Users** from the main menu.