Giters
TwiN
/
aws-eks-asg-rolling-update-handler
Handles rolling upgrades for AWS ASGs on EKS
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
43
Watchers:
3
Issues:
20
Forks:
4
TwiN/aws-eks-asg-rolling-update-handler Issues
SetDesiredCapacityInfo lowered the number of nodes in ASG
Closed
a year ago
Comments count
2
Ability to bump secondary ASG if primary is full
Updated
a year ago
Ability to roll nodes at a specific time range
Updated
a year ago
Comments count
1
The handler sometimes doesn't cordon any node
Closed
a year ago
Comments count
9
Cordon all outdated nodes before any rolling update action
Closed
2 years ago
Comments count
6
Handle rolling upgrade when ASG desired capacity has reached max size
Updated
2 years ago
GracePeriod in client.Drain() should be configurable
Closed
2 years ago
Comments count
1
1.4.2 fails to drain nodes
Closed
2 years ago
Comments count
2
Get ASGs to manage based on tag
Closed
2 years ago
Comments count
1
Unable to increase ASG desired size: unable to increase ASG
Closed
3 years ago
Comments count
3
deployed the handler successfully, but nothing happens just write staring execution and execution took ...
Closed
3 years ago
Comments count
3
Panic while upgrading EKS ASGs
Closed
3 years ago
Comments count
4
High Availability (HA) for aws-eks-asg-rolling-update-handler
Closed
3 years ago
Comments count
4
There is a potential you won't get all ASGs returned if you have more than 50 ASGs in the account
Closed
3 years ago
Comments count
2
Handle different hostname label options
Closed
4 years ago
Comments count
3
Create /health endpoint and report health there instead of panicking
Closed
4 years ago
Occasional deadlock during drain
Closed
4 years ago
Unable to terminate instance when desired capacity equals ASG min size
Closed
4 years ago
Filter out pods from daemon sets when calculating resources
Closed
4 years ago