aws / aws/containers-roadmap

[EKS] [request]: 1-click upgrades support blue/green or reversibility

Open
#1,592 2 comments 26 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**

In this year's re:invent's EKS deep dive, the speaker mentioned that more and more customers were moving from 1-click upgrade to blue/green EKS deployments.
I'd like to see the option to blue/green the API server with the same "1-click" ease.
This will enable one of AWS' well architected framework best practices "[Make frequent, small, **reversible** changes](https://docs.aws.amazon.com/wellarchitected/latest/framework/a-prepare.html)"

**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?**
Reliable, reversible kubernetes upgrades currently require spinning up a new cluster and migrating workloads to it. This requires managing migration automation or spending resources on migration toil.

**Are you currently working around this issue?**
self-managed blue/green EKS deployments.

Contributor guide

Open the contributing guide

Research direction

The request names Amazon EKS and self-managed blue/green deployments, but no repository files, tests, or entry points. Start by clarifying the desired EKS upgrade and reversibility workflow and its constraints; done would be an agreed implementation path for one-click blue/green upgrades or rollback support.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, devops, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.