[EKS] [request]: Support to select release channel of EKS cluster
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
**Tell us about your request**
Allowing users to select the version of Kubernetes from broader range of release channels to try and test new features like GKE
**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?**
I would like to deploy newer version of Kubernetes in development environment even if AWS doesn't consider it to be production ready,
which means that users don't care about the SLA compliance.
Upstream Kubernetes releases new features or bug fixes so often, but in EKS, we have to hold our finger and wait until AWS announces to support new version of Kubernetes, which is battle-tested by AWS.
So, we have to wait for a longer term to check new features of Kubernetes even if we use it on development environment.
It'd be great if we can choose Kubernetes release channels like GKE recently announced.
**Are you currently working around this issue?**
Deploy Kubernetes cluster on EC2 by kubeadm to check new features.
**Additional context**
I think I tell enough informations.
**Attachments**
https://cloud.google.com/kubernetes-engine/docs/concepts/release-channels
Contributor guide
Research direction
Start with the EKS request and the linked GKE release-channels documentation; no repository files, tests, or entry points are identified. Done would require an agreed design and support for selecting Kubernetes release channels for EKS, including newer versions for development use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100