mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 12:38:05 +00:00
requirement updates.
This commit is contained in:
Mark Bishop
committed by
Denise Schannon
Denise Schannon
parent
6e3162a64b
commit
1840e8c3fd
@@ -1,12 +1,16 @@
|
||||
# Authentication
|
||||
|
||||
One of the key features that {{< product >}} adds to Kubernetes is enhanced user authentication.
|
||||
One of the key features that {{< product >}} adds to Kubernetes is centralized user authentication. This feature allows your users to use one set of credentials to authenticate with any of your Kubernetes clusters.
|
||||
|
||||
By default, Kubernetes has some authentication shortcomings. Namely, users and groups are tied to the two scopes that Kubernetes uses to group resources: global and namespace. These scopes make it difficult to manage users and groups across different clusters and namespaces. Kubenetes allows integration with other authentication providers that work around these issues using plugins. However, this integration is not available to those leveraging cloud-based Kubenetes offerings such as Google Container Engine (GKE).
|
||||
This centralized user authentication is accomplished using the {{< product >}} authentication proxy, which is installed with the rest of {{< product >}}. This proxy authenticates your users and forwards their requests to your Kubernetes clusters using a service account.
|
||||
|
||||
Rancher improves on Kubernetes authentication by integrating external authentication. Out-of-the-box, Rancher provides integration with the following authentication services:
|
||||
## External vs. Local Authentication
|
||||
|
||||
The {{< product >}} authentication proxy integrates with the following external authentication services.
|
||||
|
||||
- Microsoft Active Directory
|
||||
- GitHub
|
||||
|
||||
## External vs. Local Authentication
|
||||
However, {{< product >}} also provides local authentication.
|
||||
|
||||
In most cases, you should use an external authentication service over local, as external authentication allows user management from a central location. However, you may want a few local authentication accounts for managing {{< product >}} under rare circumstances, such as if Active Directory is down.
|
||||
|
||||
@@ -1,78 +0,0 @@
|
||||
---
|
||||
title: Rancher Requirements
|
||||
draft: true
|
||||
tags: [ "tag", "tag", "tag", "tag" ]
|
||||
layout: single-left
|
||||
categories:
|
||||
- ""
|
||||
- ""
|
||||
---
|
||||
|
||||
# Rancher Requirements
|
||||
|
||||
Before you install {{< product >}}, wrangle up these requirements. Yip! Yip! Yah!
|
||||
|
||||
## Operating System Requirements
|
||||
|
||||
- Ubuntu 16.04 (64-bit)
|
||||
- Red Hat Enterprise Linux 7.5 (64-bit)
|
||||
- RancherOS
|
||||
|
||||
## Hardware Requirements
|
||||
|
||||
- Memory: 4GB
|
||||
|
||||
|
||||
## Software Requirements
|
||||
|
||||
- Docker
|
||||
|
||||
<a name="node-requirements"></a>**Supported Versions:**
|
||||
|
||||
- `1.12.6`
|
||||
- `1.13.1`
|
||||
- `17.03.2`
|
||||
|
||||
>**Notes:**
|
||||
>
|
||||
> * 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
|
||||
|
||||
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)
|
||||
|
||||
Protocol | Direction | Port Range | Purpose
|
||||
--|---|---|--
|
||||
TCP | Inbound | 22 | SSH server
|
||||
TCP | Inbound | 80 | ?
|
||||
TCP | Inbound | 443 | ?
|
||||
TCP | Inbound | 6443 | Kubernetes API server
|
||||
TCP | Inbound | 2379-2380 | etcd server client API
|
||||
TCP | Inbound | 10250 | kubelet API
|
||||
TCP | Inbound | 10251 | scheduler
|
||||
TCP | Inbound | 10252 | controller
|
||||
TCP | Inbound | 10256 | kubeproxy
|
||||
UDP | Inbound | 8472 | Canal
|
||||
|
||||
### Worker Nodes
|
||||
|
||||
Protocol | Direction | Port Range | Purpose
|
||||
--|---|---|--
|
||||
TCP | Inbound | 22 | SSH Server
|
||||
TCP | Inbound | 80 | ?
|
||||
TCP | Inbound | 443 | ?
|
||||
TCP | Inbound | 10250 | kubelet API
|
||||
TCP | Inbound | 10256 | kubeproxy
|
||||
TCP | Inbound | 30000-32767 | NodePort Services
|
||||
UDP | Inbound | 8472 | Canal
|
||||
|
||||
## Additional Requirements
|
||||
|
||||
### Non High Availability
|
||||
|
||||
### High Availability
|
||||
|
||||
### Optional: etcd
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
title: Requirements
|
||||
draft: true
|
||||
tags: [ "tag", "tag", "tag", "tag" ]
|
||||
layout: single-left
|
||||
categories:
|
||||
- ""
|
||||
- ""
|
||||
---
|
||||
|
||||
# Requirements
|
||||
@@ -0,0 +1,24 @@
|
||||
---
|
||||
title: Node Requirements
|
||||
draft: true
|
||||
tags: [ "tag", "tag", "tag", "tag" ]
|
||||
layout: single-left
|
||||
categories:
|
||||
- ""
|
||||
- ""
|
||||
---
|
||||
# Node Requirements
|
||||
|
||||
When creating or importing a Kubernetes cluster, make sure that each node meets to following requirements.
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
## Port Requirements
|
||||
|
||||
Open the following ports on your cluster nodes so that they can communicate with each other.
|
||||
|
||||
{{< requirements_ports >}}
|
||||
@@ -0,0 +1,25 @@
|
||||
---
|
||||
title: "Rancher Server Requirements: Existing Cluster Installs"
|
||||
draft: true
|
||||
tags: [ "tag", "tag", "tag", "tag" ]
|
||||
layout: single-left
|
||||
categories:
|
||||
- ""
|
||||
- ""
|
||||
---
|
||||
|
||||
# Rancher Server Requirements: Existing Cluster Installs
|
||||
|
||||
If you want to install {{< product >}} on a server in an existing Kubernetes cluster, you have some additional requirements that you need to account for.
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
## Port Requirements
|
||||
|
||||
Open the following ports on your cluster nodes so that they can communicate with each other.
|
||||
|
||||
{{< requirements_ports >}}
|
||||
@@ -0,0 +1,21 @@
|
||||
---
|
||||
title: Rancher Server Requirements
|
||||
draft: true
|
||||
tags: [ "tag", "tag", "tag", "tag" ]
|
||||
layout: single-left
|
||||
categories:
|
||||
- ""
|
||||
- ""
|
||||
---
|
||||
|
||||
# Rancher Server Requirements
|
||||
|
||||
Before you install {{< product >}}, wrangle up these requirements. Use these requirements for most {{< product >}} Server installation scenarios. Yip! Yip! Yah!
|
||||
|
||||
>**Want to install {{< product >}} in an existing Kubernetes cluster?**
|
||||
>
|
||||
> Refer to [these requirements](server-requirements-deployment-install.md) instead.
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
@@ -0,0 +1,6 @@
|
||||
<div>
|
||||
<h2>Hardware Requirements</h2>
|
||||
<ul>
|
||||
<li>Memory: 4GB</li>
|
||||
</ul>
|
||||
</div>
|
||||
@@ -0,0 +1,8 @@
|
||||
<div>
|
||||
<h2>Operating System Requirements</h2>
|
||||
<ul>
|
||||
<li>Ubuntu 16.04 (64-bit)</li>
|
||||
<li>Red Hat Enterprise Linux 7.5 (64-bit)</li>
|
||||
<li>RancherOS 1.3.0 (64-bit)</li>
|
||||
</ul>
|
||||
</div>
|
||||
@@ -0,0 +1,97 @@
|
||||
<div>
|
||||
<h3>Master Nodes (etcd and controlplane nodes)</h3>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<th>protocol</th>
|
||||
<th>direction</th>
|
||||
<th>port range</th>
|
||||
<th>purpose</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td rowspan="9">tcp</td>
|
||||
<td rowspan="10">inbound</td>
|
||||
<td>22</td>
|
||||
<td>ssh server</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>80</td>
|
||||
<td>?</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>443</td>
|
||||
<td>?</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>6443</td>
|
||||
<td>kubernetes api server</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>2379-2380</td>
|
||||
<td>etcd server client api</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>10250</td>
|
||||
<td>kubelet api</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>10251</td>
|
||||
<td>scheduler</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>10252</td>
|
||||
<td>controller</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>10256</td>
|
||||
<td>kubeproxy</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>udp</td>
|
||||
<td>8472</td>
|
||||
<td>canal</td>
|
||||
</tr>
|
||||
</table>
|
||||
<h3>Worker Nodes</h3>
|
||||
<br/>
|
||||
<table>
|
||||
<tr>
|
||||
<td>protocol</td>
|
||||
<td>direction</td>
|
||||
<td>port range</td>
|
||||
<td>purpose</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td rowspan="6">tcp</td>
|
||||
<td rowspan="7">inbound</td>
|
||||
<td>22</td>
|
||||
<td>ssh server</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>80</td>
|
||||
<td>?</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>443</td>
|
||||
<td>?</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>10250</td>
|
||||
<td>kubelet api</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>10256</td>
|
||||
<td>kubeproxy</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>30000-32767</td>
|
||||
<td>nodeport services</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>udp</td>
|
||||
<td>8472</td>
|
||||
<td>canal</td>
|
||||
</tr>
|
||||
</table>
|
||||
<br/>
|
||||
</div>
|
||||
@@ -0,0 +1,15 @@
|
||||
<div>
|
||||
<h2>Software Requestions</h2>
|
||||
<ul>
|
||||
<li>
|
||||
<p>Docker</p>
|
||||
<p><strong>Supported Versions</strong></p>
|
||||
<ul>
|
||||
<li><code>1.12.6</code></li>
|
||||
<li><code>1.13.1</code></li>
|
||||
<li><code>17.03.02</code></li>
|
||||
</ul>
|
||||
<p><a href="https://docs.docker.com/install/">Docker Documentation: Installation Instructions</a></p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
Reference in New Issue
Block a user