Move AWS node group system nodes to Karpenter Node Pools
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
We're currently using a mix of AWS managed Node Groups (for the system pods) and Karpenter node pools for workbench workloads. We need to switch to using one method of management to simplify and consolidate, and also offer additional features that node groups do not provide, such as automatic expiration of nodes to force AMI updates.
Related to https://positpbc.atlassian.net/browse/PTDC-181
Once this ticket is done, we need to upgrade affected customers to rotate nodes on at least a monthly basis.
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
No files, tests, or entry points are named. Start by reading the AWS managed Node Group and Karpenter Node Pool configuration, then review PTDC-181; done means system pods use the consolidated Karpenter approach and affected customers can rotate nodes at least monthly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100