-
Updated
Jan 7, 2022 - Shell
eks
Here are 697 public repositories matching this topic...
-
Updated
Feb 2, 2022 - C++
-
Updated
Feb 2, 2022 - HCL
What would you like to be added:
Cilium is our default CNI solution on EKS-A clusters. It would be beneficial to enable Cilium metrics so that existing Prometheus could be configured to scrape those targets.
NTH Queue-Processor should catch the ASG Launch Lifecycle Hook and complete it once the node has joined the k8s cluster successfully. Since ASG considers the instance ready when EC2 health checks pass rather than when it actually joins the k8s cluster, if ASG performs Launch-Before-Terminate, a node could be terminated before the new node is ready to go.
-
Updated
Feb 2, 2022 - Shell
-
Updated
Sep 25, 2021 - Python
-
Updated
Feb 2, 2022 - HCL
-
Updated
Jan 4, 2022 - Shell
-
Updated
Nov 21, 2019 - Python
-
Updated
Sep 16, 2021 - Dockerfile
-
Updated
Jan 8, 2022 - HCL
-
Updated
Jan 20, 2022 - HTML
k8s_taints are not documented right now.
see https://github.com/aws-samples/aws-eks-accelerator-for-terraform/blob/main/modules/aws-eks-managed-node-groups/locals.tf#L24
Here is a working example you can use:
k8s_taints = [{key= "purpose", value="execution", "effect"="NO_SCHEDULE"}]I haven't tested it with fargate profiles:
https://github.com/aws-samples/aws-eks-acc
-
Updated
Jan 31, 2022 - PHP
-
Updated
Dec 17, 2021 - HCL
-
Updated
Dec 21, 2021 - Python
-
Updated
Feb 2, 2022 - Python
-
Updated
Sep 24, 2021 - Go
-
Updated
Jul 20, 2019
-
Updated
Jul 15, 2021 - Go
-
Updated
Feb 2, 2022 - HCL
Some log entries are using V(1) but still get emitted by default.
We should have a way to mute debug logs using a flag.
-
Updated
Aug 2, 2021 - HCL
-
Updated
Nov 7, 2021 - Shell
-
Updated
Jan 27, 2022 - Python
-
Updated
Apr 19, 2021 - TypeScript
Improve this page
Add a description, image, and links to the eks topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the eks topic, visit your repo's landing page and select "manage topics."
What feature/behavior/change do you want?
Add the ability to set the maximum instance lifetime of instances in node groups:
https://docs.aws.amazon.com/autoscaling/ec2/userguide/asg-max-instance-lifetime.html
Why do you want this feature?
We'd like to ensure that our instances don't hang around for too long and so this would be a nice feature to have.