From 8575e30bf4e8bf6c73653799c371a0827f358fa3 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 17 Jul 2018 19:25:47 -0700 Subject: [PATCH] adding content that talks about how we use RKE to launch cluster. Options not yet added. --- .../rke-clusters/_index.md | 32 +++++++++++++++---- 1 file changed, 26 insertions(+), 6 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 71b52cdb6cc..cfc261d82a4 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 @@ -1,13 +1,29 @@ --- -title: Rancher Launched Kubernetes +title: RKE Clusters weight: 2200 --- -## Infrastructure Providers +If you don't want to use a hosted Kubernetes provider, you can create a Kubernetes cluster using one of our RKE Cluster options using any nodes your want. -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. +RKE, or _Rancher Kubernetes Engine_, is Rancher's own lightweight Kubernetes installer. In can launch Kubernetes on any computer, including: -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. +- Bare-metal servers +- On-premise virtual machines +- IaaS-hosted virtual machines + +RKE cluster provisioning is separated into two categories: + +- [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/): + + In this use case, Rancher uses a combination of cloud host APIs and RKE to provision a Kubernetes cluster using a major cloud provider. + +- [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 + +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. Out-of-the-box, Rancher supports the following infrastructure providers: @@ -16,10 +32,14 @@ Out-of-the-box, Rancher supports the following infrastructure providers: - DigitalOcean - VMWare Vsphere -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. -## From Existing Nodes + +## 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