adding folders and renaming files to correct the website browsing experience

2026-09-25 20:48:11 +00:00 · 2018-04-27 17:50:30 -07:00
parent e7add82746
commit 3182de13d0
48 changed files with 123 additions and 44 deletions
@@ -1,7 +1,7 @@
 ---
 title: Rancher 2.0 Documentation
 shortTitle: Rancher 2.0
-weight: 1
+weight: 5
 ---

 # Rancher 2.0 Documentation
@@ -1,5 +1,9 @@
 ---
-  title: Rancher Overview
+  title: Concepts
  weight: 2000
 ---
-# Rancher Overview
+# Concepts
+
+This section describes the different features in Rancher, the ideas behind them, and how they work.
+
+Choose a concept from the side-menu to start learning about Rancher!
@@ -1,5 +1,5 @@
 ---
-title: Rancher Architecture
+title: Architecture
 weight: 2050
 ---

@@ -2,3 +2,6 @@
 title: Logging
 weight: 2325
 ---
+# Logging
+
+Coming Soon!
@@ -1,5 +1,5 @@
 ---
-title: Rancher Overview
+title: Overview
 weight: 2025
 ---
 ## What's Rancher?
@@ -1,7 +1,6 @@
 ---
-  layout: single-docs
  title: Users and Roles
-  weight: 
+  weight:
 ---

 # Users and Roles
@@ -1,30 +0,0 @@
---
-title: Installation Objectives
-weight: 75
---
-# Installation Checklist
-
-1. [Installation Scenarios]({{< ref "installation-scenarios.md" >}})
-
-	You can install {{< product >}} and Kubernetes in virtually any network environement in a variety of configurations. Before you start installation, review the different use cases we've identified and choose the install solution best for you.
-
-2.	[Review {{< product >}} Server Requirements]({{< ref "requirements/_index.md" >}})
-
-	Depending on your install scenario, you'll have a different set of requirements you must meet. [Installation Scenarios]({{< ref "installation-scenarios.md" >}}) lists which set of requirements applies to you.
-
-3.	Provision Your Linux Host(s)
-
-	Provision your Linux host or cluster according to the [requirements]
-	({{< ref "requirements/_index.md" >}}).
-
-4.	[Install {{< product >}}]({{< ref "server-installation/_index.md" >}})
-
-	Complete the install procedure for your installation scenario.
-
-5.	[Configure Load Balancing]({{< ref "config-load-balancing.md" >}})
-
-	Configure a solution for balancing loads between the different nodes in your Kubernetes clusters.
-
-6.	[Configure SSL]({{< ref "config-ssl" >}})
-
-	Finally, you must configure your nodes for SSL communication. Obtain an SSL certificate and install it on your {{< product >}} nodes.
@@ -0,0 +1,8 @@
+---
+title: No-Internet Installation
+weight: 350
+draft: true
+---
+# No-Internet Installation
+
+Coming Soon!
@@ -1,5 +1,5 @@
 ---
-title: Rancher Server Installation
+title: Deploy Rancher
 weight: 225
 ---

@@ -1,5 +1,5 @@
 ---
-title: Rancher Server Tags
+title: Server Tags
 weight: 200
 ---

@@ -1,5 +1,5 @@
 ---
-title: Quick Start Guide
+title: Quick Start
 weight: 25
 ---

@@ -3,3 +3,5 @@ title: Tasks
 weight: 3000
 ---
 # Tasks
+
+This section of the docs provide step-by-step instructions on how to accomplish a goal within Rancher.
@@ -4,4 +4,4 @@ weight: 3200
 ---
 # Creating a Cluster

-let's create clusters!
+Rancher includes a variety of options for getting a Kubernetes cluster up and running using a single Linux node as a temple. Choose from one of the options below to get started!
@@ -0,0 +1,92 @@
+---
+title: Authentication
+weight: 3075
+---
+
+# Configuring User Authentication
+
+You have three options for user authentication in {{< product >}}:
+
+-	**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.
+
+## Configure an Authentication Method
+
+### To Configure Active Directory
+
+>**Prerequisites:** Create a service account in Active Directory with **read-only** access. {{< product >}} uses this account to verify group membership when a user makes a request using an API key.
+
+1.	From the **Global** view, select **Security > Authentication** from the main menu.
+
+2.	Select **Active Directory**.
+
+3.	Complete the **Configure an Active Directory server** form.
+
+	You may need to log in to your domain controller to find the information requested in the form.
+
+	>**Using TLS?**
+ 	>
+	Make sure you have an [LDAP certificate installed](placeholder.md).
+
+	>**User Search Base vs. Group Search Base**
+	>
+	>When configuring AD authentication, you must enter a search base for your users. This base allows Rancher to search for users that are in your Active Directory.
+		- If your users and groups are in the search base, complete only the User Search Base.
+		- If your groups are in a different search base, you can optionally complete the Group Search Base. This field is dedicated to searching groups, but is not required.
+
+4.	If your Active Directory deviates from the standard AD schema, complete the **Customize Schema** form to match it. Otherwise, skip this step.
+
+5.	Enter your AD username and password in **Test and enable authentication** to confirm that Rancher is configured to use AD authentication.
+
+### To Configure GitHub
+
+1.	From the **Global** view, select **Security > Authentication** from the main menu.
+
+2.	Select **GitHub**.
+
+3.	Follow the directions displayed to **Setup a GitHub Application**. Rancher redirects you to GitHub to complete registration.
+
+	>**What's an Authorization Callback URL?**
+	>
+	>The Authorization Callback URL is the URL where users to begin using your application (i.e. the splash screen).
+
+	>When you use external authentication, sign on authentication does not actually take place in your application. Instead, authentication takes place externally (in this case, GitHub). After this external authorization completes successfully, the Authorization Callback URL is the location that the user reenters your application.
+
+4. From GitHub, copy the **Client ID** and **Client Secret**. Paste them into {{< product >}}.
+
+	>**Where do I find the Client ID and Client Secret?**
+	>
+	>From GitHub, select Settings > Developer Settings > OAuth Apps. The Client ID and Client Secret are displayed prominently.
+
+5.	Click **Authenticate with GitHub**.
+
+6.	Use the **Site Access** options to configure the scope of user authorization.
+
+	-	**Allow any valid Users**
+
+		_Any_ GitHub user can access Rancher. We generally discourage use of this setting!
+
+	-	**Allow members of Clusters, Projects, plus Authorized Users and Organizations**
+
+		Any GitHub user or group added as a **Cluster Member** or **Project Member** can log in to Rancher. Additionally, any GitHub user or group you add to the **Authorized Users and Organizations** list may log in to Rancher.
+
+	-	**Restrict access to only Authorized Users and Organizations**
+
+		Only GitHub users or groups added to the Authorized Users and Organizations can log in to Rancher.
+		<br/>
+7.	Click **Save**.
+
+**Result:**
+
+- GitHub authentication is configured.
+- You are signed into Rancher with your GitHub account.
+- Your GitHub account is added to Rancher as an administrator.
+
+### To Configure Local Authentication
+
+1.	From the **Global** view, select **Users** from the main menu.
+
+2.	Click **Add User**. Then complete the **Add User** form. Click **Create** when you're done.
@@ -1,7 +1,8 @@
 ---
-title: Upgrade Scenarios
+title: Upgrades
 weight: 1000
 ---

-Notes:	1.	Upgrade Scenarios
-A list of upgrade scenarios. Each scenario offers a synopsis.
+# Upgrades
+
+Coming Soon!