[EKS] [request]: A reliable EKS AMI release process : followup
Open
EKS
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
EKS had a release consistency problem for a long time that was captured in https://github.com/aws/containers-roadmap/issues/319
while this was fixed for a while, this seems to have reoccurred in https://github.com/awslabs/amazon-eks-ami/issues/2518 and the response seems unaware of this long standing issue that EKS had solved
Contributor guide
Research direction
Start by reading the linked containers-roadmap issue #319 and amazon-eks-ami issue #2518 to compare the earlier fix with the reported recurrence. Clarify the expected EKS AMI release consistency and the owner or entry point for resolving it; done should mean the release process and its expected behavior are explicitly addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100