mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-28 22:18:52 +00:00
unshelving new install files and deleting old ones
This commit is contained in:
@@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
title: Single Node Installation
|
||||||
|
layout: single-docs
|
||||||
|
weight: 250
|
||||||
|
---
|
||||||
|
|
||||||
|
# Installing Rancher Using a Docker Container
|
||||||
|
|
||||||
|
## Provision Linux Host
|
||||||
|
|
||||||
|
Provision a single Linux host to use as a template to launch your {{< product >}}.
|
||||||
|
|
||||||
|
### Requirements
|
||||||
|
|
||||||
|
{{< requirements_os >}}
|
||||||
|
|
||||||
|
{{< requirements_hardware >}}
|
||||||
|
|
||||||
|
{{< requirements_software >}}
|
||||||
|
|
||||||
|
## Install Rancher
|
||||||
|
|
||||||
|
Installing Rancher on a Linux host using a single Docker container is simple. Simply connect to your host and run the command below.
|
||||||
|
|
||||||
|
1. Log in to your Linux host using your preferred shell, such as PuTTy or a remote Terminal connection.
|
||||||
|
|
||||||
|
2. From your shell, enter the following command:
|
||||||
|
|
||||||
|
```
|
||||||
|
$ sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher
|
||||||
|
```
|
||||||
|
|
||||||
|
>**Note:**
|
||||||
|
>- `rancher/rancher` is hosted on DockerHub. If you don't have access to DockerHub, or you are installing Rancher without an internet connection, refer to {{< ref "private-registries" >}}.
|
||||||
|
>- For a list of other Rancher server tags available, refer to {{< ref "server-tags" >}}.
|
||||||
|
|
||||||
|
**Result:** Rancher is installed.
|
||||||
+20
-8
@@ -1,21 +1,32 @@
|
|||||||
---
|
---
|
||||||
title: High-Availability Installation
|
title: Installing Rancher in a Kubernetes Cluster
|
||||||
layout: single-docs
|
layout: single-docs
|
||||||
weight: 275
|
weight: 275
|
||||||
---
|
---
|
||||||
|
|
||||||
# High-Availability Installation <br/>(i.e. Multi-Node Installation)
|
# Installing Rancher in a Kubernetes Cluster
|
||||||
|
|
||||||
In high-availability installations, Rancher is installed on multiple nodes of a Kubernetes cluster. This multi-node configuration ensures that Rancher server is always available, even if your primary Rancher server goes down.
|
In high-availability installations, Rancher is installed on multiple nodes of a Kubernetes cluster. This multi-node configuration ensures that Rancher server is always available, even if your primary Rancher server goes down.
|
||||||
|
|
||||||
## Provision Linux Hosts
|
## Provision Linux Hosts
|
||||||
|
|
||||||
1. Provision a minimum of three Linux hosts according to our {{ ref "server-requirements.md" }}
|
Provision a minimum of three Linux hosts. Use the requirements below.
|
||||||
2. Add the hosts to your Domain Name System (DNS)—each host requires a fully qualified domain name (FQDN) for something you'll be doing later.
|
|
||||||
|
### Requirements
|
||||||
|
|
||||||
|
{{< requirements_os >}}
|
||||||
|
|
||||||
|
{{< requirements_hardware >}}
|
||||||
|
|
||||||
|
{{< requirements_software >}}
|
||||||
|
|
||||||
|
{{< requirements_ports >}}
|
||||||
|
|
||||||
|
{{< requirements_ha >}}
|
||||||
|
|
||||||
## Get RKE
|
## Get RKE
|
||||||
|
|
||||||
Rancher Kubernetes Engine (RKE) is a fast, versatile Kubernetes installe you can use to install Kubernetes on your Linux hosts. You can download RKE from GitHub.
|
Rancher Kubernetes Engine (RKE) is a fast, versatile Kubernetes installer you can use to install Kubernetes on your Linux hosts. You can download RKE from GitHub.
|
||||||
|
|
||||||
1. From your workstation, open a web browser and navigate to [https://github.com/rancher/rke/releases](https://github.com/rancher/rke/releases). Download the latest RKE installer.
|
1. From your workstation, open a web browser and navigate to [https://github.com/rancher/rke/releases](https://github.com/rancher/rke/releases). Download the latest RKE installer.
|
||||||
|
|
||||||
@@ -60,21 +71,21 @@ Once you have a template, customize it to suit your needs.
|
|||||||
|
|
||||||
```
|
```
|
||||||
nodes:
|
nodes:
|
||||||
- address: 159.65.99.240
|
- address: <HOSTIP>
|
||||||
user: root
|
user: root
|
||||||
role:
|
role:
|
||||||
- controlplane
|
- controlplane
|
||||||
- etcd
|
- etcd
|
||||||
- worker
|
- worker
|
||||||
ssh_key_path: /home/user/.ssh/id_rsa #PATH TO PUBLIC KEY, I.E. PEM FILE
|
ssh_key_path: /home/user/.ssh/id_rsa #PATH TO PUBLIC KEY, I.E. PEM FILE
|
||||||
- address: 206.189.168.116
|
- address: <HOSTIP>
|
||||||
user: root
|
user: root
|
||||||
role:
|
role:
|
||||||
- controlplane
|
- controlplane
|
||||||
- etcd
|
- etcd
|
||||||
- worker
|
- worker
|
||||||
ssh_key_path: /home/user/.ssh/id_rsa #PATH TO PUBLIC KEY, I.E. PEM FILE
|
ssh_key_path: /home/user/.ssh/id_rsa #PATH TO PUBLIC KEY, I.E. PEM FILE
|
||||||
- address: 206.189.168.31
|
- address: <HOSTIP>
|
||||||
user: root
|
user: root
|
||||||
role:
|
role:
|
||||||
- controlplane
|
- controlplane
|
||||||
@@ -138,6 +149,7 @@ Once you have a template, customize it to suit your needs.
|
|||||||
- `<BASE64_KEY>`
|
- `<BASE64_KEY>`
|
||||||
- `<BASE64_CA>`
|
- `<BASE64_CA>`
|
||||||
|
|
||||||
|
|
||||||
**Example:**
|
**Example:**
|
||||||
|
|
||||||
```
|
```
|
||||||
@@ -1,25 +0,0 @@
|
|||||||
---
|
|
||||||
title: Single Node Installation
|
|
||||||
layout: single-docs
|
|
||||||
weight: 250
|
|
||||||
---
|
|
||||||
|
|
||||||
# Single-Node Installation
|
|
||||||
|
|
||||||
## Option 1: Single Container Install
|
|
||||||
|
|
||||||
Installing Rancher on a Linux host using a single Docker container is simple. Simply connect to your host and run the command below.
|
|
||||||
|
|
||||||
1. Log in to your Linux host using your preferred shell, such as PuTTy or a remote Terminal connection.
|
|
||||||
|
|
||||||
2. From your shell, enter the following command:
|
|
||||||
|
|
||||||
```
|
|
||||||
$ sudo docker run -d --restart=unless-stopped -p 80:80 -p 443:443 rancher/rancher
|
|
||||||
```
|
|
||||||
|
|
||||||
**Result:** Rancher is installed.
|
|
||||||
|
|
||||||
## Option 2: Single Container Install with etcd
|
|
||||||
|
|
||||||
## Option 3: Local Cluster Install
|
|
||||||
Reference in New Issue
Block a user