aws / aws/containers-roadmap

[EKS] [request]: Provide platform version upgrade feature

Open
#1,037 17 comments 149 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Provide platform version upgrade feature

**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 just want to upgrade the EKS platform version for security patch instead of major version upgrade.
From [doc](https://docs.aws.amazon.com/eks/latest/userguide/platform-versions.html) it says
```Automatic upgrades of existing Amazon EKS platform versions are rolled out incrementally. The roll-out process might take some time. If you need the latest Amazon EKS platform version features immediately, you should create a new Amazon EKS cluster.```

I don’t know when the automatic update will be actually performed. For example, the latest platform ver for 1.15 is already ```eks.4``` , however all our 1.15 clusters still stay at ```eks.2``` , there is no automatic upgrade performed.

Even if automatic upgrade is performed, i still prefer manual upgrade, It would be better to let user decide when to upgrade the control plane. Automatic upgrade is kind of risky.

Contributor guide

Open the contributing guide

Research direction

The request concerns Amazon EKS platform versions and links to the AWS platform-version documentation; no repository files, tests, or implementation entry points are mentioned. Start by reviewing that documentation and the issue discussion, then define what a manual control-plane platform-version upgrade would expose and how completion would be verified.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.