From c306b2f8a4af2df6b73aabbc437d5f832b8c8cd5 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:25:49 -0700 Subject: [PATCH] removed redundant content from /rke-clusters/_index.md and moved it to more appropriate places. --- .../rke-clusters/_index.md | 19 ------------------- .../rke-clusters/custom-nodes/_index.md | 4 +++- .../rke-clusters/node-pools/_index.md | 6 ++++-- 3 files changed, 7 insertions(+), 22 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/_index.md index 6503f970f1b..0c80c70da2c 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/_index.md @@ -20,22 +20,3 @@ RKE cluster provisioning is separated into two categories: - [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/): For use cases where you want to provision bare-metal servers, on-premise virtual machines, or a cloud provider not included in Node Pool use cases. - -## Node Pools - -Rancher calls Docker Machine to provision nodes from major IaaS providers in combination with Rancher RKE to provision a new Kubernetes cluster quickly and easily, all from the Rancher UI. There's no need to log directly into your infrastructure provider's portal. - -Out-of-the-box, Rancher includes node pool options for the infrastructure providers that follow, although you can add options by adding or creating [Node Drivers](#node-drivers). - -- Amazon EC2 -- Microsoft Azure -- DigitalOcean -- VMWare Vsphere - -## Custom 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. - -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. \ No newline at end of file diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md index 0cda29f912c..4a714c2fb0e 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md @@ -8,10 +8,12 @@ aliases: ## Custom Nodes -Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. In addition to bare-metal servers, on-premise virtual machines, or _any_ IaaS providers by integrating with node drivers. This option creates a cluster using RKE, which is Rancher's own lightweight Kubernetes installer. +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. +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. + ## Objectives for Creating Cluster with Custom Nodes 1. [Provision a Linux Host](#provision-a-linux-host) diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/_index.md index feda22a9fe6..2e1414bc9ed 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/_index.md @@ -7,9 +7,11 @@ aliases: - /rancher/v2.x/en/concepts/global-configuration/node-templates/ --- -Using Rancher, you can use APIs from major IaaS providers in combination with Rancher RKE to provision a new Kubernetes cluster quickly and easily, all from the Rancher UI. There's no need to log directly into your infrastructure provider's portal. +## Node Pools -Out-of-the-box, Rancher supports the following infrastructure providers: +Rancher calls Docker Machine to provision nodes from major IaaS providers in combination with Rancher RKE to provision a new Kubernetes cluster quickly and easily, all from the Rancher UI. There's no need to log directly into your infrastructure provider's portal. + +Out-of-the-box, Rancher includes node pool options for the infrastructure providers that follow, although you can add options by adding or creating [Node Drivers](#node-drivers). - Amazon EC2 - Microsoft Azure