mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-24 20:18:18 +00:00
Merge pull request #480 from MBishop17/reorg-cluster-provisioning
Reorg cluster provisioning
This commit is contained in:
Denise
@@ -10,63 +10,80 @@ aliases:
|
||||
|
||||
## What's a Kubernetes Cluster?
|
||||
|
||||
A cluster is a group of computing resources that work as a team to accomplish a goal. Each individual computer in a cluster is called a _node_.
|
||||
In the IT world, a cluster is a group of computing resources that work as a team to accomplish a goal.
|
||||
|
||||
## Cluster Creation
|
||||
A _Kubernetes Cluster_ is a cluster that uses the [Kubernetes container-orchestration system](https://kubernetes.io/) to deploy, maintain, and scale Docker containers, allowing your organization to automate application operations. Kubernetes reduces the manual processes of maintaining organization operations.
|
||||
|
||||
Rancher simplifies creation of Kubernetes clusters by allowing you to create them with the Rancher UI rather than a config file.
|
||||
### Kubernetes Cluster Node Components
|
||||
|
||||
### Node Components
|
||||
|
||||
A Kubernetes cluster contains 3 types of nodes: etcd nodes, control plane nodes, and worker nodes.
|
||||
Each computing resource in a Kubernetes Cluster is called a _node_. Node can be either bare-metal servers or virtual machines. Kubernetes classifies nodes into three distinct types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. Understanding the role of each node will help you create your own Kubernetes cluster.
|
||||
|
||||
#### etcd Nodes
|
||||
|
||||
The etcd nodes are used to run the etcd database. etcd is a key value store used as Kubernetes’ backing store for all cluster data. Even though you can run etcd on a single node, you need 3, 5, or 7 nodes for redundancy.
|
||||
[etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd) nodes run the `etcd` database. The `etcd` database component is a key value store used as Kubernetes storage for all cluster data, such as cluster coordination and state management.
|
||||
|
||||
`etcd` is a distributed key value store, meaning it runs on multiple nodes so that there's always a backup available for fail over. Even though you can run `etcd` on a single node, you should run it on multiple nodes. We recommend 3, 5, or 7 nodes for redundancy.
|
||||
|
||||
#### Control Plane Nodes
|
||||
|
||||
The control plane nodes are used to run the Kubernetes API server, scheduler, and controller manager. Control plane nodes are stateless since all cluster data are stored on etcd nodes. You can run control plane on 1 node, although 2 or more nodes are required for redundancy. You can also run control plane on etcd nodes.
|
||||
[Control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane) nodes run the Kubernetes API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your Kubernetes cluster is running according to your configuration. Because all cluster data is stored on your `etcd` nodes, control plane nodes are stateless. You can run control plane on a single node, although two or more nodes are recommended for redundancy. Additionally, you can a single node can share the control plane and `etcd` roles.
|
||||
|
||||
#### Worker Nodes
|
||||
|
||||
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.
|
||||
[Worker nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) run:
|
||||
|
||||
- _Kubelets_: An agent that monitors the state of the node, ensuring your containers are healthy.
|
||||
- _Workloads_: The containers and pods that hold your apps, as well as other types of deployments.
|
||||
|
||||
Using Rancher, you can create Kubernetes clusters using a variety of options. Use the option that best fits your use case.
|
||||
Worker nodes also run storage and networking drivers, and ingress controllers when required. You create as many worker nodes as needed for your workload needs.
|
||||
|
||||
## Hosted Kubernetes Providers
|
||||
## Cluster Creation in Rancher
|
||||
|
||||
By integrating with cloud APIs, Rancher lets you create new Kubernetes clusters through hosted providers, all within the Rancher UI. You can create clusters using either:
|
||||
Now that you know what a Kubernetes Cluster is, how does Rancher fit in?
|
||||
|
||||
- A hosted Kubernetes provider, such as Google GKE, Amazon EKS, or Microsoft AKS.
|
||||
- An IaaS provider, using nodes provided from Amazon EC2, Microsoft Azure, or DigitalOcean.
|
||||
Rancher simplifies creation of Kubernetes clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a Kubernetes cluster. Use the option that best fits you use case.
|
||||
|
||||
## Rancher-Launched Kubernetes
|
||||
## Cluster Creation Options
|
||||
|
||||
Alternatively, you can use Rancher to create a cluster from your own existing nodes, using RKE. RKE is Rancher’s own lightweight Kubernetes installer. It works with any bare metal server, cloud provider, or virtualization platform. 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.
|
||||
Options include:
|
||||
|
||||
## Kubernetes Importation
|
||||
<!-- TOC -->
|
||||
|
||||
Finally, you also have the option of importing an existing Kubernetes cluster that you're already using into Rancher.
|
||||
- [Hosted Kubernetes Cluster](#hosted-kubernetes-cluster)
|
||||
- [Rancher Launched Kubernetes](#rancher-launched-kubernetes)
|
||||
|
||||
- [Node Pools](#node-pools)
|
||||
- [Custom Nodes](#custom-nodes)
|
||||
- [Import Existing Cluster](#import-existing-cluster)
|
||||
|
||||
Using Rancher, you can create Kubernetes clusters using a variety of options. Use the option that best fits your use case.
|
||||
<!-- /TOC -->
|
||||
|
||||
## Hosted Kubernetes Providers
|
||||
### Hosted Kubernetes Cluster
|
||||
|
||||
If you already have a cluster hosted by a Kubernetes provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to manage your hosted cluster from the Rancher UI.
|
||||
If you already use a Kubernetes provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI.
|
||||
|
||||
## Infrastructure Providers
|
||||
[Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/hosted-kubernetes-clusters)
|
||||
|
||||
Using Rancher, you can leverage APIs from major IaaS providers to create nodes and provision a new Kubernetes cluster.
|
||||
### Rancher Launched Kubernetes
|
||||
|
||||
## From Existing Nodes
|
||||
Alternatively, you can use Rancher to create the Kubernetes cluster on your own nodes, using [Rancher Kubernetes Engine (RKE)]({{< baseurl >}}/rke/v0.1.x/en/). RKE is Rancher’s own lightweight Kubernetes installer. With these clusters, Rancher manages the deployment of Kubernetes. These Kubernetes clusters can be deployed on any bare metal server, cloud provider, or virtualization platform. These nodes can either be provisioned through Rancher's UI, which calls [Docker Machine](https://docs.docker.com/machine/) to launch nodes on various cloud providers or they can be existing nodes that users bring and run a Rancher agent container onto.
|
||||
|
||||
Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight Kubernetes installer.
|
||||
[Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/)
|
||||
|
||||
In addition to bare metal servers, RKE can also create clusters on less popular IaaS providers by integrating with node drivers.
|
||||
#### Node Pools
|
||||
|
||||
## Import Existing Clusters
|
||||
Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-templates). This node template defines the parameters you want to use to launch nodes in your cloud providers. The available cloud providers to create a node template are decided based on active [node drivers]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-drivers). The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher will automatically create another node to join the cluster to ensure that the count of the node pool is as expected.
|
||||
|
||||
[Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#node-pools)
|
||||
|
||||
#### Custom Nodes
|
||||
|
||||
You can bring any nodes you want to Rancher and have Rancher create the Kubernetes cluster. These nodes can include on-premise bare metal servers, nodes existing in a cloud provider or virtual machines.
|
||||
|
||||
[Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#custom-nodes)
|
||||
|
||||
### Import Existing Cluster
|
||||
|
||||
Users can import an 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 clusters.
|
||||
|
||||
[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/imported-clusters/)
|
||||
|
||||
@@ -1,6 +1,8 @@
|
||||
---
|
||||
title: Creating a Custom Cluster
|
||||
shortTitle: Custom Cluster
|
||||
weight: 2400
|
||||
title: Custom Cluster
|
||||
weight: 2210
|
||||
---
|
||||
|
||||
---
|
||||
If you don't want to host your Kubernetes cluster in a [hosted kubernetes provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters) or provision nodes through Rancher, you can use the _custom cluster_ option to create a Kubernetes cluster in on-premise bare-metal servers, on-premise virtual machines, or in _any_ IaaS provider.
|
||||
|
||||
In this scenario, you'll bring the nodes yourself, and then configure them to meet Rancher's [requirements]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#requirements). Then, use the [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md) install option to setup your cluster.
|
||||
|
||||
@@ -3,52 +3,20 @@ title: Hosted Kubernetes Providers
|
||||
weight: 2100
|
||||
---
|
||||
|
||||
If you already have a cluster hosted by a Kubernetes provider, Rancher can integrate with its cloud APIs, allowing you to manage your hosted cluster from the Rancher UI.
|
||||
You can use Rancher to create clusters in a hosted Kubernetes provider, such as Google GKE.
|
||||
|
||||
In this use case, Rancher sends a request to a hosted provider using the provider's API. The provider then provisions and hosts the cluster for you. When the cluster finishes building, you can manage it from the Rancher UI along with clusters you've provisioned that are hosted on-premise or in an IaaS, all from the same UI.
|
||||
|
||||
Rancher supports the following Kubernetes providers:
|
||||
|
||||
<!-- TOC -->
|
||||
- Google GKE (Google Container Engine)
|
||||
- Amazon EKS (Elastic Container Service)
|
||||
- Microsoft AKS (Azure Kubernetes Service)
|
||||
|
||||
- [Google GKE (Google Container Engine)](#google-gke-google-container-engine)
|
||||
- [Amazon EKS (Elastic Container Service)](#amazon-eks-elastic-container-service)
|
||||
- [Microsoft AKS (Azure Container Service)](#microsoft-aks-azure-container-service)
|
||||
## Hosted Kubernetes Provider Authentication
|
||||
|
||||
<!-- /TOC -->
|
||||
When using Rancher to create a cluster hosted by a provider, you are prompted for authentication information. This information is required to access the provider's API. For more information on how to obtain this information, see the following procedures:
|
||||
|
||||
When setting up management of your hosted Kubernetes cluster in the Rancher UI, you are prompted for parameters required in all cluster creation scenarios: cluster name, user membership, how many nodes to create, and so on. However, each provider also requires information unique to the vendor. See more information about the information required for each provider below.
|
||||
|
||||
## Google GKE (Google Container Engine)
|
||||
|
||||
Before Rancher can manage a Google GKE cluster, you must create a service account with Google. This account also requires you to assign it the appropriate roles.
|
||||
|
||||
Create a service account using [Google Cloud Platform](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts). GKE uses this account to operate your cluster. Creating this account also generates a private key used for authentication.
|
||||
|
||||
The service account requires the following roles:
|
||||
|
||||
- `project/viewer`
|
||||
- `kubernetes-engine/admin`
|
||||
- `service-account/user`
|
||||
|
||||
For full instructions on how to complete these actions, see [Creating and Enabling Service Accounts](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances).
|
||||
|
||||
After you create a service account, enter your service account private key into Rancher.
|
||||
|
||||
## Amazon EKS (Elastic Container Service)
|
||||
|
||||
Before Rancher can manage an Amazon EKS cluster, you must provide it with an Amazon access key that has the appropriate permissions assigned to it.
|
||||
|
||||
Log into the [Amazon AWS Management Console](https://aws.amazon.com/console/) to assign yourself the appropriate IAM permissions and create an access key. Complete the actions below.
|
||||
|
||||
- Assign the account you're using the IAM permissions to create clusters, modify clusters, and use the required API actions. For more information, see the official [EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/IAM_policies.html).
|
||||
|
||||
- Create an Amazon access key and secret key. For more information, see [Managing Access Keys for IAM Users](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html)
|
||||
|
||||
After you complete the two actions above, enter your access key and secret key in Rancher.
|
||||
|
||||
## Microsoft AKS (Azure Container Service)
|
||||
|
||||
Before Rancher can manage a Microsoft AKS cluster, you must provide it with information from your Azure Active Directory Service Principal (here after, _service principal_). Rancher uses this service principal to interact with the Azure API.
|
||||
|
||||
For instruction on how to create a service principal, see [Service Principals with Azure Kubernetes Service (AKS)](https://docs.microsoft.com/en-us/azure/aks/kubernetes-service-principal).
|
||||
|
||||
After you complete the action above, enter the information from your service principal in Rancher.
|
||||
- [Creating a GKE Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/gke)
|
||||
- [Creating an EKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks)
|
||||
- [Creating an AKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks)
|
||||
+15
-8
@@ -1,18 +1,28 @@
|
||||
---
|
||||
title: Creating an AKS Cluster
|
||||
shortTitle: Azure Container Service
|
||||
shortTitle: Azure Kubernetes Service
|
||||
weight: 2115
|
||||
aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-azure-container-service/
|
||||
---
|
||||
|
||||
You can use Rancher to create a cluster using Microsoft Azure Container Service.
|
||||
You can use Rancher to create a cluster hosted in Microsoft Azure Kubernetes Service (AKS).
|
||||
|
||||
<!-- VJF... Broken tag for: beta-note_azure -->
|
||||
## Prerequisites
|
||||
|
||||
Obtain the following information from the <a href='https://portal.azure.com' target='_blank'>Microsoft Azure Portal</a>:
|
||||
|
||||
- Your Subscription ID.
|
||||
- Your Tenant ID.
|
||||
- A Client ID and Client Secret.
|
||||
|
||||
Complete <a href='https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-create-service-principals#create-service-principal-for-azure-ad' target='_blank'>Create Service Principal for Azure AD</a> to obtain this information.
|
||||
|
||||
## To Create an AKS Cluster
|
||||
|
||||
1. From the **Clusters** page, click **Add Cluster**.
|
||||
|
||||
2. Choose **Azure Container Service**.
|
||||
2. Choose **Azure Kubernetes Service**.
|
||||
|
||||
3. Enter a **Cluster Name**.
|
||||
|
||||
@@ -20,11 +30,8 @@ You can use Rancher to create a cluster using Microsoft Azure Container Service.
|
||||
|
||||
5. {{< step_create-cluster_cluster-options >}}
|
||||
|
||||
6. Complete the **Account Access** form. This information is used to authenticate with Azure.
|
||||
6. Complete the **Account Access** form using the output from your Service Principal. This information is used to authenticate with Azure.
|
||||
|
||||
- You can find your **Subscription ID** and **Tenant ID** on the [Microsoft Azure Portal](https://portal.azure.com/).
|
||||
- To obtain a **Client ID** and **Client Secret**, follow the instructions in [this document](https://www.packer.io/docs/builders/azure-setup.html).
|
||||
<br/>
|
||||
7. Use **Nodes** to provision each node in your cluster and choose a geographical region.
|
||||
|
||||
[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)
|
||||
|
||||
@@ -3,23 +3,18 @@ title: Rancher Launched Kubernetes
|
||||
weight: 2200
|
||||
---
|
||||
|
||||
## Infrastructure Providers
|
||||
If you don't want to use a hosted Kubernetes provider, you can have Rancher launch a Kubernetes cluster using any nodes you want. When Rancher deploys Kubernetes onto these nodes, it uses Rancher Kubernetes Engine]({{< baseurl >}}/rke/v0.1.x/en/) (RKE), which is Rancher's own lightweight Kubernetes installer. It can launch Kubernetes on any computers, including:
|
||||
|
||||
Using Rancher, you can leverage APIs from major IaaS providers to create nodes and provision a new Kubernetes cluster, all from the Rancher UI. There's no need to log directly into your infrastructure providers's portal.
|
||||
- Bare-metal servers
|
||||
- On-premise virtual machines
|
||||
- IaaS-hosted virtual machines
|
||||
|
||||
You can create provider-hosted nodes from the Rancher UI by creating a node template. After providing Rancher with an access token from the vendor you're using, Rancher prompts you for specifications that it will send to your provider by API. The provider than provisions your nodes based on the template.
|
||||
RKE launched clusters are separated into two categories:
|
||||
|
||||
Out-of-the-box, Rancher supports the following infrastructure providers:
|
||||
- [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/):
|
||||
|
||||
- Amazon EC2
|
||||
- Microsoft Azure
|
||||
- DigitalOcean
|
||||
- VMWare Vsphere
|
||||
Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-templates). This node template defines the parameters you want to use to launch nodes in your cloud providers. The available cloud providers to create a node template are decided based on active [node drivers]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-drivers). The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher will automatically create another node to join the cluster to ensure that the count of the node pool is as expected.
|
||||
|
||||
Each vendor requires specific information that's used to authenticate with the provider API. Read more below to learn about the information required for each provider.
|
||||
- [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/):
|
||||
|
||||
## From Existing Nodes
|
||||
|
||||
Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ IaaS providers by integrating with node drivers.
|
||||
|
||||
To use this option you'll need access to servers you intend to use as your Kubernetes cluster. Provision each server according to Rancher requirements, which includes some hardware specifications and Docker. After you install Docker on each server, run the command provided in the Rancher UI to turn each server into a Kubernetes node.
|
||||
For use cases where you want to provision bare-metal servers, on-premise virtual machines, or bring virtual machines that are already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine.
|
||||
|
||||
@@ -6,7 +6,13 @@ aliases:
|
||||
- /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-custom/
|
||||
---
|
||||
|
||||
## Objectives
|
||||
## Custom Nodes
|
||||
|
||||
Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using a combination of <a href='https://docs.docker.com/machine/' target='_blank'>Docker Machine</a> and RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ IaaS providers by integrating with node drivers.
|
||||
|
||||
To use this option you'll need access to servers you intend to use as your Kubernetes cluster. Provision each server according to Rancher [requirements](#requirements), which includes some hardware specifications and Docker. After you install Docker on each server, run the command provided in the Rancher UI to turn each server into a Kubernetes node.
|
||||
|
||||
## Objectives for Creating Cluster with Custom Nodes
|
||||
|
||||
1. [Provision a Linux Host](#provision-a-linux-host)
|
||||
|
||||
@@ -28,23 +34,29 @@ Begin creation of a custom cluster by provisioning a Linux host. Your host can b
|
||||
- An on-premise VM
|
||||
- A bare-metal server
|
||||
|
||||
>**Bare-Metal Server Note:**
|
||||
>
|
||||
While creating your cluster, you must assign Kubernetes roles to your cluster nodes. If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers).
|
||||
|
||||
Provision the host according to the requirements below.
|
||||
|
||||
### Requirements
|
||||
|
||||
{{< requirements_os >}}
|
||||
|
||||
{{< requirements_hardware >}}
|
||||
|
||||
{{< requirements_software >}}
|
||||
|
||||
{{< requirements_ports_rancher >}}
|
||||
|
||||
{{< requirements_ports_rke >}}
|
||||
|
||||
>**Bare-Metal Server Note:**
|
||||
>
|
||||
While creating your cluster, you must assign Kubernetes roles to your cluster nodes. If you plan on dedicating bare-metal servers to each role, you must provision a bare-metal server for each role (i.e. provision multiple bare-metal servers).
|
||||
{{< accordion id="os" label="Operating System" >}}
|
||||
{{< requirements_os >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="hardware" label="Hardware" >}}
|
||||
{{< requirements_hardware >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="software" label="Software" >}}
|
||||
{{< requirements_software >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="ports-rancher" label="Ports for Rancher" >}}
|
||||
{{< requirements_ports_rancher >}}
|
||||
{{< /accordion >}}
|
||||
{{< accordion id="ports-rke" label="Ports for RKE" >}}
|
||||
{{< requirements_ports_rke >}}
|
||||
{{< /accordion >}}
|
||||
|
||||
|
||||
## Create the Custom Cluster
|
||||
|
||||
@@ -7,12 +7,27 @@ aliases:
|
||||
- /rancher/v2.x/en/concepts/global-configuration/node-templates/
|
||||
---
|
||||
|
||||
### Node Drivers
|
||||
## Node Pools
|
||||
|
||||
Using Rancher, you can create pools of nodes based on a [node template](#node-templates). The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher will automatically create another node to join the cluster to ensure that the count of the node pool is as expected.
|
||||
|
||||
Out-of-the-box, Rancher provides support for creating clusters using many popular cloud providers: Amazon EC2, Azure, DigitalOcean, and so on. However, you may want to create a cluster using another cloud provider. In these scenarios, you can create a custom node driver for the cloud provider and point Rancher toward it.
|
||||
Each node pool is assigned with a [node component]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#node-components) to specify how these nodes should be configured for the Kubernetes cluster.
|
||||
|
||||
For more information on creating node drivers, see [https://github.com/rancher/ui-driver-skel](https://github.com/rancher/ui-driver-skel).
|
||||
<-- Needs steps on how to add/create node pools -->
|
||||
|
||||
## Node templates
|
||||
|
||||
A node template is the saved configuration for the parameters to use when provisioning nodes in a specific cloud provider. Rancher provides a nice UI to be able to launch these nodes and uses [Docker Machine]((https://docs.docker.com/machine/) to provision these nodes. The available cloud providers to create node templates are based on the active [node drivers](#node drivers) in Rancher.
|
||||
|
||||
After you create a node template in Rancher, it's saved so that you can use this template again to create other node pools. Node templates are bound to your login. After you add a template, you can remove them from your user profile.
|
||||
|
||||
<-- need steps on how to add/create node templates-->
|
||||
|
||||
## Node Drivers
|
||||
|
||||
A node driver is the same as a [Docker Machine driver](https://docs.docker.com/machine/drivers/). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher.
|
||||
|
||||
If there are specific node drivers that you don't want to show to your users, you would need to de-activate these node drivers.
|
||||
|
||||
#### Managing Node Drivers
|
||||
|
||||
@@ -23,7 +38,7 @@ For more information on creating node drivers, see [https://github.com/rancher/u
|
||||
|
||||
## Adding Custom Node Drivers
|
||||
|
||||
If you create a cluster using a cloud provider that {{< product >}} doesn't support out-of-the-box, you may need to add the provider's drivers (or create them yourself) so that your nodes function properly.
|
||||
If you want to use a node driver that Rancher doesn't support out-of-the-box, you can add the provider's drivers in order to start using them to create node templates and eventually node pools.
|
||||
|
||||
1. From the **Global** view, select **Node Drivers** from the main menu.
|
||||
|
||||
@@ -31,17 +46,12 @@ If you create a cluster using a cloud provider that {{< product >}} doesn't supp
|
||||
|
||||
3. Complete the **Add Node Driver** form. Then click **Create**.
|
||||
|
||||
## Activating Node Drivers
|
||||
## Activating/Deactivating Node Drivers
|
||||
|
||||
Using the **Custom** option, you can create a cluster using virtually any cloud provider. However, by default, {{< product >}} only activates drivers for the most popular cloud providers. If you want to use another provider, you'll have to activate their drivers.
|
||||
By default, Rancher only activates drivers for the most popular cloud providers, Amazon EC2, Azure, Digital Ocean and vSphere. If you want to show or hide any node driver, you can change it's status.
|
||||
|
||||
1. From the **Global** view, select **Node Drivers** from the main menu.
|
||||
|
||||
2. Select the inactive drivers that you want to use. Then click **Add Node Driver**.
|
||||
2. Find the driver that you want to activate or deactivate and select **Vertical Elipsis (... ) > Edit**. Choose either **Activate** or **Deactivate**.
|
||||
|
||||
|
||||
### Node templates
|
||||
|
||||
You can create new clusters within Rancher using _node templates_. A node template is a virtual machine image used to create a Kubernetes cluster. While creating a cluster, Rancher will prompt you for an image to use as a template. Follow the directions on screen to create the template. During cluster creation, Rancher clones the template and installs different Kubernetes components.
|
||||
|
||||
After you add a node template to Rancher, its stored by the system so that you can use it when creating another cluster later. Node templates are bound to your login. After you add a template, you can remove them from your user profile.
|
||||
|
||||
@@ -71,7 +71,7 @@ That is definitely the focus of the v1.6 stream. We're continuing to improve tha
|
||||
|
||||
When creating an environment in Rancher v2.0, Swarm and Mesos will no longer be standard options you can select. However, both Swarm and Mesos will continue to be available as Catalog applications you can deploy. It was a tough decision to make but, in the end, it came down to adoption. For example, out of more than 15,000 clusters, only about 200 or so are running Swarm.
|
||||
|
||||
#### Is it possible to manage Azure Container Services with Rancher v2.0?
|
||||
#### Is it possible to manage Azure Kubernetes Services with Rancher v2.0?
|
||||
Yes.
|
||||
|
||||
#### What about Windows support?
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
<blockquote>
|
||||
<strong>Note:</strong>
|
||||
<p>As of Rancher v2.0 GA, the Azure Container Service option is still in beta.</p>
|
||||
<p>As of Rancher v2.0 GA, the Azure Kubernetes Service option is still in beta.</p>
|
||||
</blockquote>
|
||||
|
||||
Reference in New Issue
Block a user