Spot Instances and containers are an excellent combination, because containerized applications are often stateless and instance flexible. In this blog, I illustrate the best practices of using Spot Instances such as diversification, automated interruption handling, and leveraging Auto Scaling groups to acquire capacity. You then adapt these Spot Instance best practices to EKS with the goal of cost optimizing and increasing the resilience of container-based workloads.
Jun 09, 2020 · A Spot Fleet, in which you specify a certain capacity of instances you want to maintain, is a collection of Spot Instances and can also include On-Demand Instances. AWS attempts to meet the target capacity specified by using a Spot Fleet to launch the number of Spot Instances and On-Demand Instances specified in the Spot Fleet request.
You can configure a managed node group with Amazon EC2 Spot Instances to optimize costs for the compute nodes running in your Amazon EKS cluster. How it works To use Spot Instances inside a managed node group, you need to create a managed node group by setting the capacity type as spot .
As soon as the launch configuration is created, you’ll see an option to Create an Auto Scaling group using this launch configuration. Click that to start creating the auto scaling group. Enter a Group name (we’ll use gitlab-auto-scaling-group). For Group size, enter the number of instances you want to start with (we’ll enter 2).
Unfortunately, until the EKS Node Group API natively supports spot and it gets implemented in the terraform provider, there isn't much we can do. Some enterprising folks could probably do some horror using a local-exec provisioner block and calls to the awscli. It wouldn't really be a terraform-native or recommended approach.
Nov 13, 2018 · Currently tk8 cluster destroy rke doesn’t work as it should, to delete the cluster you need to delete the nodes in AWS Web Console followed by theses steps: $ tk8 cluster destroy rke → doesn’t work for now, but deletes the NLB and Target Group remove rke1-role under “Roles” in IAM $ aws iam delete-instance-profil — instance-profile ...
A separate stack is created for the EKS Cluster control plane and the worker node nodegroup. An illustrative example is shown below. Worker Nodes. The AWS EC2 nodes backing the Worker Nodes can be viewed on the AWS Console (EC2 Service). Note that the names of the nodes start with the EKS cluster's name in the Console.