checking in skeleton for the install bucket so that contributors have some guidance about where to write their content.

2026-09-26 13:08:11 +00:00 · 2018-04-19 17:05:23 -07:00
parent c647774db5
commit 5ad9008500
12 changed files with 159 additions and 17 deletions
@@ -6,5 +6,6 @@
  weight: 100
 ---

-Notes:	Installation Scenarios
+# Installation Scenarios
+
 A directory of install scenarios. Each scenario offers a synopsis.
@@ -0,0 +1,18 @@
+---
+title: "{{ replace .TranslationBaseName "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+tags: [ "tag", "tag", "tag", "tag" ]
+layout: single-left
+categories:
+  - ""
+  - ""
+---
+
+# Load Balancing Configuration
+
+## Option 1: Amazon ELB
+
+## Option 2: HAProxy
+
+## Option 3: NGINX
@@ -1,13 +1,16 @@
 # Rancher Requirements

-#### Hardware Requirements
+## Operating System Requirements
+
+-	Operating System: Ubuntu 16.04 (64-bit)
+
+## Hardware Requirements

 -	Memory: 4GB

-#### Software requirements
+## Software Requirements

-	Operating System: Ubuntu 16.04 (64-bit)
-	Software: Docker
+-	Docker

 	<a name="node-requirements"></a>**Supported Versions:**

@@ -20,11 +23,11 @@
 	> * For Docker installation instructions, visit their [documentation](https://docs.docker.com/install/).
 	> * Docker requirements apply to both your Linux host and your cluster nodes.

-#### Port Requirements
+## Port Requirements

 When provisioning your Linux host, open the ports listed below so that your master and worker nodes can communicate.

-##### Master Nodes (etcd and controlplane nodes)
+### Master Nodes (etcd and controlplane nodes)

 Protocol  | Direction  | Port Range  | Purpose  
 --|---|---|--
@@ -38,7 +41,7 @@ TCP | Inbound | 10251  | scheduler
 TCP | Inbound | 10252  | controller
 TCP | Inbound | 10256  | kubeproxy

-##### Worker Nodes
+### Worker Nodes

 Protocol  | Direction  | Port Range  | Purpose  
 --|---|---|--
@@ -48,3 +51,11 @@ TCP | Inbound | 443  | Canal
 TCP | Inbound | 10250  |  kubelet API
 TCP | Inbound | 10256  |  kubeproxy
 TCP | Inbound | 30000-32767  |  NodePort Services
+
+## Additional Requirements
+
+### Non High Availability
+
+### High Availability
+
+### Optional: etcd
@@ -0,0 +1,11 @@
+---
+title: "{{ replace .TranslationBaseName "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+tags: [ "tag", "tag", "tag", "tag" ]
+layout: single-left
+categories:
+  - "rancher"
+---
+
+# {{< product >}} Server Installation
@@ -0,0 +1,14 @@
+---
+title: "{{ replace .TranslationBaseName "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+tags: [ "tag", "tag", "tag", "tag" ]
+layout: single-left
+categories:
+  - ""
+  - ""
+---
+
+# Multi-Node Installation
+
+## Part 1: Launch Using RKE
@@ -0,0 +1,18 @@
+---
+title: "{{ replace .TranslationBaseName "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+tags: [ "tag", "tag", "tag", "tag" ]
+layout: single-left
+categories:
+  - ""
+  - ""
+---
+
+# Single Node Installation
+
+## Option 1: Single Container Install
+
+## Option 2: Single Container With External ETCD
+
+## Option 3: Local Cluster Install
@@ -0,0 +1,12 @@
+---
+title: "{{ replace .TranslationBaseName "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+tags: [ "tag", "tag", "tag", "tag" ]
+layout: single-left
+categories:
+  - ""
+  - ""
+---
+
+# Rancher Server Tags
@@ -0,0 +1,26 @@
+---
+title: "{{ replace .TranslationBaseName "-" " " | title }}"
+date: {{ .Date }}
+draft: true
+tags: [ "tag", "tag", "tag", "tag" ]
+layout: single-left
+categories:
+  - ""
+  - ""
+---
+
+# SSL Configuration
+
+## Before You Start: Choose a Certificate Host
+
+### On {{< product >}}
+
+### On Load Balancer
+
+## Option 1: Default Self-Signed Certificate
+
+## Option 2: Self-Provided Self-Signed Certificate
+
+## Option 3: LetsEncrypt Signed Certificate
+
+## Option 4: Certificate Authority Signed Certificate
@@ -0,0 +1,10 @@
+---
+tag: ["rancher", "pod security policies","security policies", "settings" ]
+category: "rancher"
+layout: list-docs
+title: Creating a Cluster
+weight: 90
+---
+# Creating a Cluster
+
+let's create clusters!
@@ -15,14 +15,35 @@ Using {{< product >}}, you can create a pod security policy using our GUI rather
 	**Step Result:** The **Add Policy** form opens.

 2. Name the policy.
+
 3. Complete each section of the form. Refer to the Kubernetes documentation linked below for more information on what each policy does.

-	- Basic Policies
-	- Capability Policies
-	- Volume Policy
-	- Allowed Host Paths Policy
-	- FS Group Policy
-	- Host Ports Policy
-	- Run As User Policy
-	- SELinux Policy
-	- Supplemental Groups Policy
+	- Basic Policies:
+
+		- [Privilege Escalation](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#privilege-escalation)
+		- [Host Namespaces][2]
+		- [Read Only Root Filesystems][1]
+
+	- [Capability Policies](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#capabilities)
+	- [Volume Policy][1]
+	- [Allowed Host Paths Policy][1]
+	- [FS Group Policy][1]
+	- [Run As User Policy][1]
+	- [Host Ports Policy][2]
+	- [Run As User Policy][3]
+	- [SELinux Policy](https://kubernetes.io/docs/concepts/policy/pod-security-policy/#selinux)
+	- [Supplemental Groups Policy][3]
+
+### What's Next?
+
+Now that you've created a Pod Security Policy, you can apply it to:
+
+- An existing cluster
+- A brand new cluster. For more details, see [Creating a Cluster](../../clusters/creating-a-cluster/_index)
+
+
+<!-- links -->
+
+[1]: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#volumes-and-file-systems
+[2]: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#host-namespaces
+[3]: https://kubernetes.io/docs/concepts/policy/pod-security-policy/#users-and-groups