Create Cluster on AWS
Managed Kubernetes supports creation of highly available, multi-master Kubernetes clusters on AWS that can tolerate the failure of one or more master nodes as well as an entire availability zone (AZ) going down. This is critical for running production workloads in Kubernetes.
A highly available cluster is composed of at least 3 master nodes, each running an instance of etcd.
To create a cluster on AWS, you must first have an AWS cloud provider. Refer to AWS Cloud Provider Management to create a new AWS cloud provider.
Follow the steps given below to create a Kubernetes cluster on AWS.
Any instance type from the current generation instance families can be used. Instance types from previous generation instance families (t1, m2, m1, and c1) cannot be used. For details on the different instance families, please see the AWS documentation.
- Navigate to Kubernetes>Infrastructure>Clusters.
- Click Add Cluster.
- Enter following information for Cluster Configuration:
| Field | Description |
|---|---|
| Cloud Provider | From the drop down select your desired AWS cloud provider |
| Name | The name of the cluster |
| Region | Select the AWS region to deploy this cluster into |
| Availability Zone | Select one or more Availability Zones within this region to deploy the master nodes of this cluster into. Select at-least 3 availability zones for high availability. |
| Operating System | The operating system version for the nodes deployed in the cluster. Note that you are only selecting the operating system major version. |
| Master Node Instance Type | Instance type for the master node. Platform9 recommends m4.large
instance type for master and instance type from the m4, t2, c4,
and r4 instance families for worker nodes. |
| Worker Node Instance Type | Instance type for the worker node |
| SSH Key | The SSH key your public cloud account has access to. AWS injects the keys into the node while deploying it. The SSH key is useful for debugging purpose if you ever need to log in to the node. |
| Number of Master Nodes | Number of master nodes in the Kubernetes cluster |
| Number of Worker Nodes | Number of worker nodes in the Kubernetes cluster |
| Privileged | Select the check box to enable the cluster to run privileged containers |
- Follow the rest of the options for networking configuration. See AWS Network Integrations.
- Review the cluster configuration and if everything looks okay, click Create Cluster
The cluster is created on AWS.
You can now start deploying your applications on the newly created Kubernetes cluster.
All existing and new AWS clusters in PMK must be configured with an is_update flag and restricted security group rules. Without this cluster updates(such as AMI updates) and upgrades may fail. Please reach out to Platform9 support for this configuration.