SPIKE: Investigate Node Group Rebalancing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
We may want to find an automated way to disable the AZRebalance process that runs by default in the Autoscaling Group created for EKS managed node groups. If left on, this can lead to terminating nodes that might have active user sessions and create a disruptive experience. Using a self-managed node group gives us the option to disable AZ rebalancing.
This issue indicates the AWS team is aware of this deficiency with EKS managed node groups and is looking to address it.
Options
- wait for AWS team to handle this for EKS managed node groups
- find a way to update the managed ASG to disable
AZRebalance - use one node group per AZ
- self managed node groups
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked AWS containers-roadmap issue and the four options in this issue. Investigate how EKS managed node groups create and update their Auto Scaling Groups, especially whether AZRebalance can be disabled safely. Done means documenting a viable approach and its disruption trade-offs, or recording why AWS support or an alternative node-group design is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100