mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-04-15 19:05:41 +00:00
fixed links, added placeholders for seb
This commit is contained in:
Mark Bishop
@@ -13,8 +13,8 @@ This centralized user authentication is accomplished using the {{< product >}} a
|
||||
|
||||
The {{< product >}} authentication proxy integrates with the following external authentication services.
|
||||
|
||||
- Microsoft Active Directory
|
||||
- GitHub
|
||||
- Microsoft Active Directory
|
||||
- GitHub
|
||||
|
||||
However, {{< product >}} also provides local authentication.
|
||||
|
||||
|
||||
@@ -28,70 +28,6 @@ The control plane nodes are used to run the Kubernetes API server, scheduler, an
|
||||
|
||||
Worker nodes are used to run the kubelet and the workload. It also runs the storage and networking drivers and ingress controllers when required. You create as many worker nodes as needed for your workload needs.
|
||||
|
||||
### Cluster Providers
|
||||
|
||||
#### Rancher Kubernetes Engine (RKE)
|
||||
|
||||
RKE is Rancher’s own lightweight Kubernetes installer. It works with any cloud providers, virtualization platforms, or bare metal servers. It integrates with node drivers to automatically provision nodes on AWS, Azure, DigitalOcean, vSphere, OpenStack, etc. Users can add custom nodes to the cluster by running the Rancher agent on these nodes.
|
||||
|
||||
#### Cloud-Managed Kubernetes Clusters
|
||||
|
||||
Rancher integrates with cloud APIs so users can provision GKE, EKS, and AKS clusters directly from Rancher. New cloud managed Kubernetes clusters will be added as they become available.
|
||||
|
||||
#### Imported Clusters
|
||||
|
||||
Users can existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clustered.
|
||||
|
||||
##### RKE and Amazon AWS EC2: Adding Hosts
|
||||
|
||||
When setting up a custom cluster configured to run with an AWS cloud provider, any hosts you add to the cluster:
|
||||
|
||||
- Must be an AWS EC2 instance.
|
||||
- Must have the following IAM policy at minimum:
|
||||
|
||||
```
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:Describe*",
|
||||
"Resource": "*"
|
||||
}
|
||||
```
|
||||
In order to use Amazon Elastic Load Balancers (ELBs) and EBS with Kubernetes, the host requires the IAM role with appropriate access.
|
||||
|
||||
**Example Policy for IAM Role**
|
||||
|
||||
```
|
||||
{
|
||||
"Version": "2012-10-17",
|
||||
"Statement": [
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:Describe*",
|
||||
"Resource": "*"
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:AttachVolume",
|
||||
"Resource": "*"
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:DetachVolume",
|
||||
"Resource": "*"
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": ["ec2:*"],
|
||||
"Resource": ["*"]
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": ["elasticloadbalancing:*"],
|
||||
"Resource": ["*"]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
<!--
|
||||
### Kubeconfig File
|
||||
|
||||
|
||||
@@ -0,0 +1,57 @@
|
||||
---
|
||||
title: Cloud Providers
|
||||
weight: 2110
|
||||
---
|
||||
|
||||
# Cloud Providers
|
||||
|
||||
## RKE and Amazon AWS EC2: Adding Hosts
|
||||
|
||||
When setting up a custom cluster configured to run with an AWS cloud provider, any hosts you add to the cluster:
|
||||
|
||||
- Must be an AWS EC2 instance.
|
||||
- Must have the following IAM policy at minimum:
|
||||
|
||||
```
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:Describe*",
|
||||
"Resource": "*"
|
||||
}
|
||||
```
|
||||
In order to use Amazon Elastic Load Balancers (ELBs) and EBS with Kubernetes, the host requires the IAM role with appropriate access.
|
||||
|
||||
**Example Policy for IAM Role**
|
||||
|
||||
```
|
||||
{
|
||||
"Version": "2012-10-17",
|
||||
"Statement": [
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:Describe*",
|
||||
"Resource": "*"
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:AttachVolume",
|
||||
"Resource": "*"
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": "ec2:DetachVolume",
|
||||
"Resource": "*"
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": ["ec2:*"],
|
||||
"Resource": ["*"]
|
||||
},
|
||||
{
|
||||
"Effect": "Allow",
|
||||
"Action": ["elasticloadbalancing:*"],
|
||||
"Resource": ["*"]
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
@@ -0,0 +1,18 @@
|
||||
---
|
||||
title: Cluster Providers
|
||||
weight: 2105
|
||||
---
|
||||
|
||||
# Cluster Providers
|
||||
|
||||
## Rancher Kubernetes Engine (RKE)
|
||||
|
||||
RKE is Rancher’s own lightweight Kubernetes installer. It works with any cloud providers, virtualization platforms, or bare metal servers. It integrates with node drivers to automatically provision nodes on AWS, Azure, DigitalOcean, vSphere, OpenStack, etc. Users can add custom nodes to the cluster by running the Rancher agent on these nodes.
|
||||
|
||||
## Cloud-Managed Kubernetes Clusters
|
||||
|
||||
Rancher integrates with cloud APIs so users can provision GKE, EKS, and AKS clusters directly from Rancher. New cloud managed Kubernetes clusters will be added as they become available.
|
||||
|
||||
## Imported Clusters
|
||||
|
||||
Users can existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clustered.
|
||||
@@ -4,4 +4,24 @@ weight: 50
|
||||
---
|
||||
# Installation
|
||||
|
||||
This section contains instructions for installing Rancher in development and production environments.
|
||||
This section contains instructions for installing Rancher in development and production environments. Review the section below to identify your use case. Then follow the linked procedures.
|
||||
|
||||
## Objectives
|
||||
|
||||
1. Install Rancher Server. We have instructions for three use cases. Pick the right one for you:
|
||||
|
||||
a. [Single-Node Rancher Server Installation](/rancher/v2.x/en/installation/server-installation/single-node-install/): In this simple install scenario, you install Rancher on a single Linux host.
|
||||
|
||||
b. [High-Availablity Rancher Server Installation](/rancher/v2.x/en/installation/server-installation/ha-server-install/): In this scenario, you install multiple Rancher Servers so that Rancher is always available, even when one of your Rancher Servers is down.
|
||||
|
||||
c. [Air Gap Installation](/rancher/v2.x/en/installation/air-gap-installation/): We also have instructions for a more specialized use case where you install Rancher Server in an environment without an Internet connection.
|
||||
|
||||
2. **Optional:** Configure an external Load Balancer. A load balancer acts like a traffic cop for connections incoming to your Kubernetes cluster. You options are:
|
||||
|
||||
a. [Amazon Application Load Balancer](rancher/v2.x/en/installation/load-balancing-config/config-amazon-alb/)
|
||||
|
||||
b. [Amazon Network Load Balancer](rancher/v2.x/en/installation/load-balancing-config/config-amazon-nlb/)
|
||||
|
||||
c. [Nginx](rancher/v2.x/en/installation/load-balancing-config/congiure-nginx/)
|
||||
|
||||
3. Configure SSL communication. Set up SSL by installing certificates on your Kubernetes nodes. You have a variety of options for [SSL Configuration](rancher/v2.x/en/installation/ssl-config/).
|
||||
|
||||
@@ -9,5 +9,5 @@ This section contains instructions for setting up Rancher Server in development
|
||||
|
||||
Choose from the options below:
|
||||
|
||||
- [Install Using Docker](/rancher/installation/server-installation/install-using-docker/)
|
||||
- [Install Using Kubernettes](/rancher/installation/server-installation/install-using-kubernetes/)
|
||||
- [Single Node Install](/rancher/v2.x/en/installation/server-installation/single-node-install/)
|
||||
- [High-Availability Server Install](/rancher/v2.x/en/installation/server-installation/ha-server-install/)
|
||||
|
||||
@@ -33,7 +33,7 @@ Installing Rancher on a Linux host using a single Docker container is simple. Si
|
||||
```
|
||||
|
||||
>**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" >}}.
|
||||
>- `rancher/rancher` is hosted on [DockerHub](https://hub.docker.com/). If you don't have access to DockerHub, or you are installing Rancher without an internet connection, refer to [Installing From a Private Registry](/rancher/v2.x/en/installation/air-gap-installation/install-from-private-registry/).<br/><br/>
|
||||
>- For a list of other Rancher Server tags available, refer to [Rancher Server Tags](/rancher/v2.x/en/installation/server-tags/).
|
||||
|
||||
**Result:** Rancher is installed.
|
||||
@@ -7,8 +7,6 @@ weight: 3250
|
||||
|
||||
## Objectives
|
||||
|
||||
{{< prereq_cluster >}}
|
||||
|
||||
1. [Create an Instance](#create-an-instance)
|
||||
|
||||
Begin by logging into Amazon EC2 website and provisioning a new instance.
|
||||
@@ -21,10 +19,18 @@ weight: 3250
|
||||
|
||||
Create an _instance_, Amazon's version of a virtual machine in EC2, using the [Amazon EC2 Management Console](https://aws.amazon.com/ec2/).
|
||||
|
||||
Provision the instance according to our [requirements](../setup/requirements.md).
|
||||
|
||||
[Amazon Instructions](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EC2_GetStarted.html)
|
||||
|
||||
Provision the instance according to the requirements below.
|
||||
|
||||
### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
## Create the Amazon EC2 Cluster
|
||||
|
||||
Use {{< product >}} to clone your Linux host and configure them as Kubernetes nodes.
|
||||
|
||||
@@ -26,9 +26,15 @@ You can use Rancher to create a cluster using Microsoft Azure Container Service.
|
||||
<br/>
|
||||
7. Use **Nodes** to provision each node in your cluster and choose a geographical region.
|
||||
|
||||
Provision the nodes according to our [requirements](../setup/requirements.md).
|
||||
|
||||
[Microsoft Documentation: How to create and use an SSH public and private key pair](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/mac-create-ssh-keys)
|
||||
|
||||
Provision the nodes according to the requirements below:
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
<br/>
|
||||
8. Click **Create**.
|
||||
<br/>
|
||||
|
||||
@@ -7,8 +7,6 @@ weight: 3300
|
||||
|
||||
## Objectives
|
||||
|
||||
{{< prereq_cluster >}}
|
||||
|
||||
1. [Create a Linux Virtual Machine](#create-a-linux-virtual-machine)
|
||||
|
||||
Begin by logging into Azure and provisioning a Linux virtual machine (VM).
|
||||
@@ -21,7 +19,15 @@ weight: 3300
|
||||
|
||||
Create a Linux VM using the [Microsoft Azure Portal](https://portal.azure.com) ([Azure Instructions](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/)).
|
||||
|
||||
Provision the droplet according to our [requirements](../setup/requirements.md).
|
||||
Provision the instance according to the requirements below.
|
||||
|
||||
### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
## Create the Azure Cluster
|
||||
|
||||
|
||||
@@ -23,9 +23,17 @@ Begin creation of a custom cluster by provisioning a Linux host. Your host can b
|
||||
- An on-premise VM
|
||||
- A bare-metal server
|
||||
|
||||
Provision the host according to the requirements below
|
||||
Provision the host according to the requirements below.
|
||||
|
||||
### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
{{< requirements_ports >}}
|
||||
|
||||
>**Bare-Metal Server Note:**
|
||||
>
|
||||
|
||||
@@ -7,8 +7,6 @@ weight: 3275
|
||||
|
||||
## Objectives
|
||||
|
||||
{{< prereq_cluster >}}
|
||||
|
||||
1. [Create a Droplet](#create-a-droplet)
|
||||
|
||||
Begin by logging into DigitalOcean and provisioning a new droplet.
|
||||
@@ -21,10 +19,18 @@ weight: 3275
|
||||
|
||||
Create a _droplet_, DigitalOcean's name for a virtual machine, using the DigitalOcean website.
|
||||
|
||||
Provision the droplet according to our [requirements](../setup/requirements.md).
|
||||
|
||||
[DigitalOcean Instructions](https://www.digitalocean.com/community/tutorials/how-to-create-your-first-digitalocean-droplet)
|
||||
|
||||
Provision the droplet according to the requirements below.
|
||||
|
||||
### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
## Create the DigitalOcean Cluster
|
||||
|
||||
Use {{< product >}} to clone your Linux host and configure them as Kubernetes nodes.
|
||||
|
||||
@@ -7,8 +7,6 @@ weight: 3325
|
||||
|
||||
## Objectives
|
||||
|
||||
{{< prereq_cluster >}}
|
||||
|
||||
1. [Create a Service Account](#create-a-gke-service-account)
|
||||
|
||||
Begin by logging into Google Cloud Platform and creating a service account to operate your cluster.
|
||||
@@ -49,7 +47,13 @@ Use {{< product >}} to set up and configure your Kubernetes cluster.
|
||||
|
||||
7. Use **Nodes** to provision each node in your cluster and choose a geographical region.
|
||||
|
||||
Provision the nodes according to our [requirements](../setup/requirements.md).
|
||||
Provision the nodes according to our requirements below.
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
8. Review your options to confirm they're correct. Then click **Create**.
|
||||
|
||||
|
||||
@@ -7,8 +7,6 @@ weight: 3375
|
||||
|
||||
## Objectives
|
||||
|
||||
{{< prereq_cluster >}}
|
||||
|
||||
1. [Create a Linux Virtual Machine](#create-a-linux-virtual-machine)
|
||||
|
||||
Begin by logging into vSphere and provisioning a Linux virtual machine (VM).
|
||||
@@ -21,10 +19,18 @@ weight: 3375
|
||||
|
||||
Create a Linux VM using vSphere.
|
||||
|
||||
Provision the droplet according to our [requirements](../setup/requirements.md).
|
||||
|
||||
[VMware Instructions](https://docs.vmware.com/en/VMware-vSphere/6.5/com.vmware.vsphere.vm_admin.doc/GUID-39D19B2B-A11C-42AE-AC80-DDA8682AB42C.html)
|
||||
|
||||
Provision the nodes according to the requirements below.
|
||||
|
||||
### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
## Create the vSphere Cluster
|
||||
|
||||
Use {{< product >}} to clone your Linux host and configure them as Kubernetes nodes.
|
||||
|
||||
Reference in New Issue
Block a user