You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: update templates to specify control and worker shapes separately (#19)
While the users can specify the shapes independently we wanted our
defined templates to support this as well. It should make it easier
for our users to quickly define different shapes independent of each
other.
Copy file name to clipboardExpand all lines: docs/src/gs/create-workload-cluster.md
+45-34Lines changed: 45 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,66 +2,80 @@
2
2
3
3
## Workload Cluster Templates
4
4
5
-
Choose one of the available templates for to create your workload clusters from the [latest released artifacts][latest-release]. Each workload cluster template can be further configured with the parameters below.
5
+
Choose one of the available templates for to create your workload clusters from the
6
+
[latest released artifacts][latest-release]. Each workload cluster template can be
7
+
further configured with the parameters below.
6
8
7
9
## Workload Cluster Parameters
8
10
9
-
The following Oracle Cloud Infrastructure (OCI) configuration parameters are available when creating a workload cluster on OCI:
11
+
The following Oracle Cloud Infrastructure (OCI) configuration parameters are available
12
+
when creating a workload cluster on OCI using one of our predefined templates:
|`OCI_COMPARTMENT_ID`|| The OCID of the compartment where the OCI resources are to be created |
14
-
|`OCI_IMAGE_ID`|| The OCID of the Compute Image (Oracle Linux or Ubuntu) with which to create the Kubernetes nodes |
15
-
|`OCI_SHAPE`| VM.Standard.E4.Flex | The shape of the Kubernetes nodes |
16
-
|`OCI_SHAPE_MEMORY_IN_GBS`|| The amount of memory to be allocated to the instances. If not provided it is automatically computed by compute API. |
17
-
|`OCI_SHAPE_OCPUS`| 1 | The number of OCPUs allocated to the instance |
18
-
|`OCI_SSH_KEY`|| The public SSH key to be added to the Kubernetes nodes. It can be used to login to the node and troubleshoot failures. |
19
-
|`OCI_PV_TRANSIT_ENCRYPTION`| true |[In-transit encryption](https://docs.oracle.com/en-us/iaas/Content/File/Tasks/intransitencryption.htm) provides a way to secure your data between instances and mounted file systems using TLS v.1.2 (Transport Layer Security) encryption. Only [some bare metal instances](https://docs.oracle.com/en-us/iaas/releasenotes/changes/60d602f5-abb3-4639-aa19-292a5744a808/) support In-transit encryption |
|`OCI_COMPARTMENT_ID`|| The OCID of the compartment in which to create the required compute, storage and network resources. |
17
+
|`OCI_IMAGE_ID`|| The OCID of the image for the kubernetes nodes. This same image is used for both the control plane and the worker nodes. |
18
+
|`OCI_CONTROL_PLANE_MACHINE_TYPE`| VM.Standard.E4.Flex | The [shape](https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm) of the Kubernetes control plane machine. |
19
+
|`OCI_CONTROL_PLANE_MACHINE_TYPE_OCPUS`| 1 | The number of OCPUs allocated to the control plane instance. |
20
+
|`OCI_NODE_MACHINE_TYPE`| VM.Standard.E4.Flex | The [shape](https://docs.oracle.com/en-us/iaas/Content/Compute/References/computeshapes.htm) of the Kubernetes worker machine. |
21
+
|`OCI_NODE_MACHINE_TYPE_OCPUS`| 1 | The number of OCPUs allocated to the worker instance. |
22
+
|`OCI_SSH_KEY`|| The public SSH key to be added to the Kubernetes nodes. It can be used to login to the node and troubleshoot failures. |
23
+
|`OCI_CONTROL_PLANE_PV_TRANSIT_ENCRYPTION`| true | Enables [in-flight Transport Layer Security (TLS) 1.2 encryption](https://docs.oracle.com/en-us/iaas/Content/File/Tasks/intransitencryption.htm) of data between control plane nodes and their associated block storage devices. |
24
+
|`OCI_NODE_PV_TRANSIT_ENCRYPTION`| true | Enables [in-flight Transport Layer Security (TLS) 1.2 encryption](https://docs.oracle.com/en-us/iaas/Content/File/Tasks/intransitencryption.htm) of data between worker nodes and their associated block storage devices. |
25
+
26
+
*NOTE* Only specific [bare metal shapes](https://docs.oracle.com/en-us/iaas/releasenotes/changes/60d602f5-abb3-4639-aa19-292a5744a808/)
27
+
support in-transit encryption. If an unsupported shape is specified, the deployment will fail completely.
28
+
29
+
*NOTE:* Using the predefined templates the machine's memory size is automatically allocated based on the chosen shape
30
+
and OCPU count.
20
31
21
32
The following Cluster API parameters are also available:
|`CLUSTER_NAME`|| The name of the workload cluster to create |
26
-
|`CONTROL_PLANE_MACHINE_COUNT`| 1 | The number of control plane machines for the workload cluster.|
27
-
|`KUBERNETES_VERSION`|| The Kubernetes version to use for the workload cluster. If unspecified, the value from OS environment variables or the .cluster-api/clusterctl.yaml config file will be used. |
28
-
|`NAMESPACE`|| The namespace to use for the workload cluster. If unspecified, the current namespace will be used |
29
-
|`POD_CIDR`| 1 | The CIDR range for the Kubernetes POD network. |
30
-
|`SERVICE_CIDR`|| The CIDR for the Kubernetes services network. |
31
-
|`SERVICE_DOMAIN`|||
32
-
|`WORKER_MACHINE_COUNT`|| The number of worker machines for the workload cluster. |
|`CLUSTER_NAME`|| The name of the workload cluster to create. |
37
+
|`CONTROL_PLANE_MACHINE_COUNT`| 1 | The number of control plane machines for the workload cluster. |
38
+
|`KUBERNETES_VERSION`|| The Kubernetes version installed on the workload cluster nodes. If this environement variable is not configured, the version must be specifed in the `.cluster-api/clusterctl.yaml` file |
39
+
|`NAMESPACE`|| The namespace for the workload cluster. If not specified, the current namespace is used. |
40
+
|`POD_CIDR`| 192.168.0.0/16 | CIDR range of the Kubernetes pod-to-pod network. |
41
+
|`SERVICE_CIDR`| 10.128.0.0/12 | CIDR range of the Kubernetes pod-to-services network. |
42
+
|`NODE_MACHINE_COUNT`|| The number of worker machines for the workload cluster. |
33
43
34
44
## Create a new workload cluster on virtual instances using an Ubuntu custom image
35
45
36
-
Run the command below to create a Kubernetes cluster with 1 control plane node and 1 worker node:
46
+
The following command will create a workload cluster comprising a single
47
+
control plane node and single worker node using the default values as specified in the preceding
0 commit comments