[EKS]: Add the recommended CNI, DNS and kubeproxy versions to the SSM parameter store
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
What do you want us to build?
The recommended EKS optimized AMI for each version is available from the SSM parameter store. It would be useful if the recommended versions of the CNI plugin, CoreDNS and kubeproxy where also available. This would enable better automation of updates/upgrades and it would easier to get notifications when the values change (instead of having to remember to check https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html periodically)
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We've automated the whole management of our application, including EKS. However, while we can update the CNI, CoreDNS and kubeproxy, it only happens when we remember to check the online page and update our automation stack with any new values
**Are you currently working around this issue?**
Manual updates
Contributor guide
Research direction
Start by reviewing the EKS version guidance linked in the issue and the existing SSM parameter store approach for EKS-optimized AMIs. Determine the recommended CNI, CoreDNS, and kubeproxy values for each EKS version, then verify that those values are available in SSM and can support automated updates and notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100