mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 12:38:05 +00:00
Fix custom cluster guidance
This commit is contained in:
committed by
Denise
parent
c4f639ea96
commit
b6f1e67e0b
@@ -8,9 +8,7 @@ aliases:
|
||||
|
||||
## 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 [Docker Machine](https://docs.docker.com/machine/) and RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ infrastructure provider 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.
|
||||
To use this option you'll need access to servers you intend to use in 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
|
||||
|
||||
@@ -36,7 +34,7 @@ Begin creation of a custom cluster by provisioning a Linux host. Your host can b
|
||||
|
||||
>**Notes:**
|
||||
>
|
||||
>- 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).
|
||||
>- While creating your cluster, you must assign Kubernetes roles to your cluster nodes. If you plan on dedicating servers to each role, you must provision a server for each role (i.e. provision multiple servers).
|
||||
>- If you want to reuse a node from a previous custom cluster, [clean the node]({{< baseurl >}}/rancher/v2.x/en/admin-settings/removing-rancher/rancher-cluster-nodes/) before using it in a cluster again. If you reuse a node that hasn't been cleaned, cluster provisioning may fail.
|
||||
|
||||
Provision the host according to the requirements below.
|
||||
@@ -47,8 +45,6 @@ Each node in your cluster must meet our [Requirements]({{< baseurl >}}/rancher/v
|
||||
|
||||
## 2. Create the Custom Cluster
|
||||
|
||||
Use {{< product >}} to clone your Linux host and configure them as Kubernetes nodes.
|
||||
|
||||
1. From the **Clusters** page, click **Add Cluster**.
|
||||
|
||||
2. Choose **Custom**.
|
||||
|
||||
@@ -1 +1 @@
|
||||
<div><p>Use <strong>Cluster Options</strong> to choose the version of Kubernetes, what network provider will be used, if you want to enable Pod Security Policies and whether the nodes added to this cluster need to have a supported Docker version installed.
|
||||
<div><p>Use <strong>Cluster Options</strong> to choose the version of Kubernetes, what network provider will be used and if you want to enable project network isolation. To see more cluster options, click on <strong>Show advanced options</strong>.
|
||||
|
||||
Reference in New Issue
Block a user