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

Merge pull request #2085 from catherineluse/reorg

Browse Source 
Add content to blank page
This commit is contained in:
Catherine Luse
2019-12-12 08:39:23 -07:00
committed by GitHub
parent f834419912 421f047241
commit a70b7062bf
2 changed files with 13 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/other-installation-methods/_index.md
+12
View File
@@ -2,3 +2,15 @@
title: Other Installation Methods
weight: 4
---
### Single Node Installations
The [single-node Docker installation]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/single-node) is for Rancher users that are wanting to test out Rancher. Instead of running on a Kubernetes cluster using Helm, you install the Rancher server component on a single node using a `docker run` command.
Since there is only one node and a single Docker container, if the node goes down, there is no copy of the etcd data available on other nodes and you will lose all the data of your Rancher server.
### Air Gapped Installations
Follow [these steps]({{<baseurl>}}/rancher/v2.x/en/installation/other-installation-methods/air-gap) to install the Rancher server in an air gapped environment.
An air gapped environment could be where Rancher server will be installed offline, behind a firewall, or behind a proxy.
content/rancher/v2.x/en/installation/other-installation-methods/air-gap/_index.md
+1 -1
View File
@@ -11,7 +11,7 @@ This section is about installations of Rancher server in an air gapped environme
### Air Gapped High Availability (HA) Installations
Rancher recommends installing Rancher in a Highly Available (HA) configuration in an air gapped environment.
This section covers how to install Rancher in a Highly Available (HA) configuration in an air gapped environment.
An HA installation is comprised of three nodes running the Rancher server components on a Kubernetes cluster. The persistence layer (etcd) is also replicated on these three nodes, providing redundancy and data duplication in case one of the nodes fails.