From b80e35d76ef51e9fd6db2885317d745f6b3fa25f Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 1 Nov 2018 17:53:26 -0700 Subject: [PATCH 1/4] making edits at Will's request --- .../v2.x/en/cluster-provisioning/cloning-clusters/_index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md index d9fd08aaa8d..e1597489fcd 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md @@ -9,14 +9,12 @@ If you have a cluster in Rancher that you want to use as a template for creating - Only [cluster types]({{< baseurl >}}/content/rancher/v2.x/en/cluster-provisioning) that interact with cloud hosts over API can be duplicated. Duplication of imported clusters and custom clusters provisioned using Docker machine is not supported. - | Cluster Type | Cloneable? | | -------------------------------- | ------------- | | [Hosted Kubernetes Providers][1] | ✓ | | [Nodes Hosted by IaaS][2] | ✓ | | [Custom Cluster][3] | | | [Imported Cluster][4] | | - - During the process of duplicating a cluster, you will edit a config file full of cluster settings. However, we recommend editing only values explicitly listed in this document, as cluster duplication is designed for simple cluster copying, _not_ wide scale configuration changes. Editing other values may invalidate the config file, which will lead to cluster deployment failure. [1]: {{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/ @@ -57,12 +55,12 @@ Use your favorite text editor to modify the cluster configuration in `cluster-te 1. Open `cluster-template.yml` (or whatever you named your config) in your favorite test editor. - >**Warning:** Only edit the cluster config values explicitly called out below. Many of the values listed in this file are used to provision your duplicate cluster, and editing their values may break the provisioning process. + >**Warning:** Only edit the cluster config values explicitly called out below. Many of the values listed in this file are used to provision your duplicate cluster, and editing their values may break the provisioning process. 1. As depicted in one of the examples below, at the `` placeholder, replace your original cluster's name with a unique name (``). If your cloned cluster has a duplicate name, the cluster will not provision successfully. {{% accordion id="gke" label="GKE" %}} -``` +```yml Version: v3 clusters: : # ENTER UNIQUE NAME From 493d0f1bb5b7118023d060fcac855dc68e44dd1f Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 1 Nov 2018 19:15:43 -0700 Subject: [PATCH 2/4] removing term 'iaas' --- .../removing-rancher/user-cluster-nodes/_index.md | 2 +- .../v2.x/en/cluster-provisioning/cloning-clusters/_index.md | 6 +++--- .../v2.x/en/cluster-provisioning/custom-clusters/_index.md | 2 +- .../hosted-kubernetes-clusters/_index.md | 2 +- .../v2.x/en/cluster-provisioning/rke-clusters/_index.md | 2 +- .../rke-clusters/custom-nodes/_index.md | 2 +- content/rancher/v2.x/en/installation/requirements/_index.md | 2 +- content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md | 6 +++--- 8 files changed, 12 insertions(+), 12 deletions(-) diff --git a/content/rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/_index.md b/content/rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/_index.md index 5431793e941..35594a6e7b8 100644 --- a/content/rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/_index.md +++ b/content/rancher/v2.x/en/admin-settings/removing-rancher/user-cluster-nodes/_index.md @@ -14,7 +14,7 @@ When removing nodes from your Rancher-launched cluster (provided that they are i When cleaning nodes provisioned using Rancher, the following components are deleted based on the type of cluster node you're removing. -| Removed Component | [IaaS Nodes][1] | [Custom Nodes][2] | [Hosted Cluster][3] | [Imported Nodes][4] | +| Removed Component | [Nodes Hosted by Infrastructure Provider][1] | [Custom Nodes][2] | [Hosted Cluster][3] | [Imported Nodes][4] | | ------------------------------------------------------------------------------ | --------------- | ----------------- | ------------------- | ------------------- | | The Rancher deployment namespace (`cattle-system` by default) | ✓ | ✓ | ✓ | ✓ | | `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` labeled by Rancher | ✓ | ✓ | ✓ | ✓ | diff --git a/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md index e1597489fcd..ca084f2dac5 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md @@ -12,7 +12,7 @@ If you have a cluster in Rancher that you want to use as a template for creating | Cluster Type | Cloneable? | | -------------------------------- | ------------- | | [Hosted Kubernetes Providers][1] | ✓ | - | [Nodes Hosted by IaaS][2] | ✓ | + | [Nodes Hosted by Infrastructure Provider][2] | ✓ | | [Custom Cluster][3] | | | [Imported Cluster][4] | | - During the process of duplicating a cluster, you will edit a config file full of cluster settings. However, we recommend editing only values explicitly listed in this document, as cluster duplication is designed for simple cluster copying, _not_ wide scale configuration changes. Editing other values may invalidate the config file, which will lead to cluster deployment failure. @@ -110,7 +110,7 @@ clusters: sshPublicKeyContents: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDJc2kDExgRaDLD ``` {{% /accordion %}} -{{% accordion id="ec2" label="IaaS Clusters (EC2, Azure, or DigitalOcean )" %}} +{{% accordion id="ec2" label="Nodes Hosted by Infrastructure Provider (EC2, Azure, or DigitalOcean )" %}} ```yml Version: v3 clusters: @@ -128,7 +128,7 @@ clusters: ``` {{% /accordion %}} -1. **IaaS Clusters Only:** For each `nodePools` section, replace the original nodepool name with a unique name at the `` placeholder. If your cloned cluster has a duplicate nodepool name, the cluster will not provision successfully. +1. **Nodes Hosted by Infrastructure Provider Only:** For each `nodePools` section, replace the original nodepool name with a unique name at the `` placeholder. If your cloned cluster has a duplicate nodepool name, the cluster will not provision successfully. ```yml nodePools: 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 0f6b7d9237e..84c184fc6fc 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 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. +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_ node hosted by an infrastructure provider. 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/) install option to setup your cluster. 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 5c47482aae3..69c6aeeb8fb 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 @@ -5,7 +5,7 @@ weight: 2100 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. +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 infrastructure provider, all from the same UI. Rancher supports the following Kubernetes providers: 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 377013f3bf0..d0388377478 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 @@ -7,7 +7,7 @@ If you don't want to use a hosted Kubernetes provider, you can have Rancher laun - Bare-metal servers - On-premise virtual machines -- IaaS-hosted virtual machines +- Virtual machines hosted by an infrastructure provider RKE launched clusters are separated into two categories: 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 5de778b6628..9912d70255d 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,7 +8,7 @@ aliases: ## Custom Nodes -Use Rancher to create a Kubernetes cluster on your on-premise bare metal servers. This option creates a cluster using a combination of [Docker Machine](https://docs.docker.com/machine/) and RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ 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](https://docs.docker.com/machine/) and RKE, which is Rancher's own lightweight Kubernetes installer. In addition to bare metal servers, RKE can also create clusters on _any_ infrastructure provider by integrating with node drivers. To use this option you'll need access to servers you intend to use as your Kubernetes cluster. Provision each server according to Rancher [requirements](#requirements), which includes some hardware specifications and Docker. After you install Docker on each server, run the command provided in the Rancher UI to turn each server into a Kubernetes node. diff --git a/content/rancher/v2.x/en/installation/requirements/_index.md b/content/rancher/v2.x/en/installation/requirements/_index.md index 90f914047d1..d3d4a50194f 100644 --- a/content/rancher/v2.x/en/installation/requirements/_index.md +++ b/content/rancher/v2.x/en/installation/requirements/_index.md @@ -78,7 +78,7 @@ Each node used (either for the Single Node Install, High Availability (HA) Insta

Port requirements

-When deploying Rancher in an HA cluster, certain ports on your nodes must be open to allow communication with Rancher. The ports that must be open change according to the type of machines hosting your cluster nodes. For example, if your are deploying Rancher on nodes hosted by an IaaS, port `22` must be open for SSH. The following diagram depicts the ports that are opened for each [cluster type]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning). +When deploying Rancher in an HA cluster, certain ports on your nodes must be open to allow communication with Rancher. The ports that must be open change according to the type of machines hosting your cluster nodes. For example, if your are deploying Rancher on nodes hosted by an infrastructure, port `22` must be open for SSH. The following diagram depicts the ports that are opened for each [cluster type]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning). Cluster Type Port Requirements ![Basic Port Requirements]({{< baseurl >}}/img/rancher/port-communications.svg) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md index 2dc2d9b142b..1973669206d 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md @@ -96,19 +96,19 @@ Select this option to view the node's [API endpoints]({{< baseurl >}}/rancher/v2 Use **Delete** to remove defective nodes from the cloud provider. When you the delete a defective node, Rancher automatically replaces it with an identically provisioned node. ->**Tip:** If your cluster is hosted on IaaS nodes, and you want to scale your cluster down instead of deleting a defective node, [scale down](#scaling-nodes) rather than delete. +>**Tip:** If your cluster is hosted by an infrastructure provider, and you want to scale your cluster down instead of deleting a defective node, [scale down](#scaling-nodes) rather than delete. ## Scaling Nodes -For nodes hosted by an IaaS, you can scale the number of nodes in each node pool by using the scale controls. This option isn't available for other cluster types. +For nodes hosted by an infrastructure provider, you can scale the number of nodes in each node pool by using the scale controls. This option isn't available for other cluster types. ![Scaling Nodes]({{< baseurl >}}/img/rancher/iaas-scale-nodes.png) ## Remoting into a Node Pool Node -For [nodes hosted by an IaaS]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/), you have the option of downloading its SSH key so that you can connect to it remotely from your desktop. +For [nodes hosted by an infrastructure provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/), you have the option of downloading its SSH key so that you can connect to it remotely from your desktop. 1. From the Node Pool cluster, select **Nodes** from the main menu. From a927570d3289b4aeef5d3dc3bdf99331b3bff73c Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Thu, 1 Nov 2018 19:24:46 -0700 Subject: [PATCH 3/4] changing use of 'node pools' to 'infrastructure provider' --- content/rancher/v2.x/en/cluster-provisioning/_index.md | 9 ++++----- .../v2.x/en/cluster-provisioning/rke-clusters/_index.md | 4 ++-- .../rke-clusters/node-pools/_index.md | 2 +- content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md | 6 +++--- .../v2.x/en/user-settings/node-templates/_index.md | 2 +- .../en/config-options/cloud-providers/vsphere/_index.md | 8 ++++---- 6 files changed, 15 insertions(+), 16 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/_index.md b/content/rancher/v2.x/en/cluster-provisioning/_index.md index 808214f97e8..318cf361898 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/_index.md @@ -51,8 +51,7 @@ Options include: - [Hosted Kubernetes Cluster](#hosted-kubernetes-cluster) - [Rancher Launched Kubernetes](#rancher-launched-kubernetes) - - - [Node Pools](#node-pools) + - [Nodes Hosted by an Infrastructure Provider](#nodes-hosted-by-an-infrastructure-provider) - [Custom Nodes](#custom-nodes) - [Import Existing Cluster](#import-existing-cluster) @@ -73,11 +72,11 @@ Alternatively, you can use Rancher to create a cluster on your own nodes, using [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/) -#### Node Pools +#### Nodes Hosted by an Infrastructure Provider -Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-templates). This template defines the parameters used to launch nodes in your cloud providers. The cloud providers available for creating a node template are decided based on the [node drivers]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-drivers) active in the Rancher UI. The benefit of using a node pool is that if a node loses connectivity with the cluster, Rancher automatically replaces it, thus maintaining the expected cluster configuration. +Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-templates). This template defines the parameters used to launch nodes in your cloud providers. The cloud providers available for creating a node template are decided based on the [node drivers]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-drivers) active in the Rancher UI. The benefit of using nodes hosted by an infrastructure provider is that if a node loses connectivity with the cluster, Rancher automatically replaces it, thus maintaining the expected cluster configuration. -[Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/) +[Nodes Hosted by an Infrastructure Provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/) #### Custom Nodes 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 d0388377478..f64297f1e8e 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 @@ -11,9 +11,9 @@ If you don't want to use a hosted Kubernetes provider, you can have Rancher laun RKE launched clusters are separated into two categories: -- [Node Pools]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/): +- [Nodes Hosted by an Infrastructure Provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/): - Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/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-provisioning/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. + Using Rancher, you can create pools of nodes based on a [node template]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/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-provisioning/rke-clusters/node-pools/#node-drivers). The benefit of using a node hosted by an infrastructure provider 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/): 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 9fbdb7e18a6..3ab3fabc935 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 @@ -1,5 +1,5 @@ --- -title: Nodes hosted in an Infrastructure Provider +title: Nodes Hosted in an Infrastructure Provider weight: 2205 aliases: - /rancher/v2.x/en/concepts/global-configuration/node-drivers/ diff --git a/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md index 1973669206d..32a960e0831 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/nodes/_index.md @@ -15,7 +15,7 @@ To manage individual nodes, browse to the cluster that you want to manage and th The following table lists which node options are available for each [type of cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#cluster-creation-options) in Rancher. Click the links in the **Option** column for more detailed information about each feature. -| Option | [Node Pool][1] | [Custom Node][2] | [Hosted Cluster][3] | [Imported Nodes][4] | Description | +| Option | [Nodes Hosted by an Infrastructure Provider][1] | [Custom Node][2] | [Hosted Cluster][3] | [Imported Nodes][4] | Description | | ------------------------------------------------ | ------------------------------------------------ | ---------------- | ------------------- | ------------------- | ------------------------------------------------------------------ | | [Cordon](#cordoning-a-node) | ✓ | ✓ | ✓ | | Marks the node as unschedulable. | | [Drain](#draining-a-node) | ✓ | ✓ | ✓ | | Marks the node as unschedulable _and_ evicts all pods. | @@ -106,12 +106,12 @@ For nodes hosted by an infrastructure provider, you can scale the number of node ![Scaling Nodes]({{< baseurl >}}/img/rancher/iaas-scale-nodes.png) -## Remoting into a Node Pool Node +## Remoting into a Node Hosted by an Infrastructure Provider For [nodes hosted by an infrastructure provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/), you have the option of downloading its SSH key so that you can connect to it remotely from your desktop. -1. From the Node Pool cluster, select **Nodes** from the main menu. +1. From the cluster hosted by an infrastructure provider, select **Nodes** from the main menu. 1. Find the node that you want to remote into. Select **Ellipsis (...) > Download Keys**. diff --git a/content/rancher/v2.x/en/user-settings/node-templates/_index.md b/content/rancher/v2.x/en/user-settings/node-templates/_index.md index fdc48f6e6b1..24d0d604602 100644 --- a/content/rancher/v2.x/en/user-settings/node-templates/_index.md +++ b/content/rancher/v2.x/en/user-settings/node-templates/_index.md @@ -3,7 +3,7 @@ title: Managing Node Templates weight: 7010 --- -When you provision a [node pool]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools) cluster, [node templates]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) are used to provision the cluster nodes. These templates use Docker Machine configuration options to define an operating system image and settings/parameters for the node. You can create node templates in two contexts: +When you provision a cluster [hosted by an infrastructure provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools), [node templates]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/#node-templates) are used to provision the cluster nodes. These templates use Docker Machine configuration options to define an operating system image and settings/parameters for the node. You can create node templates in two contexts: - While [provisioning a node pool cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools). - At any time, from your [user settings](#creating-a-node-template-from-user-settings). diff --git a/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md b/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md index fdfdddcac7c..9a79826b2df 100644 --- a/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md +++ b/content/rke/v0.1.x/en/config-options/cloud-providers/vsphere/_index.md @@ -28,7 +28,7 @@ When provisioning clusters in Rancher using the [vSphere node driver]({{< baseur 5. Assign **Member Roles** as required. 6. Expand **Cluster Options** and configure as required. 7. Set **Cloud Provider** option to `Custom`. - + ![vsphere-node-driver-cloudprovider]({{< baseurl >}}/img/rancher/vsphere-node-driver-cloudprovider.png) 8. Click on **Edit as YAML** @@ -149,7 +149,7 @@ The following configuration options are available under the disk directive: ___ -### network +### network The following configuration options are available under the network directive: @@ -184,7 +184,7 @@ cloud_provider: folder: k8s-dummy default-datastore: ds-1 datacenter: eu-west-1 - + ``` ## Annex @@ -245,7 +245,7 @@ $ rancher ssh ``` 3. Inspect the logs of the controller-manager and kubelet containers looking for errors related to the vSphere cloud provider: - + ```sh $ docker logs --since 15m kube-controller-manager $ docker logs --since 15m kubelet From bed345156b333295b2f26132055dc33ec5f47a87 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 2 Nov 2018 10:34:25 -0700 Subject: [PATCH 4/4] replacing 'duplicate' with 'clone' --- .../cloning-clusters/_index.md | 20 ++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md b/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md index ca084f2dac5..a437724d2ab 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/cloning-clusters/_index.md @@ -1,13 +1,13 @@ --- -title: Duplicating Clusters +title: Cloning Clusters weight: 2400 --- -If you have a cluster in Rancher that you want to use as a template for creating similar clusters, you can use Rancher CLI to duplicate the cluster's configuration, edit it, and then use it to quickly launch the duplicate cluster. +If you have a cluster in Rancher that you want to use as a template for creating similar clusters, you can use Rancher CLI to clone the cluster's configuration, edit it, and then use it to quickly launch the cloned cluster. ## Caveats -- Only [cluster types]({{< baseurl >}}/content/rancher/v2.x/en/cluster-provisioning) that interact with cloud hosts over API can be duplicated. Duplication of imported clusters and custom clusters provisioned using Docker machine is not supported. +- Only [cluster types]({{< baseurl >}}/content/rancher/v2.x/en/cluster-provisioning) that interact with cloud hosts over API can be cloned. Duplication of imported clusters and custom clusters provisioned using Docker machine is not supported. | Cluster Type | Cloneable? | | -------------------------------- | ------------- | @@ -29,6 +29,8 @@ Download and install [Rancher CLI]({{< baseurl >}}/rancher/v2.x/en/cli). Remembe ## 1. Export Cluster Config +Begin by using Rancher CLI to export the configuration for the cluster that you want to clone. + 1. Open Terminal and change your directory to the location of the Rancher CLI binary, `rancher`. 1. Enter the following command to list the clusters managed by Rancher. @@ -45,17 +47,17 @@ Download and install [Rancher CLI]({{< baseurl >}}/rancher/v2.x/en/cli). Remembe ./rancher clusters export - **Step Result:** The YAML for a duplicate cluster prints to Terminal. + **Step Result:** The YAML for a cloned cluster prints to Terminal. 1. Copy the YAML to your clipboard and paste it in a new file. Save the file as `cluster-template.yml` (or any other name, as long as it has a `.yml` extension). ## 2. Modify Cluster Config -Use your favorite text editor to modify the cluster configuration in `cluster-template.yml` for your duplicate cluster. +Use your favorite text editor to modify the cluster configuration in `cluster-template.yml` for your cloned cluster. -1. Open `cluster-template.yml` (or whatever you named your config) in your favorite test editor. +1. Open `cluster-template.yml` (or whatever you named your config) in your favorite text editor. - >**Warning:** Only edit the cluster config values explicitly called out below. Many of the values listed in this file are used to provision your duplicate cluster, and editing their values may break the provisioning process. + >**Warning:** Only edit the cluster config values explicitly called out below. Many of the values listed in this file are used to provision your cloned cluster, and editing their values may break the provisioning process. 1. As depicted in one of the examples below, at the `` placeholder, replace your original cluster's name with a unique name (``). If your cloned cluster has a duplicate name, the cluster will not provision successfully. @@ -144,10 +146,10 @@ clusters: 1. When you're done, save and close the configuration. -## 3. Launch Duplicate Cluster +## 3. Launch Cloned Cluster Move `cluster-template.yml` into the same directory as the Rancher CLI binary. Then run this command: ./rancher up --file cluster-template.yml -**Result:** Your duplicate cluster begins provisioning. Enter `./rancher cluster ls` to confirm. You can also log into the Rancher UI and open the **Global** view to watch your provisioning cluster's progress. \ No newline at end of file +**Result:** Your cloned cluster begins provisioning. Enter `./rancher cluster ls` to confirm. You can also log into the Rancher UI and open the **Global** view to watch your provisioning cluster's progress. \ No newline at end of file