A guide for creating DKP clusters on AWS console
Before you begin
Simplified Cluster Creation on AWS in the UI
In the selected workspace Dashboard, select the Add Cluster option in the Actions dropdown menu at the top right.
On the Add Cluster page, select the Create DKP Cluster.
Provide some basic cluster details within the form:
Workspace: The workspace where this cluster belongs (if within the Global workspace).
Kubernetes Version: The initial version of Kubernetes to install on the cluster.
Name: A valid Kubernetes name for the cluster.
Add Labels: By default, your cluster has labels that reflect the infrastructure provider provisioning. For example, your AWS cluster may have a label for the data center region and
provider: aws. Cluster labels are matched to the selectors created for Projects. Changing a cluster label may add or remove the cluster from projects.
Region: Select a data center region or specify a custom region.
Configure Node Pools: Specify pools of nodes, their machine types, quantity, and the IAM instance profile.
Machine Type: Machine instance type.
Quantity: Number of nodes. The control plane must be an odd number.
IAM instance profile: Name of the IAM instance profile to assign to the machines.
AMI Image Lookup: You can also specify the base OS, lookup format, and owner ID of the AMI Image, or the AMI ID as part of each pool. Selecting ‘Show Advanced’ within the Configure Node Pools section will show these options.
Base OS: Base OS for Lookup search.
Lookup Format: Lookup Format string to generate AMI search name from.
Owner ID: Owner ID for AMI Lookup search.
AMI ID: AMI ID to use for all nodes.
Worker Availability Zone: Worker Zones for a region (worker nodes only).
Add Infrastructure Provider Tags: Specify tags applied on all resources created in your infrastructure for this cluster. Different infrastructure providers have varying restrictions on the usable tags. See the AWS Tags User Guide for more information on using tags in AWS.
Select Create to begin provisioning the cluster. This step may take a few minutes, taking time for the cluster to be ready and fully deploy its components. The cluster automatically tries to join, and should resolve once it is fully-provisioned.