EKSCTL-Example-Configurations
provider-terraform
| EKSCTL-Example-Configurations | provider-terraform | |
|---|---|---|
| 5 | 3 | |
| 11 | 112 | |
| - | 6.3% | |
| 10.0 | 7.7 | |
| over 1 year ago | 4 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
provider-terraform
-
Options for handling Terraform with ArgoCD
I'm aware of: - A k8s cronjob shelling out to the terraform CLI - flamingo -> Flux -> weaveworks Terraform controller - Terraform cloud operator - Crossplane's terraform provider
-
How are most EKS clusters deployed?
If you really really want to manage everything in kubernetes, I'd suggest trying out Crossplane with the Upbound Terraform provider, too keep the number of CRD's low - there were times when you could literally kill kubernetes with Crossplane CRD's
-
Argo CD with Terraform?
Crossplane hit Cloud Native space a little bit over a year ago and has seen a lot of development and adoption. Instead of competing directly with terraform users they have included a provider that will consume a Terraform workspace. Here is a link to the official provider https://github.com/upbound/provider-terraform
What are some alternatives?
kube-reqsizer - A Kubernetes controller for automatically optimizing pod requests based on their continuous usage. VPA alternative that can work with HPA.
tofu-controller - A GitOps OpenTofu and Terraform controller for Flux
featbit - A feature flags service written in .NET
terranetes-controller - The terraform controller manages the life cycles of a terraform resource, allowing developers to self-serve dependencies in a controlled manner.
Universal-Kubernetes-Helm-Charts - Some universal helm charts used for deploying services onto Kubernetes. All-in-one best-practices
terraform-aws-eks - Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦
playwright-testing
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
dyrectorio - dyrector.io is a self-hosted continuous delivery & deployment platform with version management.
terraform-aws-eks-blueprints - Configure and deploy complete EKS clusters.
ngs - Next Generation Shell (NGS)
unleash - Open-source feature management solution built for developers.