From 9dd8e52bf53668fc1009f9020789b4db9624eaf9 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 9 Aug 2018 15:19:55 -0700 Subject: [PATCH 1/4] moving topics under installation folder into root. added aliases too --- .../rke/v0.1.x/en/{installation => }/etcd-snapshots/_index.md | 4 +++- .../v0.1.x/en/{installation => }/managing-clusters/_index.md | 4 +++- content/rke/v0.1.x/en/{installation => }/os/_index.md | 4 +++- 3 files changed, 9 insertions(+), 3 deletions(-) rename content/rke/v0.1.x/en/{installation => }/etcd-snapshots/_index.md (99%) rename content/rke/v0.1.x/en/{installation => }/managing-clusters/_index.md (95%) rename content/rke/v0.1.x/en/{installation => }/os/_index.md (99%) diff --git a/content/rke/v0.1.x/en/installation/etcd-snapshots/_index.md b/content/rke/v0.1.x/en/etcd-snapshots/_index.md similarity index 99% rename from content/rke/v0.1.x/en/installation/etcd-snapshots/_index.md rename to content/rke/v0.1.x/en/etcd-snapshots/_index.md index 022fdee9912..f9ab1d2bb6b 100644 --- a/content/rke/v0.1.x/en/installation/etcd-snapshots/_index.md +++ b/content/rke/v0.1.x/en/etcd-snapshots/_index.md @@ -1,6 +1,8 @@ --- title: Backups and Disaster Recovery -weight: 65 +weight: 150 +aliases: + - /rke/v0.1.x/en/installation/etcd-snapshots/ --- As of v0.1.7, you can configure a RKE cluster to automatically take snapshots of etcd. In a disaster scenario, you can restore these snapshots, which are stored on other nodes in the cluster. diff --git a/content/rke/v0.1.x/en/installation/managing-clusters/_index.md b/content/rke/v0.1.x/en/managing-clusters/_index.md similarity index 95% rename from content/rke/v0.1.x/en/installation/managing-clusters/_index.md rename to content/rke/v0.1.x/en/managing-clusters/_index.md index b4abbf17020..97345671800 100644 --- a/content/rke/v0.1.x/en/installation/managing-clusters/_index.md +++ b/content/rke/v0.1.x/en/managing-clusters/_index.md @@ -1,6 +1,8 @@ --- title: Managing RKE Clusters -weight: 60 +weight: 175 +aliases: + - /rke/v0.1.x/en/installation/managing-clusters/ --- ### Adding/Removing Nodes diff --git a/content/rke/v0.1.x/en/installation/os/_index.md b/content/rke/v0.1.x/en/os/_index.md similarity index 99% rename from content/rke/v0.1.x/en/installation/os/_index.md rename to content/rke/v0.1.x/en/os/_index.md index e15f2710f31..293fc9cfcb4 100644 --- a/content/rke/v0.1.x/en/installation/os/_index.md +++ b/content/rke/v0.1.x/en/os/_index.md @@ -1,6 +1,8 @@ --- title: Operating System Requirements -weight: 55 +weight: 5 +aliases: + - /rke/v0.1.x/en/etcd-snapshots/os --- RKE runs on almost any Linux OS with Docker installed. Most of the development and testing of RKE occurred on Ubuntu 16.04. However, some OS's have restrictions and specific requirements. From 4743a50cdf9310f00dadfabb2dde59cf8d9e1609 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 9 Aug 2018 15:39:55 -0700 Subject: [PATCH 2/4] retitling os reqs to requirements. Dividing into sections. --- content/rke/v0.1.x/en/os/_index.md | 33 +++++++++++++++++++++++++----- 1 file changed, 28 insertions(+), 5 deletions(-) diff --git a/content/rke/v0.1.x/en/os/_index.md b/content/rke/v0.1.x/en/os/_index.md index 293fc9cfcb4..e5fc2e2b736 100644 --- a/content/rke/v0.1.x/en/os/_index.md +++ b/content/rke/v0.1.x/en/os/_index.md @@ -1,9 +1,32 @@ --- -title: Operating System Requirements +title: Requirements weight: 5 aliases: - /rke/v0.1.x/en/etcd-snapshots/os --- +**In this section:** + + + +- [Operating System](#operating-system) + + - [RedHat Enterprise Linux (RHEL) / Oracle Enterprise Linux (OEL) / CentOS](#redhat-enterprise-linux-rhel--oracle-enterprise-linux-oel--centos) + + - [Using upstream Docker](#using-upstream-docker) + - [Using RHEL/CentOS packaged Docker](#using-rhelcentos-packaged-docker) +- [Software](#software) +- [Ports](#ports) + - [Opening port TCP/6443 using `iptables``](#opening-port-tcp6443-using-iptables) + - [Opening port TCP/6443 using `firewalld`](#opening-port-tcp6443-using-firewalld) +- [Notes about Atomic Nodes](#notes-about-atomic-nodes) + + - [Container Volumes](#container-volumes) + - [OpenSSH version](#openssh-version) + - [Creating a Docker Group](#creating-a-docker-group) + + + +## Operating System RKE runs on almost any Linux OS with Docker installed. Most of the development and testing of RKE occurred on Ubuntu 16.04. However, some OS's have restrictions and specific requirements. @@ -107,7 +130,7 @@ $ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ``` -### Software +## Software - Docker - Each Kubernetes version supports different Docker versions. @@ -149,14 +172,14 @@ Server: - OpenSSH 7.0+ - In order to SSH into each node, OpenSSH must be installed on each node. -### Ports +## Ports {{< requirements_ports_rke >}} If you are using an external firewall, make sure you have this port opened between the machine you are using to run `rke` and the nodes that you are going to use in the cluster. -#### Opening port TCP/6443 using `iptables`` +### Opening port TCP/6443 using `iptables`` ``` # Open TCP/6443 for all @@ -166,7 +189,7 @@ iptables -A INPUT -p tcp --dport 6443 -j ACCEPT iptables -A INPUT -p tcp -s your_ip_here --dport 6443 -j ACCEPT ``` -#### Opening port TCP/6443 using `firewalld` +### Opening port TCP/6443 using `firewalld` ``` # Open TCP/6443 for all From ba19895b50252896be597deb326e93a85df6234c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 9 Aug 2018 16:02:25 -0700 Subject: [PATCH 3/4] retitling sections --- content/rke/v0.1.x/en/managing-clusters/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rke/v0.1.x/en/managing-clusters/_index.md b/content/rke/v0.1.x/en/managing-clusters/_index.md index 97345671800..dae9101a846 100644 --- a/content/rke/v0.1.x/en/managing-clusters/_index.md +++ b/content/rke/v0.1.x/en/managing-clusters/_index.md @@ -1,5 +1,5 @@ --- -title: Managing RKE Clusters +title: Adding and Removing Nodes in RKE Clusters weight: 175 aliases: - /rke/v0.1.x/en/installation/managing-clusters/ @@ -19,7 +19,7 @@ After you've made changes to add/remove nodes, run `rke up` with the updated `cl You can add/remove only worker nodes, by running `rke up --update-only`. This will ignore everything else in the `cluster.yml` except for any worker nodes. -### Removing Kubernetes Clusters from Nodes +### Removing Kubernetes Components from Nodes In order to remove the Kubernetes components from nodes, you use the `rke remove` command. From cdc1c7cb00382c4c46d364cae31110b9c7e965a7 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 10 Aug 2018 15:09:32 -0700 Subject: [PATCH 4/4] correcting alias --- content/rke/v0.1.x/en/os/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rke/v0.1.x/en/os/_index.md b/content/rke/v0.1.x/en/os/_index.md index e5fc2e2b736..3dcc2f52f32 100644 --- a/content/rke/v0.1.x/en/os/_index.md +++ b/content/rke/v0.1.x/en/os/_index.md @@ -2,7 +2,7 @@ title: Requirements weight: 5 aliases: - - /rke/v0.1.x/en/etcd-snapshots/os + - /rke/v0.1.x/en/installation/os --- **In this section:**