Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
EKSCTL-Example-Configurations
Some sample configurations for EKSCTL.io to help understand how best to use it and increase adoption
-
containers-roadmap
This is the public roadmap for AWS container services (ECS, ECR, Fargate, and EKS).
-
amazon-ec2-instance-selector
A CLI tool and go library which recommends instance types based on resource criteria like vcpus and memory
First, install the AWS Spot Termination Handler to ensure you gracefully handle terminations. Along with other standard things you should install like Cluster Autoscaler to handle failures/scale outs.
Second, make sure you create a spot instance group that attempts to launch MULTIPLE different instance types. This way if one instance type gets flushed, your autoscaler will kick in and launch a different type. Without this, you WILL HAVE DOWNTIME if a sudden price hike and flush occurs. If you're using eksctl I have example configurations that use multi-instance types on Github here.
First, install the AWS Spot Termination Handler to ensure you gracefully handle terminations. Along with other standard things you should install like Cluster Autoscaler to handle failures/scale outs.
Second, make sure you create a spot instance group that attempts to launch MULTIPLE different instance types. This way if one instance type gets flushed, your autoscaler will kick in and launch a different type. Without this, you WILL HAVE DOWNTIME if a sudden price hike and flush occurs. If you're using eksctl I have example configurations that use multi-instance types on Github here.
Avoid managed node groups for now if you like saving money with spot, but leave a thumbs up at https://github.com/aws/containers-roadmap/issues/1903
sounds like https://github.com/aws/amazon-ec2-instance-selector