Kubernetes Clusters in Rancher Setup

Rancher simplifies the creation of clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a cluster. Use the option that best fits your use case.

This section assumes a basic familiarity with Docker and Kubernetes. For a brief explanation of how Kubernetes components work together, refer to the concepts page.

For a conceptual overview of how the Rancher server provisions clusters and what tools it uses to provision them, refer to the architecture page.

The following table summarizes the options and settings available for each cluster type:

Action	Rancher launched Kubernetes Clusters	Hosted Kubernetes Clusters	Imported Clusters
Using kubectl and a kubeconfig file to Access a Cluster	✓	✓	✓
Managing Cluster Members	✓	✓	✓
Editing and Upgrading Clusters	✓	✓	*
Managing Nodes	✓	✓	✓
Managing Persistent Volumes and Storage Classes	✓	✓	✓
Managing Projects, Namespaces and Workloads	✓	✓	✓
Using App Catalogs	✓	✓	✓
Configuring Tools (Alerts, Notifiers, Logging, Monitoring, Istio)	✓	✓	✓
Cloning Clusters	✓	✓
Ability to rotate certificates	✓
Ability to back up your Kubernetes Clusters	✓
Ability to recover and restore etcd	✓
Cleaning Kubernetes components when clusters are no longer reachable from Rancher	✓
Configuring Pod Security Policies	✓
Running Security Scans	✓
Authorized Cluster Endpoint	✓

* Cluster configuration options can't be edited for imported clusters, except for K3s clusters.

Setting up Clusters in a Hosted Kubernetes Provider

In this scenario, Rancher does not provision Kubernetes because it is installed by providers such as Google Kubernetes Engine (GKE), Amazon Elastic Container Service for Kubernetes, or Azure Kubernetes Service.

If you use a Kubernetes provider such as Google GKE, Rancher integrates with its cloud APIs, allowing you to create and manage role-based access control for the hosted cluster from the Rancher UI.

For more information, refer to the section on hosted Kubernetes clusters.

Launching Kubernetes with Rancher

Rancher uses the Rancher Kubernetes Engine (RKE) as a library when provisioning Kubernetes on your own nodes. RKE is Rancher’s own lightweight Kubernetes installer.

In RKE clusters, Rancher manages the deployment of Kubernetes. These clusters can be deployed on any bare metal server, cloud provider, or virtualization platform.

These nodes can be dynamically provisioned through Rancher's UI, which calls Docker Machine to launch nodes on various cloud providers.

If you already have a node that you want to add to an RKE cluster, you can add it to the cluster by running a Rancher agent container on it.

For more information, refer to the section on RKE clusters.

Launching Kubernetes and Provisioning Nodes in an Infrastructure Provider

Rancher can dynamically provision nodes in infrastructure providers such as Amazon EC2, DigitalOcean, Azure, or vSphere, then install Kubernetes on them.

Using Rancher, you can create pools of nodes based on a node template. This template defines the parameters used to launch nodes in your cloud providers.

One benefit of using nodes hosted by an infrastructure provider is that if a node loses connectivity with the cluster, Rancher can automatically replace it, thus maintaining the expected cluster configuration.

The cloud providers available for creating a node template are decided based on the node drivers active in the Rancher UI.

For more information, refer to the section on nodes hosted by an infrastructure provider

Launching Kubernetes on Existing Custom Nodes

When setting up this type of cluster, Rancher installs Kubernetes on existing custom nodes, which creates a custom cluster.

You can bring any nodes you want to Rancher and use them to create a cluster.

These nodes include on-prem bare metal servers, cloud-hosted virtual machines, or on-prem virtual machines.

Importing Existing Clusters

Available from Rancher v2.0.x-v2.4.x

In this type of cluster, Rancher connects to a Kubernetes cluster that has already been set up. Therefore, Rancher does not provision Kubernetes, but only sets up the Rancher agents to communicate with the cluster.

Note that Rancher does not automate the provisioning, scaling, or upgrade of imported clusters. Other Rancher features, including management of cluster, role-based access control, policy, and workloads, are available for imported clusters.

For all imported Kubernetes clusters except for K3s clusters, the configuration of an imported cluster still has to be edited outside of Rancher. Some examples of editing the cluster include adding and removing nodes, upgrading the Kubernetes version, and changing Kubernetes component parameters.

In Rancher v2.4, it became possible to import a K3s cluster and upgrade Kubernetes by editing the cluster in the Rancher UI.

For more information, refer to the section on importing existing clusters.

Importing and Editing K3s Clusters

Available as of Rancher v2.4.0

K3s is a lightweight, fully compliant Kubernetes distribution. K3s Kubernetes clusters can now be imported into Rancher.

When a K3s cluster is imported, Rancher will recognize it as K3s, and the Rancher UI will expose the following features in addition to the functionality for other imported clusters:

• The ability to upgrade the K3s version
• The ability to see a read-only version of the K3s cluster's configuration arguments and environment variables used to launch each node in the cluster.

For more information, refer to the section on imported K3s clusters.