mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 04:28:15 +00:00
updated HA install instructions per will and sheng. split into two procedures, made instructions more didactic, linked to new templates in rancher repo, simplified port table
This commit is contained in:
Mark Bishop
+7
-194
@@ -4,203 +4,16 @@ weight: 275
|
||||
---
|
||||
# High Availability Rancher Server Install
|
||||
|
||||
You can deploy Rancher in a high-availability (HA) configuration using the Rancher Kubernetes Engine (RKE). RKE is Rancher's own fast and light-weight Kubernetes installer. Use RKE to set up a new cluster that deploys Rancher as an addon.
|
||||
You have the option of installing Rancher Server in a High-Availability (HA) configuration. This configuration sets up multiple Rancher Servers, which ensure that you can always access Rancher, even when one of your Rancher Servers is down for maintentance.
|
||||
|
||||
## Objectives
|
||||
Install Rancher in an HA configuration using the Rancher Kubernetes Engine (RKE). RKE is Rancher's own fast and light-weight Kubernetes installer. Use RKE to set up a new cluster that deploys Rancher as an addon.
|
||||
|
||||
We've broken installation of Rancher by Kubernetes into a series of smaller tasks. Here's what you'll do during your RKE install.
|
||||
Complete one of the following procedures to install Rancher in an HA configuration:
|
||||
|
||||
1. [Provision Linux Hosts](#provision-linux-hosts)
|
||||
- [SSL Passthrough]({{< baseurl >}}/rancher/v2.x/en/installation/server-installation/ha-server-install/ssl-passthrough/)
|
||||
|
||||
Begin by provisioning Linux hosts or an existing Kubernetes cluster. Make sure your hosts meet Rancher requirements.
|
||||
In this scenario, your High-Availability Rancher Servers handle SSL decryption rather than a Load Balancer.
|
||||
|
||||
2. [Get RKE](#get-rke)
|
||||
- [SSL Termination]({{< baseurl >}}/rancher/v2.x/en/installation/server-installation/ha-server-install/ssl-termination/)
|
||||
|
||||
Download the RKE installer from GitHub.
|
||||
|
||||
3. [Get YAML Template](#get-yaml-template)
|
||||
|
||||
During installation, the RKE uses a `.yml` config file containing specifications for your cluster. You'll have to configure this file. We have a variety of config file templates available for download.
|
||||
|
||||
4. [Edit YAML Template](#edit-yaml-template)
|
||||
|
||||
After you download a config file template, edit it according to how you want to configure Rancher and your Kubernetes cluster.
|
||||
|
||||
5. [Run RKE](#run-rke)
|
||||
|
||||
Finally, run the RKE installer with it pointing toward your config file.
|
||||
|
||||
### Provision Linux Hosts
|
||||
|
||||
Before you install Rancher, confirm you meet the requirements. Provision a minimum of three new Linux hosts using the requirements below.
|
||||
|
||||
#### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
{{< requirements_ports >}}
|
||||
|
||||
{{< requirements_ha >}}
|
||||
|
||||
### Get RKE
|
||||
|
||||
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.
|
||||
|
||||
2. Make the RKE binary that you just downloaded executable. Open Terminal, change directory to the location of the RKE binary, and then run the following command:
|
||||
|
||||
```
|
||||
$ chmod +x rke
|
||||
```
|
||||
|
||||
>**Note:** adjust the command for the version of RKE that you downloaded (e.g., `rke_darwin-amd64`)
|
||||
|
||||
3. Confirm that RKE is now executable by running the following command:
|
||||
|
||||
```
|
||||
$ ./rke -version
|
||||
```
|
||||
|
||||
**Result:** You receive output similar to what follows:
|
||||
```
|
||||
rke version v<N.N.N>
|
||||
```
|
||||
|
||||
### Get YAML Template
|
||||
|
||||
During installation, RKE uses a `.yml` config file to install and configure your Kubernetes cluster. Download the `.zip` file of `.yml` templates linked below to get you started. Choose a template based on how many nodes are in your cluster and the type of certificate you plan on using:
|
||||
|
||||
- If you want to use Auto-Generated Self-Signed Certifcates (i.e. SSL passthrough), use one of the `passthough` templates.
|
||||
- If you want to use your own certificate (either CA- or Self-Signed), use one of the `certificate` templates.
|
||||
|
||||
[Download YAML Config Templates](https://gist.github.com/MBishop17/ca4691a1b126a93bf8f21bc15d44ce02)
|
||||
|
||||
### Edit YAML Template
|
||||
|
||||
Once you have a template, customize it to suit your needs.
|
||||
|
||||
1. Open the `.yml` file that you just downloaded.
|
||||
|
||||
2. Update the `nodes` section with your [Linux hosts](#provision-linux-hosts).
|
||||
|
||||
1. For each node in your cluster, update the following placeholders:
|
||||
|
||||
- `<IP>`: The IP address or hostname of the node.
|
||||
- `<USER>`: The node root user (usually `root`).
|
||||
- `<PEM_FILE>`: The path of the `.pem` file used to authenticate.
|
||||
|
||||
2. For each node in your cluster, choose what roles each node should fill. Delete any roles that aren't needed on the node.
|
||||
|
||||
**Example YAML**
|
||||
|
||||
nodes:
|
||||
- address: <IP> # IP to access nodes
|
||||
user: <USER> # root user (usually 'root')
|
||||
role: [controlplane,etcd,worker] # K8s roles for node
|
||||
ssh_key_path: <PEM_FILE> # path to PEM file
|
||||
- address: <IP>
|
||||
user: <USER>
|
||||
role: [controlplane,etcd,worker]
|
||||
ssh_key_path: <PEM_FILE>
|
||||
- address: <IP>
|
||||
user: <USER>
|
||||
role: [controlplane,etcd,worker]
|
||||
ssh_key_path: <PEM_FILE>
|
||||
|
||||
3. Scroll to `kind: Ingress`. Replace the two `<FQDN>` placeholders with the FQDN mapped to each IP address for `controlplane` and/or `worker` nodes on your DNS. On your DNS Server, each node should be added to the DNS entry for the FQDN.
|
||||
|
||||
**Example YAML**
|
||||
|
||||
spec:
|
||||
rules:
|
||||
- host: <FQDN> # FQDN to access cattle server
|
||||
http:
|
||||
paths:
|
||||
- backend:
|
||||
serviceName: cattle-service
|
||||
servicePort: 80
|
||||
tls:
|
||||
- secretName: cattle-keys-ingress
|
||||
hosts:
|
||||
- <FQDN> # FQDN to access cattle server
|
||||
|
||||
|
||||
>**Using Auto-Generated Self-Signed Certificates?**
|
||||
>
|
||||
>The next two steps don't apply to you. Save the `.yml` config file and continue to [Run RKE](#run-rke).
|
||||
|
||||
4. **Bring Your Own Certificate only:** Scroll to the codeblock that follows.
|
||||
|
||||
```
|
||||
apiVersion: v1
|
||||
kind: Secret
|
||||
metadata:
|
||||
name: cattle-keys-server
|
||||
namespace: cattle-system
|
||||
type: Opaque
|
||||
data:
|
||||
cert.pem: <BASE64_CRT> # ssl cert for cattle server.
|
||||
key.pem: <BASE64_KEY> # ssl key for cattle server.
|
||||
cacerts.pem: <BASE64_CA> # CA cert used to sign cattle server cert and key
|
||||
```
|
||||
|
||||
Replace each placeholder with the applicable `.pem`.
|
||||
|
||||
- `<BASE64_CRT>`
|
||||
- `<BASE64_KEY>`
|
||||
- `<BASE64_CA>`
|
||||
|
||||
>**Important:**
|
||||
>
|
||||
> - Each `.pem` must be in base-64: `cat <PEM_FILE> | base64`
|
||||
> - If you're using a self-signed certificate, the `cattle-keys-server` in this step and `cattle-keys-ingress` in the next step must use certificates and keys signed by the same CA.
|
||||
|
||||
5. **Bring Your Own Certificate only:** Scroll to the codeblock that follows.
|
||||
|
||||
```
|
||||
apiVersion: v1
|
||||
kind: Secret
|
||||
metadata:
|
||||
name: cattle-keys-ingress
|
||||
namespace: cattle-system
|
||||
type: Opaque
|
||||
data:
|
||||
tls.crt: <BASE64_CRT> # ssl cert for ingress. If selfsigned, must be signed by same CA as cattle server
|
||||
tls.key: <BASE64_KEY> # ssl key for ingress. If selfsigned, must be signed by same CA as cattle server
|
||||
```
|
||||
|
||||
Replace each placeholder with the applicable `.pem`.
|
||||
|
||||
- `<BASE64_CRT>`
|
||||
- `<BASE64_KEY>`
|
||||
|
||||
|
||||
>**Reminder:**
|
||||
>
|
||||
> - Each `.pem` must be in base-64: `cat <PEM_FILE> | base64`
|
||||
> If you're using a self-signed certificate, the `cattle-keys-server` from last step and `cattle-keys-ingress` from this step must use certificates and keys signed by the same CA.
|
||||
|
||||
6. Save the `.yml` file and close it.
|
||||
|
||||
### Run RKE
|
||||
|
||||
Enter the command to run RKE while pointing to your `.yml` file. RKE will install Kubernetes and Rancher using your parameters.
|
||||
|
||||
1. From your workstation, make sure your `.yml` config file and RKE are in the same directory.
|
||||
|
||||
2. Open a Terminal instance. Change to the directory that contains your config file and RKE.
|
||||
|
||||
3. Enter the following command, replacing the placeholder name with the name of the `.yml` config template that you used.
|
||||
|
||||
```
|
||||
rke up --config <YAML_TEMPLATE>
|
||||
```
|
||||
|
||||
### What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN used earlier in this procedure.
|
||||
In this scenario, your Load Balancer handles all SSL encryption, and then forwards on the communication within your Kubernetes cluster unencrypted.
|
||||
|
||||
+143
@@ -0,0 +1,143 @@
|
||||
---
|
||||
title: SSL Passthrough
|
||||
weight: 275
|
||||
---
|
||||
# High Availability Install with SSL Passthrough
|
||||
|
||||
In this scenario, your High-Availability Rancher Servers handle SSL decryption rather than a Load Balancer.
|
||||
|
||||
## Objectives
|
||||
|
||||
We've broken installation of Rancher with SSL passthrough into a series of smaller tasks. Here's what you'll do during install.
|
||||
|
||||
1. [Provision Linux Hosts](#provision-linux-hosts)
|
||||
|
||||
Begin by provisioning Linux hosts. Make sure your hosts meet Rancher requirements.
|
||||
|
||||
2. [Get RKE](#get-rke)
|
||||
|
||||
Download the Rancher Kubernetes Engine (RKE) installer from GitHub.
|
||||
|
||||
3. [Get YAML Config File Template](#get-yaml-template)
|
||||
|
||||
During installation, RKE uses a `.yml` config file containing specifications for your cluster. Download our template from GitHub.
|
||||
|
||||
4. [Edit YAML Config File Template](#edit-yaml-template)
|
||||
|
||||
Edit the `.yml` config file so that it's pointing toward your Linux hosts.
|
||||
|
||||
5. [Run RKE](#run-rke)
|
||||
|
||||
Finally, run the RKE installer with it pointing toward your `.yml` config file.
|
||||
|
||||
### Provision Linux Hosts
|
||||
|
||||
Before you install Rancher, confirm you meet the requirements. Provision three new Linux hosts using the requirements below.
|
||||
|
||||
#### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
{{< requirements_ports >}}
|
||||
|
||||
### Get RKE
|
||||
|
||||
Rancher Kubernetes Engine (RKE) is a fast, versatile Kubernetes installer that 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 our [RKE Releases](https://github.com/rancher/rke/releases) page. Download the latest RKE installer.
|
||||
|
||||
2. Make the RKE binary that you just downloaded executable. Open Terminal, change directory to the location of the RKE binary, and then run the following command:
|
||||
|
||||
```
|
||||
$ chmod +x rke
|
||||
```
|
||||
|
||||
>**Note:** Adjust the command for the version of RKE that you downloaded (e.g., `rke_darwin-amd64`)
|
||||
|
||||
3. Confirm that RKE is now executable by running the following command:
|
||||
|
||||
```
|
||||
$ ./rke -version
|
||||
```
|
||||
|
||||
**Result:** You receive output similar to what follows:
|
||||
```
|
||||
rke version v<N.N.N>
|
||||
```
|
||||
|
||||
### Get YAML Config File Template
|
||||
|
||||
During installation, RKE uses a `.yml` config file to install and configure your Kubernetes cluster. Download the `.yml` config file linked below to get you started.
|
||||
|
||||
[Download SSL Passthrough YAML Config Template](placeholder)
|
||||
|
||||
### Edit YAML Template
|
||||
|
||||
Once you have the `.yml` config file template, edit the nodes section to point toward your Linux hosts.
|
||||
|
||||
1. Open the `.yml` config file that you just downloaded.
|
||||
|
||||
2. Update the `nodes` section with your [Linux hosts](#provision-linux-hosts).
|
||||
|
||||
For each node in your cluster, update the following placeholders:
|
||||
|
||||
- `<IP>`: The IP address or hostname of the node.
|
||||
- `<USER>`: The node root user (usually `root`).
|
||||
- `<PEM_FILE>`: The path of the `.pem` file used to authenticate.
|
||||
|
||||
**Example YAML**
|
||||
|
||||
nodes:
|
||||
- address: <IP> # IP to access nodes
|
||||
user: <USER> # root user (usually 'root')
|
||||
role: [controlplane,etcd,worker] # K8s roles for node
|
||||
ssh_key_path: <PEM_FILE> # path to PEM file
|
||||
- address: <IP>
|
||||
user: <USER>
|
||||
role: [controlplane,etcd,worker]
|
||||
ssh_key_path: <PEM_FILE>
|
||||
- address: <IP>
|
||||
user: <USER>
|
||||
role: [controlplane,etcd,worker]
|
||||
ssh_key_path: <PEM_FILE>
|
||||
|
||||
3. Scroll to `kind: Ingress`. Replace the two `<FQDN>` placeholders with the FQDN mapped to each of your nodes. On your DNS Server, each node should be added to the DNS entry for the FQDN.
|
||||
|
||||
**Example YAML**
|
||||
|
||||
spec:
|
||||
rules:
|
||||
- host: <FQDN> # FQDN to access cattle server
|
||||
http:
|
||||
paths:
|
||||
- backend:
|
||||
serviceName: cattle-service
|
||||
servicePort: 80
|
||||
tls:
|
||||
- secretName: cattle-keys-ingress
|
||||
hosts:
|
||||
- <FQDN> # FQDN to access cattle server
|
||||
|
||||
6. Save the `.yml` config file and close it.
|
||||
|
||||
### Run RKE
|
||||
|
||||
Enter the command to run RKE while pointing to your `.yml` config file. RKE installs Kubernetes and Rancher using your parameters.
|
||||
|
||||
1. From your workstation, make sure your `.yml` config file and RKE are in the same directory.
|
||||
|
||||
2. Open a Terminal instance. Change to the directory that contains your config file and RKE.
|
||||
|
||||
3. Enter the following command, replacing the placeholder name with the name of the `.yml` config template that you used.
|
||||
|
||||
```
|
||||
rke up --config <YAML_CONFIG_FILE>
|
||||
```
|
||||
|
||||
### What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN used earlier in this procedure.
|
||||
+203
@@ -0,0 +1,203 @@
|
||||
---
|
||||
title: SSL Termination
|
||||
weight: 275
|
||||
---
|
||||
# High Availability Install with SSL Temination
|
||||
|
||||
In this scenario, your Load Balancer handles all SSL decryption, and then forwards the decrypted communications to your cluster.
|
||||
|
||||
## Objectives
|
||||
|
||||
We've broken installation of Rancher with SSL termination into a series of smaller tasks. Here's what you'll do during your install.
|
||||
|
||||
1. [Provision Linux Hosts](#provision-linux-hosts)
|
||||
|
||||
Begin by provisioning Linux hosts. Make sure your hosts meet Rancher requirements.
|
||||
|
||||
2. [Get RKE](#get-rke)
|
||||
|
||||
Download the Rancher Kubernetes Engine (RKE) installer from GitHub.
|
||||
|
||||
3. [Get YAML Template](#get-yaml-template)
|
||||
|
||||
During installation, RKE uses a `.yml` config file containing specifications for your cluster. Download our template from GitHub.
|
||||
|
||||
4. [Edit YAML Template](#edit-yaml-template)
|
||||
|
||||
Edit the `.yml` config file so that it's pointing toward your Linux hosts.
|
||||
|
||||
5. [Run RKE](#run-rke)
|
||||
|
||||
Finally, run the RKE installer with it pointing toward your `.yml` config file.
|
||||
|
||||
### Provision Linux Hosts
|
||||
|
||||
Before you install Rancher, confirm you meet the requirements. Provision three new Linux hosts using the requirements below.
|
||||
|
||||
#### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
{{< requirements_ports >}}
|
||||
|
||||
##### Certificate Requirements
|
||||
|
||||
Before starting this procedure, you should generate or obtain your own certificate.
|
||||
|
||||
The certificate can either be:
|
||||
|
||||
- Self-signed
|
||||
- Signed by a certificate authority (CA)
|
||||
|
||||
>**Note:**
|
||||
>-If you use a self-signed certificate, all certificates and keys must be signed by the same CA.<br/>
|
||||
>-Each `.pem` must be in base-64: `cat <PEM_FILE> | base64`.
|
||||
|
||||
|
||||
|
||||
### Get RKE
|
||||
|
||||
Rancher Kubernetes Engine (RKE) is a fast, versatile Kubernetes installer that 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 our [RKE Releases](https://github.com/rancher/rke/releases) page. Download the latest RKE installer.
|
||||
|
||||
2. Make the RKE binary that you just downloaded executable. Open Terminal, change directory to the location of the RKE binary, and then run the following command:
|
||||
|
||||
```
|
||||
$ chmod +x rke
|
||||
```
|
||||
|
||||
>**Note:** Adjust the command for the version of RKE that you downloaded (e.g., `rke_darwin-amd64`)
|
||||
|
||||
3. Confirm that RKE is now executable by running the following command:
|
||||
|
||||
```
|
||||
$ ./rke -version
|
||||
```
|
||||
|
||||
**Result:** You receive output similar to what follows:
|
||||
```
|
||||
rke version v<N.N.N>
|
||||
```
|
||||
|
||||
### Get YAML Template
|
||||
|
||||
During installation, RKE uses a `.yml` config file to install and configure your Kubernetes cluster. Download the `.yml` config file linked below to get you started.
|
||||
|
||||
[Download SSL Termination YAML Config Template](placeholder)
|
||||
|
||||
### Edit YAML Template
|
||||
|
||||
Once you have the `.yml` config file template, edit the nodes section to point toward your Linux hosts.
|
||||
|
||||
1. Open the `.yml` file that you just downloaded.
|
||||
|
||||
2. Update the `nodes` section with your [Linux hosts](#provision-linux-hosts).
|
||||
|
||||
For each node in your cluster, update the following placeholders:
|
||||
|
||||
- `<IP>`: The IP address or hostname of the node.
|
||||
- `<USER>`: The node root user (usually `root`).
|
||||
- `<PEM_FILE>`: The path of the `.pem` file used to authenticate.
|
||||
|
||||
**Example YAML**
|
||||
|
||||
nodes:
|
||||
- address: <IP> # IP to access nodes
|
||||
user: <USER> # root user (usually 'root')
|
||||
role: [controlplane,etcd,worker] # K8s roles for node
|
||||
ssh_key_path: <PEM_FILE> # path to PEM file
|
||||
- address: <IP>
|
||||
user: <USER>
|
||||
role: [controlplane,etcd,worker]
|
||||
ssh_key_path: <PEM_FILE>
|
||||
- address: <IP>
|
||||
user: <USER>
|
||||
role: [controlplane,etcd,worker]
|
||||
ssh_key_path: <PEM_FILE>
|
||||
|
||||
3. Scroll to `kind: Ingress`. Replace the two `<FQDN>` placeholders with the FQDN mapped to each of your nodes. On your DNS Server, each node should be added to the DNS entry for the FQDN.
|
||||
|
||||
**Example YAML**
|
||||
|
||||
spec:
|
||||
rules:
|
||||
- host: <FQDN> # FQDN to access cattle server
|
||||
http:
|
||||
paths:
|
||||
- backend:
|
||||
serviceName: cattle-service
|
||||
servicePort: 80
|
||||
tls:
|
||||
- secretName: cattle-keys-ingress
|
||||
hosts:
|
||||
- <FQDN> # FQDN to access cattle server
|
||||
|
||||
4. Scroll to the codeblock that follows.
|
||||
|
||||
```
|
||||
apiVersion: v1
|
||||
kind: Secret
|
||||
metadata:
|
||||
name: cattle-keys-server
|
||||
namespace: cattle-system
|
||||
type: Opaque
|
||||
data:
|
||||
cert.pem: <BASE64_CRT> # ssl cert for cattle server.
|
||||
key.pem: <BASE64_KEY> # ssl key for cattle server.
|
||||
cacerts.pem: <BASE64_CA> # CA cert used to sign cattle server cert and key
|
||||
```
|
||||
|
||||
Replace each placeholder with the applicable certificate `.pem`.
|
||||
|
||||
- `<BASE64_CRT>`
|
||||
- `<BASE64_KEY>`
|
||||
- `<BASE64_CA>`
|
||||
|
||||
>**Reminder:** Each `.pem` must be in base-64: `cat <PEM_FILE> | base64`.
|
||||
|
||||
5. Scroll to the codeblock that follows.
|
||||
|
||||
```
|
||||
apiVersion: v1
|
||||
kind: Secret
|
||||
metadata:
|
||||
name: cattle-keys-ingress
|
||||
namespace: cattle-system
|
||||
type: Opaque
|
||||
data:
|
||||
tls.crt: <BASE64_CRT> # ssl cert for ingress. If self-signed, must be signed by same CA as cattle server
|
||||
tls.key: <BASE64_KEY> # ssl key for ingress. If self-signed, must be signed by same CA as cattle server
|
||||
```
|
||||
|
||||
Replace each placeholder with the applicable `.pem`.
|
||||
|
||||
- `<BASE64_CRT>`
|
||||
- `<BASE64_KEY>`
|
||||
|
||||
|
||||
>**Reminder:** Each `.pem` must be in base-64: `cat <PEM_FILE> | base64`.
|
||||
|
||||
6. Save the `.yml` file and close it.
|
||||
|
||||
### Run RKE
|
||||
|
||||
Enter the command to run RKE while pointing to your `.yml` config file. RKE installs Kubernetes and Rancher using your parameters.
|
||||
|
||||
1. From your workstation, make sure your `.yml` config file and RKE are in the same directory.
|
||||
|
||||
2. Open a Terminal instance. Change to the directory that contains your config file and RKE.
|
||||
|
||||
3. Enter the following command, replacing the placeholder name with the name of the `.yml` config template that you used.
|
||||
|
||||
```
|
||||
rke up --config <YAML_CONFIG_FILE>
|
||||
```
|
||||
|
||||
### What's Next?
|
||||
|
||||
Log in to Rancher to make sure it deployed successfully. Open a web browser and navigate to the FQDN used earlier in this procedure.
|
||||
@@ -1,11 +1,11 @@
|
||||
<div>
|
||||
<h5>Port Requirements</h5>
|
||||
<h6>Master Nodes (etcd and controlplane nodes)</h6>
|
||||
<p>Open the following ports on your Linux hosts.</p>
|
||||
<table>
|
||||
<tr>
|
||||
<th>protocol</th>
|
||||
<th>port range</th>
|
||||
<th>purpose</th>
|
||||
<th>Protocol</th>
|
||||
<th>Port range</th>
|
||||
<th>Purpose</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
@@ -15,12 +15,12 @@
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>80</td>
|
||||
<td>Rancher Server</td>
|
||||
<td>Rancher Server/ingress</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>443</td>
|
||||
<td>Rancher Server</td>
|
||||
<td>Rancher Server/ingress</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
@@ -34,112 +34,19 @@
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10250</td>
|
||||
<td>kubelet api</td>
|
||||
<td>10250-10256</td>
|
||||
<td>kubernetes components</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10251</td>
|
||||
<td>scheduler</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10252</td>
|
||||
<td>kube-controller-manager</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10253</td>
|
||||
<td>federation</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10254</td>
|
||||
<td>ingress</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10255</td>
|
||||
<td>read-only kubelet api</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10256</td>
|
||||
<td>kubeproxy</td>
|
||||
</tr>
|
||||
<td>tcp</td>
|
||||
<td>30000-32767</td>
|
||||
<td>nodeport services</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>udp</td>
|
||||
<td>8472</td>
|
||||
<td>canal</td>
|
||||
</tr>
|
||||
</table>
|
||||
<h6>Worker Nodes</h6>
|
||||
<table>
|
||||
<tr>
|
||||
<th>protocol</th>
|
||||
<th>port range</th>
|
||||
<th>purpose</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>22</td>
|
||||
<td>ssh server</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>80</td>
|
||||
<td>ingress</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>443</td>
|
||||
<td>ingress</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10250</td>
|
||||
<td>kubelet api</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10251</td>
|
||||
<td>scheduler</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10252</td>
|
||||
<td>kube-controller-manager</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10253</td>
|
||||
<td>federation</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10254</td>
|
||||
<td>ingress</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10255</td>
|
||||
<td>read-only kubelet api</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>10256</td>
|
||||
<td>kubeproxy</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>tcp</td>
|
||||
<td>30000-32767</td>
|
||||
<td>nodeport services</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>udp</td>
|
||||
<td>8472</td>
|
||||
<td>canal</td>
|
||||
</tr>
|
||||
</table>
|
||||
<br/>
|
||||
</div>
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
<div>
|
||||
<h4>Software Requestions</h4>
|
||||
<h4>Software Requirements</h4>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Docker</p>
|
||||
|
||||
Reference in New Issue
Block a user