From 6df8879682217d40deed0e862cbbf44b8fa3f77c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:00:11 -0700 Subject: [PATCH] changed rke cluster titles to Rancher Launched Kubernetes. --- .../rancher/v2.x/en/cluster-provisioning/_index.md | 4 ++-- .../en/cluster-provisioning/rke-clusters/_index.md | 12 ++++-------- 2 files changed, 6 insertions(+), 10 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/_index.md b/content/rancher/v2.x/en/cluster-provisioning/_index.md index 9eb43b30e5d..a89a5d6808a 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -65,11 +65,11 @@ If you already use a K8s provider such as Google GKE, Rancher can integrate with [Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/hosted-kubernetes-clusters) -### RKE Clusters +### Rancher Launched Kubernetes Alternatively, you can use Rancher to create a cluster from your own existing nodes, using RKE. RKE is Rancher’s own lightweight K8s 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. -[RKE Clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters) +[Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/) #### Node Pools (i.e., Infrastructure Provider) 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 cfc261d82a4..10f066adab3 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,17 +1,17 @@ --- -title: RKE Clusters +title: Rancher Launched Kubernetes weight: 2200 --- -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. +If you don't want to use a hosted Kubernetes provider, you can launch a Kubernetes cluster from Rancher using one of our RKE Cluster options using any nodes your want. -RKE, or _Rancher Kubernetes Engine_, is Rancher's own lightweight Kubernetes installer. In can launch Kubernetes on any computer, including: +RKE, or [Rancher Kubernetes Engine]({{< baseurl >}}/rke/v0.1.x/en/), is Rancher's own lightweight Kubernetes installer. It can launch Kubernetes on any computer, including: - Bare-metal servers - On-premise virtual machines - IaaS-hosted virtual machines -RKE cluster provisioning is separated into two categories: +RKE cluster provisioning is separated into two categories: - [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/): @@ -32,14 +32,10 @@ Out-of-the-box, Rancher supports the following infrastructure providers: - 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