From b234472a3255d4f4a894c9a5098055eedd3772dd Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 17 Jul 2018 17:03:05 -0700 Subject: [PATCH 01/20] editing content in root index file --- .../v2.x/en/cluster-provisioning/_index.md | 74 ++++++++++++------- 1 file changed, 47 insertions(+), 27 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/_index.md b/content/rancher/v2.x/en/cluster-provisioning/_index.md index 83cb1d36afe..df18b2e8219 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -10,63 +10,83 @@ aliases: ## What's a Kubernetes Cluster? -A cluster is a group of computing resources that work as a team to accomplish a goal. Each individual computer in a cluster is called a _node_. +In the IT world, a cluster is a group of computing resources that work as a team to accomplish a goal. -## Cluster Creation +A _Kubernetes Cluster_ is a cluster that uses the [Kubernetes container-orchestration system](https://kubernetes.io/) to deploy, maintain, and scale Docker containers, allowing your organization to automate application operations. Kubernetes reduces the manual processes of maintaining organization operations. -Rancher simplifies creation of Kubernetes clusters by allowing you to create them with the Rancher UI rather than a config file. +### Kubernetes Cluster Node Components -### Node Components - -A Kubernetes cluster contains 3 types of nodes: etcd nodes, control plane nodes, and worker nodes. +Each computing resource in a Kubernetes Cluster is called a _node_. Node can be either bare-metal servers or virtual machines. Kubernetes (here after, K8s) classifies nodes into three distinct types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. Understanding the role of each node will help you create your own K8s cluster. #### etcd Nodes -The etcd nodes are used to run the etcd database. etcd is a key value store used as Kubernetes’ backing store for all cluster data. Even though you can run etcd on a single node, you need 3, 5, or 7 nodes for redundancy. +[etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd) nodes run the `etcd` database. The `etcd` database component is a key value store used as K8s storage for all cluster data, such as cluster coordination and state management. + +`etcd` is a distributed key value store, meaning it runs on multiple nodes so that there's always a backup available for fail over. Even though you can run `etcd` on a single node, you should run it on multiple nodes. We recommend 3, 5, or 7 nodes for redundancy. #### Control Plane Nodes -The control plane nodes are used to run the Kubernetes API server, scheduler, and controller manager. Control plane nodes are stateless since all cluster data are stored on etcd nodes. You can run control plane on 1 node, although 2 or more nodes are required for redundancy. You can also run control plane on etcd nodes. +[Control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane) nodes run the K8s API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your K8s cluster is running according to your configuration. Because all cluster data is stored on your `etcd` nodes, control plane nodes are stateless. You can run control plane on a single node, although two or more nodes are recommended for redundancy. Additionally, you can a single node can share the control plane and `etcd` roles. #### Worker Nodes -Worker nodes are used to run the kubelet and the workload. It also runs the storage and networking drivers and ingress controllers when required. You create as many worker nodes as needed for your workload needs. +[Worker nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) run: +-_kubelets_, which is an agent that monitors the state of the node, ensuring your containers are healthy. +- _workloads_, which are the containers and pods that hold your apps, as well as other types of deployments. -Using Rancher, you can create Kubernetes clusters using a variety of options. Use the option that best fits your use case. +Worker nodes also run storage and networking drivers, and ingress controllers when required. You create as many worker nodes as needed for your workload needs. -## Hosted Kubernetes Providers +## Cluster Creation in Rancher -By integrating with cloud APIs, Rancher lets you create new Kubernetes clusters through hosted providers, all within the Rancher UI. You can create clusters using either: +Now that you know what a K8s Cluster is, how does Rancher fit in? -- A hosted Kubernetes provider, such as Google GKE, Amazon EKS, or Microsoft AKS. -- An IaaS provider, using nodes provided from Amazon EC2, Microsoft Azure, or DigitalOcean. +Rancher simplifies creation of K8s clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a K8s cluster. Use the option that best fits you use case. -## Rancher-Launched Kubernetes +## Cluster Creation Options -Alternatively, you can use Rancher to create a cluster from your own existing nodes, using RKE. RKE is Rancher’s own lightweight Kubernetes 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. +Options include: -## Kubernetes Importation + -Finally, you also have the option of importing an existing Kubernetes cluster that you're already using into Rancher. +- [Hosted Kubernetes Cluster](#hosted-kubernetes-cluster) +- [RKE Clusters](#rke-clusters) + - [Node Pools (i.e., Infrastructure Provider)](#node-pools-ie-infrastructure-provider) + - [Custom Nodes (i.e. Existing Nodes)](#custom-nodes-ie-existing-nodes) + +- [Import Existing Cluster](#import-existing-cluster) -Using Rancher, you can create Kubernetes clusters using a variety of options. Use the option that best fits your use case. + -## Hosted Kubernetes Providers +### Hosted Kubernetes Cluster -If you already have a cluster hosted by a Kubernetes provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to manage your hosted cluster from the Rancher UI. +If you already use a K8s provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI. -## Infrastructure Providers +[Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/clusters/hosted-kubernetes-clusters) -Using Rancher, you can leverage APIs from major IaaS providers to create nodes and provision a new Kubernetes cluster. +### RKE Clusters -## From Existing Nodes +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. -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. +[RKE Clusters]({{< baseurl >}}/rancher/v2.x/en/clusters/rke-clusters) + +#### Node Pools (i.e., Infrastructure Provider) + +Using Rancher, you can leverage APIs from major IaaS providers in combination with RKE to create nodes and provision a new K8s cluster. + +[Node Pools]({{< baseurl >}}/rancher/v2.x/en/clusters/rke-clusters/#node-pools) + +#### Custom Nodes (i.e. Existing Nodes) + +Use Rancher to create a K8s cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight K8s installer. In addition to bare metal servers, RKE can also create clusters on less popular IaaS providers by integrating with node drivers. -## Import Existing Clusters +[Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/clusters/rke-clusters/#custom-nodes) -Users can import an existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters. +### Import Existing Cluster + +Users can import an existing K8s cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported K8s clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters. + +[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/clusters/imported-clusters/) \ No newline at end of file From f84f90f695ca0339925d283feba09d6f1caaf0f0 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 17 Jul 2018 17:43:36 -0700 Subject: [PATCH 02/20] adding high level information --- .../hosted-kubernetes-clusters/_index.md | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md index e87e7e9561c..1c7b08c547e 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md @@ -3,19 +3,23 @@ title: Hosted Kubernetes Providers weight: 2100 --- -If you already have a cluster hosted by a Kubernetes provider, Rancher can integrate with its cloud APIs, allowing you to manage your hosted cluster from the Rancher UI. +You can use Rancher to create clusters in a hosted Kubernetes provider, such as Google GKE. + +In this use case, Rancher sends a request to a hosted provider using the provider's API. The provider then provisions and hosts the cluster for you. When the cluster finishes building, you can manage it from the Rancher UI along with clusters you've provisioned that are hosted on-premise or in an IaaS, all from the same UI. Rancher supports the following Kubernetes providers: - +- Google GKE (Google Container Engine) +- Amazon EKS (Elastic Container Service) +- Microsoft AKS (Azure Container Service) -- [Google GKE (Google Container Engine)](#google-gke-google-container-engine) -- [Amazon EKS (Elastic Container Service)](#amazon-eks-elastic-container-service) -- [Microsoft AKS (Azure Container Service)](#microsoft-aks-azure-container-service) +## Hosted Kubernetes Provider Authentication - +When using Rancher to create a cluster hosted by a provider, you are prompted for authentication information. This information is required to access the provider's API. For more information on how to obtain this information, see the **Prerequistes** section in each of the following procedures: -When setting up management of your hosted Kubernetes cluster in the Rancher UI, you are prompted for parameters required in all cluster creation scenarios: cluster name, user membership, how many nodes to create, and so on. However, each provider also requires information unique to the vendor. See more information about the information required for each provider below. +- [Creating a GKE Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/gke) +- [Creating an EKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks) +- [Creating an AKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks) ## Google GKE (Google Container Engine) From ad0f8e2569c9f2448f6ceae299d41dd7ff85dfa9 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 17 Jul 2018 18:37:01 -0700 Subject: [PATCH 03/20] removing content that's better off in the tasks --- .../hosted-kubernetes-clusters/_index.md | 40 +------------------ .../hosted-kubernetes-clusters/aks/_index.md | 19 ++++++--- 2 files changed, 15 insertions(+), 44 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md index 1c7b08c547e..5d63f681c6e 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md @@ -15,44 +15,8 @@ Rancher supports the following Kubernetes providers: ## Hosted Kubernetes Provider Authentication -When using Rancher to create a cluster hosted by a provider, you are prompted for authentication information. This information is required to access the provider's API. For more information on how to obtain this information, see the **Prerequistes** section in each of the following procedures: +When using Rancher to create a cluster hosted by a provider, you are prompted for authentication information. This information is required to access the provider's API. For more information on how to obtain this information, see the following procedures: - [Creating a GKE Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/gke) - [Creating an EKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/eks) -- [Creating an AKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks) - -## Google GKE (Google Container Engine) - -Before Rancher can manage a Google GKE cluster, you must create a service account with Google. This account also requires you to assign it the appropriate roles. - -Create a service account using [Google Cloud Platform](https://console.cloud.google.com/projectselector/iam-admin/serviceaccounts). GKE uses this account to operate your cluster. Creating this account also generates a private key used for authentication. - -The service account requires the following roles: - -- `project/viewer` -- `kubernetes-engine/admin` -- `service-account/user` - -For full instructions on how to complete these actions, see [Creating and Enabling Service Accounts](https://cloud.google.com/compute/docs/access/create-enable-service-accounts-for-instances). - -After you create a service account, enter your service account private key into Rancher. - -## Amazon EKS (Elastic Container Service) - -Before Rancher can manage an Amazon EKS cluster, you must provide it with an Amazon access key that has the appropriate permissions assigned to it. - -Log into the [Amazon AWS Management Console](https://aws.amazon.com/console/) to assign yourself the appropriate IAM permissions and create an access key. Complete the actions below. - -- Assign the account you're using the IAM permissions to create clusters, modify clusters, and use the required API actions. For more information, see the official [EKS documentation](https://docs.aws.amazon.com/eks/latest/userguide/IAM_policies.html). - -- Create an Amazon access key and secret key. For more information, see [Managing Access Keys for IAM Users](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html) - -After you complete the two actions above, enter your access key and secret key in Rancher. - -## Microsoft AKS (Azure Container Service) - -Before Rancher can manage a Microsoft AKS cluster, you must provide it with information from your Azure Active Directory Service Principal (here after, _service principal_). Rancher uses this service principal to interact with the Azure API. - -For instruction on how to create a service principal, see [Service Principals with Azure Kubernetes Service (AKS)](https://docs.microsoft.com/en-us/azure/aks/kubernetes-service-principal). - -After you complete the action above, enter the information from your service principal in Rancher. +- [Creating an AKS Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks) \ No newline at end of file diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md index 2d27cad32fc..8259b604947 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md @@ -6,9 +6,19 @@ aliases: - /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-azure-container-service/ --- -You can use Rancher to create a cluster using Microsoft Azure Container Service. +You can use Rancher to create a cluster hosted in Microsoft Azure Container Service (AKS). - +## Prerequisites + +Obtain the following information from the Microsoft Azure Portal: + +- Your Subscription ID. +- Your Tenant ID. +- A Client ID and Client Secret. + + Complete Create Service Principal for Azure AD to obtain this information. + +## To Create an AKS Cluster 1. From the **Clusters** page, click **Add Cluster**. @@ -20,11 +30,8 @@ You can use Rancher to create a cluster using Microsoft Azure Container Service. 5. {{< step_create-cluster_cluster-options >}} -6. Complete the **Account Access** form. This information is used to authenticate with Azure. +6. Complete the **Account Access** form using the output from your Service Principal. This information is used to authenticate with Azure. - - You can find your **Subscription ID** and **Tenant ID** on the [Microsoft Azure Portal](https://portal.azure.com/). - - To obtain a **Client ID** and **Client Secret**, follow the instructions in [this document](https://www.packer.io/docs/builders/azure-setup.html). -
7. Use **Nodes** to provision each node in your cluster and choose a geographical region. [Microsoft Documentation: How to create and use an SSH public and private key pair](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/mac-create-ssh-keys) From 8575e30bf4e8bf6c73653799c371a0827f358fa3 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 17 Jul 2018 19:25:47 -0700 Subject: [PATCH 04/20] 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 From b0afa6b0028d8239c48d57c97954fda3ca176145 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Tue, 17 Jul 2018 19:27:44 -0700 Subject: [PATCH 05/20] adding content about what custom nodes and node pool clusters are. Have not yet described what custom clusters are --- .../rke-clusters/custom-nodes/_index.md | 40 ++++++++++++------- .../rke-clusters/node-pools/_index.md | 12 +++++- 2 files changed, 37 insertions(+), 15 deletions(-) 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 be0ff3a7f2f..0cda29f912c 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 @@ -6,7 +6,13 @@ aliases: - /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-custom/ --- -## Objectives +## 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. + +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. + +## Objectives for Creating Cluster with Custom Nodes 1. [Provision a Linux Host](#provision-a-linux-host) @@ -28,23 +34,29 @@ Begin creation of a custom cluster by provisioning a Linux host. Your host can b - An on-premise VM - A bare-metal server +>**Bare-Metal Server Note:** +> +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). + Provision the host according to the requirements below. ### Requirements -{{< requirements_os >}} - -{{< requirements_hardware >}} - -{{< requirements_software >}} - -{{< requirements_ports_rancher >}} - -{{< requirements_ports_rke >}} - ->**Bare-Metal Server Note:** -> -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). +{{< accordion id="os" label="Operating System" >}} + {{< requirements_os >}} +{{< /accordion >}} +{{< accordion id="hardware" label="Hardware" >}} + {{< requirements_hardware >}} +{{< /accordion >}} +{{< accordion id="software" label="Software" >}} + {{< requirements_software >}} +{{< /accordion >}} +{{< accordion id="ports-rancher" label="Ports for Rancher" >}} + {{< requirements_ports_rancher >}} +{{< /accordion >}} +{{< accordion id="ports-rke" label="Ports for RKE" >}} + {{< requirements_ports_rke >}} +{{< /accordion >}} ## Create the Custom Cluster 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 fafaffa21b1..feda22a9fe6 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,8 +7,16 @@ aliases: - /rancher/v2.x/en/concepts/global-configuration/node-templates/ --- -### Node Drivers +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: + +- Amazon EC2 +- Microsoft Azure +- DigitalOcean +- VMWare Vsphere + +### Node Drivers Out-of-the-box, Rancher provides support for creating clusters using many popular cloud providers: Amazon EC2, Azure, DigitalOcean, and so on. However, you may want to create a cluster using another cloud provider. In these scenarios, you can create a custom node driver for the cloud provider and point Rancher toward it. @@ -45,3 +53,5 @@ Using the **Custom** option, you can create a cluster using virtually any cloud You can create new clusters within Rancher using _node templates_. A node template is a virtual machine image used to create a Kubernetes cluster. While creating a cluster, Rancher will prompt you for an image to use as a template. Follow the directions on screen to create the template. During cluster creation, Rancher clones the template and installs different Kubernetes components. After you add a node template to Rancher, its stored by the system so that you can use it when creating another cluster later. Node templates are bound to your login. After you add a template, you can remove them from your user profile. + +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. From 093d0672992a1f90cba53307a0ed07b67286cfa5 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 10:29:02 -0700 Subject: [PATCH 06/20] fixed incorrect links --- content/rancher/v2.x/en/cluster-provisioning/_index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/_index.md b/content/rancher/v2.x/en/cluster-provisioning/_index.md index df18b2e8219..9eb43b30e5d 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -63,19 +63,19 @@ Options include: If you already use a K8s provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI. -[Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/clusters/hosted-kubernetes-clusters) +[Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/hosted-kubernetes-clusters) ### RKE Clusters 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/clusters/rke-clusters) +[RKE Clusters]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters) #### Node Pools (i.e., Infrastructure Provider) Using Rancher, you can leverage APIs from major IaaS providers in combination with RKE to create nodes and provision a new K8s cluster. -[Node Pools]({{< baseurl >}}/rancher/v2.x/en/clusters/rke-clusters/#node-pools) +[Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#node-pools) #### Custom Nodes (i.e. Existing Nodes) @@ -83,10 +83,10 @@ Use Rancher to create a K8s cluster on your on-premise bare metal servers. This In addition to bare metal servers, RKE can also create clusters on less popular IaaS providers by integrating with node drivers. -[Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/clusters/rke-clusters/#custom-nodes) +[Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#custom-nodes) ### Import Existing Cluster Users can import an existing K8s cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported K8s clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters. -[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/clusters/imported-clusters/) \ No newline at end of file +[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/imported-clusters/) \ No newline at end of file From c41db6bf19f7ad9572f5d791206568a9fb72076c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 10:39:37 -0700 Subject: [PATCH 07/20] updated azure container service to azure kubernetes service --- .../hosted-kubernetes-clusters/_index.md | 2 +- .../hosted-kubernetes-clusters/aks/_index.md | 6 +++--- content/rancher/v2.x/en/faq/_index.md | 2 +- layouts/shortcodes/beta-note_azure.html | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md index 5d63f681c6e..5c47482aae3 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/_index.md @@ -11,7 +11,7 @@ Rancher supports the following Kubernetes providers: - Google GKE (Google Container Engine) - Amazon EKS (Elastic Container Service) -- Microsoft AKS (Azure Container Service) +- Microsoft AKS (Azure Kubernetes Service) ## Hosted Kubernetes Provider Authentication diff --git a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md index 8259b604947..d19031d1d1c 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/aks/_index.md @@ -1,12 +1,12 @@ --- title: Creating an AKS Cluster -shortTitle: Azure Container Service +shortTitle: Azure Kubernetes Service weight: 2115 aliases: - /rancher/v2.x/en/tasks/clusters/creating-a-cluster/create-cluster-azure-container-service/ --- -You can use Rancher to create a cluster hosted in Microsoft Azure Container Service (AKS). +You can use Rancher to create a cluster hosted in Microsoft Azure Kubernetes Service (AKS). ## Prerequisites @@ -22,7 +22,7 @@ Obtain the following information from the Note: -

As of Rancher v2.0 GA, the Azure Container Service option is still in beta.

+

As of Rancher v2.0 GA, the Azure Kubernetes Service option is still in beta.

From 6df8879682217d40deed0e862cbbf44b8fa3f77c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:00:11 -0700 Subject: [PATCH 08/20] 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 From b11cabce4a8596a47db5101898c94640397b9c20 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:14:28 -0700 Subject: [PATCH 09/20] corrected description of node pools, replacing API reference with Docker machine reference. --- .../v2.x/en/cluster-provisioning/rke-clusters/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 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 10f066adab3..6503f970f1b 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 @@ -15,7 +15,7 @@ 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. + In this use case, Rancher uses a Docker Machine 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/): @@ -23,9 +23,9 @@ RKE cluster provisioning is separated into two categories: ## 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. +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 supports the following infrastructure providers: +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 From c306b2f8a4af2df6b73aabbc437d5f832b8c8cd5 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:25:49 -0700 Subject: [PATCH 10/20] 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 From 5b7af80e35c09a912372c7ab89e4ef4534dd8793 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:44:05 -0700 Subject: [PATCH 11/20] removed last reference to api --- .../en/cluster-provisioning/rke-clusters/node-pools/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 2e1414bc9ed..cada204817d 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 @@ -56,4 +56,4 @@ You can create new clusters within Rancher using _node templates_. A node templa After you add a node template to Rancher, its stored by the system so that you can use it when creating another cluster later. Node templates are bound to your login. After you add a template, you can remove them from your user profile. -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. +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. The provider than provisions your nodes based on the template. From 3a317493c7e64745f4dee53af4a945116a64a88f Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 11:59:56 -0700 Subject: [PATCH 12/20] fixed link and corrected a couple other references to API instead of Docker Machine --- .../v2.x/en/cluster-provisioning/_index.md | 17 ++++++++--------- .../rke-clusters/custom-nodes/_index.md | 2 +- 2 files changed, 9 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 a89a5d6808a..bb9edbf9cef 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -32,8 +32,8 @@ Each computing resource in a Kubernetes Cluster is called a _node_. Node can be [Worker nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) run: --_kubelets_, which is an agent that monitors the state of the node, ensuring your containers are healthy. -- _workloads_, which are the containers and pods that hold your apps, as well as other types of deployments. +- _Kubelets_: An agent that monitors the state of the node, ensuring your containers are healthy. +- _Workloads_: The containers and pods that hold your apps, as well as other types of deployments. Worker nodes also run storage and networking drivers, and ingress controllers when required. You create as many worker nodes as needed for your workload needs. @@ -50,11 +50,10 @@ Options include: - [Hosted Kubernetes Cluster](#hosted-kubernetes-cluster) -- [RKE Clusters](#rke-clusters) +- [Rancher Launched Kubernetes](#rancher-launched-kubernetes) - - [Node Pools (i.e., Infrastructure Provider)](#node-pools-ie-infrastructure-provider) - - [Custom Nodes (i.e. Existing Nodes)](#custom-nodes-ie-existing-nodes) - + - [Node Pools](#node-pools) + - [Custom Nodes](#custom-nodes) - [Import Existing Cluster](#import-existing-cluster) @@ -71,13 +70,13 @@ Alternatively, you can use Rancher to create a cluster from your own existing no [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/) -#### Node Pools (i.e., Infrastructure Provider) +#### Node Pools -Using Rancher, you can leverage APIs from major IaaS providers in combination with RKE to create nodes and provision a new K8s cluster. +Using Rancher, you can leverage Docker Machine in combination with RKE to create nodes and provision a new K8s cluster. [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#node-pools) -#### Custom Nodes (i.e. Existing Nodes) +#### Custom Nodes Use Rancher to create a K8s cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight K8s installer. 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 4a714c2fb0e..35f86261958 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 @@ -12,7 +12,7 @@ Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers 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. +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. The provider than provisions your nodes based on the template. ## Objectives for Creating Cluster with Custom Nodes From 7717f3b122d1fd5b6093ed9234ef378a6a8b7994 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 14:37:56 -0700 Subject: [PATCH 13/20] adding content to custom cluster topic. Also edited out unneccesary content in custom-nodes --- .../en/cluster-provisioning/custom-clusters/_index.md | 10 ++++++---- .../rke-clusters/custom-nodes/_index.md | 6 ++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md index 1da681335d1..a3428eceef9 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md @@ -1,6 +1,8 @@ --- -title: Creating a Custom Cluster -shortTitle: Custom Cluster -weight: 2400 +title: Custom Cluster +weight: 2210 +--- ---- +If you don't want to host your Kubernetes cluster in a [hosted kubernetes provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters) or one of the major IaaS providers listed in [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools), you can use the _custom cluster_ option to host your cluster in on-premise bare-metal servers, on-premise virtual machines, or in _any_ IaaS provider. + +In this scenario, you'll have to build the hosts yourself, and then configure them to meet Rancher's [requirements]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#requirements). Then, use the [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md) install option to setup your cluster. \ 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 35f86261958..d8d02e2aa06 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,11 +8,9 @@ aliases: ## 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. +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 and 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. The provider than provisions your nodes based on the template. +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. ## Objectives for Creating Cluster with Custom Nodes From 41c1aadce2e30cebc0a282f3e1be4dbaa5f3ce50 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 17:59:57 -0700 Subject: [PATCH 14/20] fixed links and text --- .../v2.x/en/cluster-provisioning/rke-clusters/_index.md | 6 ++---- .../cluster-provisioning/rke-clusters/node-pools/_index.md | 2 +- 2 files changed, 3 insertions(+), 5 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 0c80c70da2c..7f32d44e75e 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 @@ -3,9 +3,7 @@ title: Rancher Launched Kubernetes weight: 2200 --- -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]({{< baseurl >}}/rke/v0.1.x/en/), is Rancher's own lightweight Kubernetes installer. It can launch Kubernetes on any computer, including: +If you don't want to use a hosted Kubernetes provider, you can have Rancher launch a Kubernetes cluster using any nodes your want. When Rancher deploys Kubernetes onto these nodes, it uses RKE, or [Rancher Kubernetes Engine]({{< baseurl >}}/rke/v0.1.x/en/), which is Rancher's own lightweight Kubernetes installer. It can launch Kubernetes on any computer, including: - Bare-metal servers - On-premise virtual machines @@ -15,7 +13,7 @@ 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 Docker Machine and RKE to provision a Kubernetes cluster using a major cloud provider. + In this use case, Rancher uses a [Docker Machine](https://docs.docker.com/machine/) 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/): 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 cada204817d..a634330853a 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 @@ -9,7 +9,7 @@ aliases: ## 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. +Rancher calls [Docker Machine](https://docs.docker.com/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). From 8c359ff6c541b758b22e3361fe4a06ac8fe94de6 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 18:27:30 -0700 Subject: [PATCH 15/20] replaced instances of k8s --- .../v2.x/en/cluster-provisioning/_index.md | 20 +++++++++---------- 1 file changed, 10 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 bb9edbf9cef..137328504ff 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -16,17 +16,17 @@ A _Kubernetes Cluster_ is a cluster that uses the [Kubernetes container-orchestr ### Kubernetes Cluster Node Components -Each computing resource in a Kubernetes Cluster is called a _node_. Node can be either bare-metal servers or virtual machines. Kubernetes (here after, K8s) classifies nodes into three distinct types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. Understanding the role of each node will help you create your own K8s cluster. +Each computing resource in a Kubernetes Cluster is called a _node_. Node can be either bare-metal servers or virtual machines. Kubernetes classifies nodes into three distinct types: _etcd_ nodes, _control plane_ nodes, and _worker_ nodes. Understanding the role of each node will help you create your own Kubernetes cluster. #### etcd Nodes -[etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd) nodes run the `etcd` database. The `etcd` database component is a key value store used as K8s storage for all cluster data, such as cluster coordination and state management. +[etcd](https://kubernetes.io/docs/concepts/overview/components/#etcd) nodes run the `etcd` database. The `etcd` database component is a key value store used as Kubernetes storage for all cluster data, such as cluster coordination and state management. `etcd` is a distributed key value store, meaning it runs on multiple nodes so that there's always a backup available for fail over. Even though you can run `etcd` on a single node, you should run it on multiple nodes. We recommend 3, 5, or 7 nodes for redundancy. #### Control Plane Nodes -[Control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane) nodes run the K8s API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your K8s cluster is running according to your configuration. Because all cluster data is stored on your `etcd` nodes, control plane nodes are stateless. You can run control plane on a single node, although two or more nodes are recommended for redundancy. Additionally, you can a single node can share the control plane and `etcd` roles. +[Control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane) nodes run the Kubernetes API server, scheduler, and controller manager. These nodes take care of routine tasks to ensure that your Kubernetes cluster is running according to your configuration. Because all cluster data is stored on your `etcd` nodes, control plane nodes are stateless. You can run control plane on a single node, although two or more nodes are recommended for redundancy. Additionally, you can a single node can share the control plane and `etcd` roles. #### Worker Nodes @@ -39,9 +39,9 @@ Worker nodes also run storage and networking drivers, and ingress controllers wh ## Cluster Creation in Rancher -Now that you know what a K8s Cluster is, how does Rancher fit in? +Now that you know what a Kubernetes Cluster is, how does Rancher fit in? -Rancher simplifies creation of K8s clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a K8s cluster. Use the option that best fits you use case. +Rancher simplifies creation of Kubernetes clusters by allowing you to create them through the Rancher UI rather than more complex alternatives. Rancher provides multiple options for launching a Kubernetes cluster. Use the option that best fits you use case. ## Cluster Creation Options @@ -60,25 +60,25 @@ Options include: ### Hosted Kubernetes Cluster -If you already use a K8s provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI. +If you already use a Kubernetes provider such as Google GKE, Rancher can integrate with its cloud APIs, allowing you to create and manage your hosted cluster from the Rancher UI. [Hosted Kubernetes Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/hosted-kubernetes-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. +Alternatively, you can use Rancher to create a cluster from your own existing nodes, using RKE. RKE is Rancher’s own lightweight Kubernetes 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. [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/) #### Node Pools -Using Rancher, you can leverage Docker Machine in combination with RKE to create nodes and provision a new K8s cluster. +Using Rancher, you can leverage Docker Machine in combination with RKE to create nodes and provision a new Kubernetes cluster. [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#node-pools) #### Custom Nodes -Use Rancher to create a K8s cluster on your on-premise bare metal servers. This option creates a cluster using RKE, which is Rancher's own lightweight K8s 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 less popular IaaS providers by integrating with node drivers. @@ -86,6 +86,6 @@ In addition to bare metal servers, RKE can also create clusters on less popular ### Import Existing Cluster -Users can import an existing K8s cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported K8s clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters. +Users can import an existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters. [Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/imported-clusters/) \ No newline at end of file From a9376e876e51cb0ab2469dc3e25e7bdb0183838b Mon Sep 17 00:00:00 2001 From: Denise Date: Wed, 18 Jul 2018 19:49:15 -0700 Subject: [PATCH 16/20] Update _index.md --- .../v2.x/en/cluster-provisioning/rke-clusters/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 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 7f32d44e75e..9c4abe0e30b 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 @@ -3,7 +3,7 @@ title: Rancher Launched Kubernetes weight: 2200 --- -If you don't want to use a hosted Kubernetes provider, you can have Rancher launch a Kubernetes cluster using any nodes your want. When Rancher deploys Kubernetes onto these nodes, it uses RKE, or [Rancher Kubernetes Engine]({{< baseurl >}}/rke/v0.1.x/en/), which is Rancher's own lightweight Kubernetes installer. It can launch Kubernetes on any computer, including: +If you don't want to use a hosted Kubernetes provider, you can have Rancher launch a Kubernetes cluster using any nodes you want. When Rancher deploys Kubernetes onto these nodes, it uses Rancher Kubernetes Engine]({{< baseurl >}}/rke/v0.1.x/en/) (RKE), which is Rancher's own lightweight Kubernetes installer. It can launch Kubernetes on any computers, including: - Bare-metal servers - On-premise virtual machines @@ -13,8 +13,8 @@ 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 [Docker Machine](https://docs.docker.com/machine/) and RKE to provision a Kubernetes cluster using a major cloud provider. + In this use case, Rancher uses [Docker Machine](https://docs.docker.com/machine/) to provision nodes in IaaS-hosted virtual machines. After the nodes are provisioned, RKE is used deploy Kubernetes. - [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. + For use cases where you want to provision bare-metal servers, on-premise virtual machines, or bring virtual machines that are already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine. Then, RKE is used to deploy Kubernetes. From 4757b67deed65a077a4de2b99d02cad5b976f517 Mon Sep 17 00:00:00 2001 From: Denise Date: Wed, 18 Jul 2018 19:52:33 -0700 Subject: [PATCH 17/20] Update _index.md --- .../v2.x/en/cluster-provisioning/custom-clusters/_index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md index a3428eceef9..fa947219d45 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/custom-clusters/_index.md @@ -3,6 +3,6 @@ title: Custom Cluster weight: 2210 --- -If you don't want to host your Kubernetes cluster in a [hosted kubernetes provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters) or one of the major IaaS providers listed in [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools), you can use the _custom cluster_ option to host your cluster in on-premise bare-metal servers, on-premise virtual machines, or in _any_ IaaS provider. +If you don't want to host your Kubernetes cluster in a [hosted kubernetes provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters) or provision nodes through Rancher, you can use the _custom cluster_ option to create a Kubernetes cluster in on-premise bare-metal servers, on-premise virtual machines, or in _any_ IaaS provider. -In this scenario, you'll have to build the hosts yourself, and then configure them to meet Rancher's [requirements]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#requirements). Then, use the [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md) install option to setup your cluster. \ No newline at end of file +In this scenario, you'll bring the nodes yourself, and then configure them to meet Rancher's [requirements]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/#requirements). Then, use the [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/_index.md) install option to setup your cluster. From 005707a5fb23a780469becdd5e14649228ed86c1 Mon Sep 17 00:00:00 2001 From: Denise Date: Wed, 18 Jul 2018 20:05:27 -0700 Subject: [PATCH 18/20] Update _index.md --- content/rancher/v2.x/en/cluster-provisioning/_index.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/_index.md b/content/rancher/v2.x/en/cluster-provisioning/_index.md index 137328504ff..cdcc0786164 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -66,21 +66,19 @@ If you already use a Kubernetes provider such as Google GKE, Rancher can integra ### 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 Kubernetes 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. +Alternatively, you can use Rancher to create the Kubernetes cluster on your own nodes, using [Rancher Kubernetes Engine (RKE)]({{< baseurl >}}/rke/v0.1.x/en/). RKE is Rancher’s own lightweight Kubernetes installer. With these clusters, Rancher manages the deployment of Kubernetes. These Kubernetes clusters can be deployed on any bare metal server, cloud provider, or virtualization platform. These nodes can either be provisioned through Rancher's UI, which calls [Docker Machine](https://docs.docker.com/machine/) to launch nodes on various cloud providers or they can be existing nodes that users bring and run a Rancher agent container onto. [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/) #### Node Pools -Using Rancher, you can leverage Docker Machine in combination with RKE to create nodes and provision a new Kubernetes cluster. +Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-templates). This node template defines the parameters you want to use to launch nodes in your cloud providers. The available cloud providers to create a node template are decided based on active [node drivers]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-drivers). The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher will automatically create another node to join the cluster to ensure that the count of the node pool is as expected. [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#node-pools) #### 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 less popular IaaS providers by integrating with node drivers. +You can bring any nodes you want to Rancher and have Rancher create the Kubernetes cluster. These nodes can include on-premise bare metal servers, nodes existing in a cloud provider or virtual machines. [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/#custom-nodes) @@ -88,4 +86,4 @@ In addition to bare metal servers, RKE can also create clusters on less popular Users can import an existing Kubernetes cluster into Rancher. Rancher does not automate the provisioning, scaling, and upgrade of imported Kubernetes clusters. All other cluster management, policy management, and workload management capabilities of Rancher apply to imported clusters. -[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/imported-clusters/) \ No newline at end of file +[Importing Existing Cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/imported-clusters/) From 8bd25d0e23c64517250241178ac5fa8c7629c4c9 Mon Sep 17 00:00:00 2001 From: Denise Date: Wed, 18 Jul 2018 20:08:22 -0700 Subject: [PATCH 19/20] Update _index.md --- .../v2.x/en/cluster-provisioning/rke-clusters/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 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 9c4abe0e30b..f90d7e1f35f 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 @@ -9,12 +9,12 @@ If you don't want to use a hosted Kubernetes provider, you can have Rancher laun - On-premise virtual machines - IaaS-hosted virtual machines -RKE cluster provisioning is separated into two categories: +RKE launched clusters are separated into two categories: - [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/): - In this use case, Rancher uses [Docker Machine](https://docs.docker.com/machine/) to provision nodes in IaaS-hosted virtual machines. After the nodes are provisioned, RKE is used deploy Kubernetes. + Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-templates). This node template defines the parameters you want to use to launch nodes in your cloud providers. The available cloud providers to create a node template are decided based on active [node drivers]({{< baseurl >}}/rancher/v2.x/en/cluster-providers/rke-clusters/node-pools/#node-drivers). The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher will automatically create another node to join the cluster to ensure that the count of the node pool is as expected. - [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 bring virtual machines that are already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine. Then, RKE is used to deploy Kubernetes. + For use cases where you want to provision bare-metal servers, on-premise virtual machines, or bring virtual machines that are already exist in a cloud provider. With this option, you will run a Rancher agent Docker container on the machine. From 37b6868535956e262f71a2bb3922484140351bd4 Mon Sep 17 00:00:00 2001 From: Denise Date: Wed, 18 Jul 2018 20:33:11 -0700 Subject: [PATCH 20/20] Update _index.md --- .../rke-clusters/node-pools/_index.md | 38 +++++++++---------- 1 file changed, 18 insertions(+), 20 deletions(-) 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 a634330853a..1a04f63f9d6 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 @@ -9,20 +9,25 @@ aliases: ## Node Pools -Rancher calls [Docker Machine](https://docs.docker.com/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. +Using Rancher, you can create pools of nodes based on a [node template](#node-templates). The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher will automatically create another node to join the cluster to ensure that the count of the node pool is as expected. -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). +Each node pool is assigned with a [node component]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#node-components) to specify how these nodes should be configured for the Kubernetes cluster. -- Amazon EC2 -- Microsoft Azure -- DigitalOcean -- VMWare Vsphere +<-- Needs steps on how to add/create node pools --> -### Node Drivers +## Node templates -Out-of-the-box, Rancher provides support for creating clusters using many popular cloud providers: Amazon EC2, Azure, DigitalOcean, and so on. However, you may want to create a cluster using another cloud provider. In these scenarios, you can create a custom node driver for the cloud provider and point Rancher toward it. +A node template is the saved configuration for the parameters to use when provisioning nodes in a specific cloud provider. Rancher provides a nice UI to be able to launch these nodes and uses [Docker Machine]((https://docs.docker.com/machine/) to provision these nodes. The available cloud providers to create node templates are based on the active [node drivers](#node drivers) in Rancher. -For more information on creating node drivers, see [https://github.com/rancher/ui-driver-skel](https://github.com/rancher/ui-driver-skel). +After you create a node template in Rancher, it's saved so that you can use this template again to create other node pools. Node templates are bound to your login. After you add a template, you can remove them from your user profile. + +<-- need steps on how to add/create node templates--> + +## Node Drivers + +A node driver is the same as a [Docker Machine driver](https://docs.docker.com/machine/drivers/). The availability of which node driver to display when creating node templates is defined based on the node driver's status. Only `active` node drivers will be displayed as an option for creating node templates. By default, Rancher is packaged with many existing Docker Machine drivers, but you can also create custom node drivers to add to Rancher. + +If there are specific node drivers that you don't want to show to your users, you would need to de-activate these node drivers. #### Managing Node Drivers @@ -33,7 +38,7 @@ For more information on creating node drivers, see [https://github.com/rancher/u ## Adding Custom Node Drivers -If you create a cluster using a cloud provider that {{< product >}} doesn't support out-of-the-box, you may need to add the provider's drivers (or create them yourself) so that your nodes function properly. +If you want to use a node driver that Rancher doesn't support out-of-the-box, you can add the provider's drivers in order to start using them to create node templates and eventually node pools. 1. From the **Global** view, select **Node Drivers** from the main menu. @@ -41,19 +46,12 @@ If you create a cluster using a cloud provider that {{< product >}} doesn't supp 3. Complete the **Add Node Driver** form. Then click **Create**. -## Activating Node Drivers +## Activating/Deactivating Node Drivers -Using the **Custom** option, you can create a cluster using virtually any cloud provider. However, by default, {{< product >}} only activates drivers for the most popular cloud providers. If you want to use another provider, you'll have to activate their drivers. +By default, Rancher only activates drivers for the most popular cloud providers, Amazon EC2, Azure, Digital Ocean and vSphere. If you want to show or hide any node driver, you can change it's status. 1. From the **Global** view, select **Node Drivers** from the main menu. -2. Select the inactive drivers that you want to use. Then click **Add Node Driver**. +2. Find the driver that you want to activate or deactivate and select **Vertical Elipsis (... ) > Edit**. Choose either **Activate** or **Deactivate**. -### Node templates - -You can create new clusters within Rancher using _node templates_. A node template is a virtual machine image used to create a Kubernetes cluster. While creating a cluster, Rancher will prompt you for an image to use as a template. Follow the directions on screen to create the template. During cluster creation, Rancher clones the template and installs different Kubernetes components. - -After you add a node template to Rancher, its stored by the system so that you can use it when creating another cluster later. Node templates are bound to your login. After you add a template, you can remove them from your user profile. - -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. The provider than provisions your nodes based on the template.