Deploying an Amazon EKS Application Cluster
This guide describes how to install (deploy) MLOps Platform application nodes to Amazon Elastic Kubernetes Service (Amazon EKS) in an AWS cloud — i.e., deploy an AWS EKS platform application cluster.
Configuring an EKS Application Cluster
- Kubernetes Kind
- Set this to
New EKS Cluster.
- Root Block Device Type
- Leave this set to
General Purpose SSD.
- Root Block Device Size
- The size of the EBS for the control plane.
- SSH Key Pair Kind
The type of key pairing to use for SSH connections to the EKS application cluster:
New— Create a new SSH key. Existing— Use an existing SSH key. None— Don't use any SSH key.
Note that when this option is set, you cannot use SSH to connect to the EKS application nodes.
- SSH Whitelist CIDRs
- Leave this empty.
- Node Groups
You can group application nodes in the EKS application cluster into groups.
The installer predefines a default node group named "iniital". You can select the edit icon for this group to edit its configuration, but you cannot delete this group or change its minimal number of instances (1). The minimum number of instances (
Min # of instances) for the default node group is currently not configurable.
You can select the plus-sign icon (
+) to define one or more additional custom node groups. You must select a lifecycle type for the node group. The default is On Demand.
Configure the following parameters for either On Demand or Spot node groups.
- The name of the node group.
The EC2 instance lifecycle type. Choose On Demand or Spot
On Demand—recommended for applications with workloads that cannot be interrupted
Spot—cost-effective instances which are flexible about when applications are run and if they can be interrupted
- # of Instances
- The number of instances (nodes) to deploy for this group.
- Min # of Instances
- The minimum number of nodes in the group.
For the default node group, the value of this parameter is currently not configurable. For additional groups, you can set this parameter to any positive number or to zero. For high availability, it's recommended to have a minimum of two application nodes in each group.
- Max # of Instances
- The maximum number of nodes in the group.
- The EC2 instance size for the nodes in the group.
- Min # of CPUs
- The minimum number of CPUs in each node.
- Max # of CPUs
- The maximum number of CPUs in each node.
- Min # of GPUs
- The minimum number of GPUs in each node.
- Max # of GPUs
- The maximum number of GPUs in each node.
- Min amount of memory (GB)
- The minimum amount of memory (GB) in each node.
- Max amount of memory (GB)
- The maximum amount of memory (GB) in each node.
If you selected On Demand as your lifecycle type you will need to configure the size of the node group.
If you selected Spot as your lifecycle type, you will need to configure the parameters for each node in the group.
When you're done, proceed to Step 9 of the platform's AWS installation guide.