EKSCTL-Example-Configurations
amazon-ec2-instance-selector
| EKSCTL-Example-Configurations | amazon-ec2-instance-selector | |
|---|---|---|
| 5 | 4 | |
| 11 | 775 | |
| - | 2.7% | |
| 10.0 | 6.2 | |
| over 1 year ago | 24 days ago | |
| Go | ||
| - | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
EKSCTL-Example-Configurations
-
How are most EKS clusters deployed?
Here's some open source sample configurations for EKSCTL which uses YAML Aliases to keep it DRY and it shows some best-practices: https://github.com/DevOps-Nirvana/EKSCTL-Example-Configurations
-
Anybody using spot instances for worker nodes?
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.
-
Monthly 'Shameless Self Promotion' thread - 2023/01
EKSCTL example configurations that are real world useful examples of how to use EKSCTL and keep your configuration DRY with YAML Aliases. Just updated today with more examples, and tweaks based on recent experience.
-
Migrate from self managed K8 Environment to EKS using terraform
I’ve got some example commands and example configs on GitHub. https://github.com/DevOps-Nirvana/EKSCTL-Example-Configurations
amazon-ec2-instance-selector
-
Anybody using spot instances for worker nodes?
sounds like https://github.com/aws/amazon-ec2-instance-selector
- aws/amazon-ec2-instance-selector: A CLI tool and go library which recommends instance types based on resource criteria like vcpus and memory
-
How reliable are Spot Instance interruption signals?
These have been recently deprecated. In order to reduce interruptions I would recommend you to diversify over multiple instance types, ideally using https://github.com/aws/amazon-ec2-instance-selector and to use EC2 fleet API with the capacity optimized allocation strategy.
-
Ec2instances.info now has Spot pricing information, is there anything else you'd like to see?
There's a tool/Golang library released by AWS that does something like that.
What are some alternatives?
provider-terraform - A @crossplane provider for Terraform
ec2-instances-info - Golang library for specs and pricing information about AWS EC2 instances based on the data from www.ec2instances.info
kube-reqsizer - A Kubernetes controller for automatically optimizing pod requests based on their continuous usage. VPA alternative that can work with HPA.
amazon-ec2-metadata-mock - A tool to simulate Amazon EC2 instance metadata
featbit - A feature flags service written in .NET
ec2instances.info - Amazon EC2 instance comparison site
Universal-Kubernetes-Helm-Charts - Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
AutoSpotting - Saves up to 90% of AWS EC2 costs by automating the use of spot instances on existing AutoScaling groups. Installs in minutes using CloudFormation or Terraform. Convenient to deploy at scale using StackSets. Uses tagging to avoid launch configuration changes. Automated spot termination handling. Reliable fallback to on-demand instances.
playwright-testing
ec2-macos-init - EC2 macOS Init is the launch daemon used to initialize Mac instances within EC2.
dyrectorio - dyrector.io is a self-hosted continuous delivery & deployment platform with version management.
aws-utils - A small collection of AWS utilities, packaged as a single standalone binary.