The workflow prompts the user to provide critical cluster configuration details organized into logical sections:
- General (mandatory)
Review the supported cluster configurations and select your desired cluster configuration. This will determine the number of nodes you need to prepare to initiate cluster provisioning.
|Type||Number of Initial Nodes|
|Converged, Single Master||1 Nodes (1 Master/Worker)|
|Dedicated, Single Master||2 Nodes (1 Master + 1 Worker)|
|Converged, Multi Master||3 Nodes (3 Masters + 1 Worker)|
|Dedicated, Multi Master||4 Nodes (3 Masters + 1 Worker)|
Create VMs or bare metal instances compatible with the infrastructure requirements. Ensure that you have SSH access to all the instances/VMs
Ensure you have the exact number of nodes for initial provisioning as per the cluster configuration from the previous step. Additional worker nodes can be added once the cluster is successfully provisioned.
Create a Cluster¶
- Login into the Console
- Navigate to the project where you would like the cluster provisioned
- Click New Cluster
- Select Create a New Cluster and click Continue
- Select the Environment Data center / Edge
- Select Package Type Linux Installer
- Select Kubernetes Distribution Amazon EKS Distro
- Enter the Cluster Name and click Continue
All the defaults are automatically selected and presented. Several options are available for customization.
- Specify a location for the cluster (for multi-cluster workflows)
- Select cluster blueprint and version
- Select the Kubernetes version required to deploy
- Select the OS and Version you used for the nodes
- If distributed storage is required, select GlusterFS
- If you have selected multiple storage types, select the default storage class.
By default, as a security precaution, nodes need to be approved before joining a cluster. Auto Approval of nodes is available, and this can help streamline the cluster provisioning and expansion workflows.
- Enable Approve Nodes Automatically if you do not require an approval gate for nodes to join the cluster
- Select High Availability (Multi Master) if a highly available k8s master configuration is required
- Select Dedicated Master if k8s masters to be tainted not to allow workload pods
Select Enable Proxy if the infrastructure being used to provision the cluster is behind a forward proxy.
Configure the http proxy with the proxy information (ex: http://proxy.example.com:8080)
- Configure the https proxy with the proxy information (ex: http://proxy.example.com:8080)
- Configure No Proxy with Comma separated list of hosts that need connectivity without proxy
- Configure the Root CA certificate of the proxy if the proxy is terminating non MTLS traffic
- Enable TLS Termination Proxy if the proxy is terminating non MTLS traffic and cannot provide the Root CA certificate of the proxy.
Proxy configuration cannot be changed once the cluster is created.
Default subnet used for pod networking is 10.244.0.0/16 Default subnet used for k8s services is 10.96.0.0/12
If you want to customize the subnets used for Pod Networking and K8s Services:
- Select CNI Providers from the drop-down
- Configure the Pod Subnet with the subnet that you want to use
- Configure the Service Subnet with the subnet that you want to use
Cluster Networking cannot be changed once the cluster is created
Click Continue. To proceed further and complete the provisioning process, refer Upstream Cluster Provisioning