From 6f59a75556d5d1836ca5be1d7f8938f55612de81 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 18 Jul 2018 16:06:28 -0700 Subject: [PATCH] adding cluster option docs --- .../rke-clusters/options/_index.md | 29 ++++++++++++++++++- 1 file changed, 28 insertions(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/_index.md b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/_index.md index d24363a15a8..05178979e67 100644 --- a/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/_index.md +++ b/content/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/_index.md @@ -12,4 +12,31 @@ You can configure K8s options one of two ways: ## Rancher UI -## Config File \ No newline at end of file +When creating a cluster using one of the options described in [Rancher Launched Kubenernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters), you can configure basic K8s options using the **Cluster Options** section. + +From this section allows you choose: + +- The version of Kubernetes installed on your cluster nodes. Rancher uses its own version of Kubernetes based on [hyperkube](https://hub.docker.com/r/kubernetesonarm/hyperkube/), but packaged with more utilities. + +- Whether your nodes allow installation of an unsupported version of Docker (i.e., a version not listed in the Rancher requirements). + +- The Network Provider that the cluster uses. Out of the box, Rancher supports: + + - Flannel + + - Calico + + - Canal (default) + +- Whether or not to use a cloud provider. + +- Whether or not to use a pod security policy. You must have an existing pod security policy configured before you can use this option. + +## Config File + +Instead of using the Rancher UI to choose K8s options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the options available in an RKE installation. + +- To edit an RKE config file directly from the Rancher UI, click **Edit as YAML**. +- To read from an existing RKE file, click **Read from File**. + +For an example of RKE config file syntax, see the RKE documentation. \ No newline at end of file