EKS: Migration of workloads between region: There should be a feature where we can easily migrate our EKS cluster or workload to another regions.
- 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**
A process or service to migrate exisiting EKS workload to another region.
**Which service(s) is this request for?**
EKS
**There should be a service or process by which we can easily migrate exisitng EKS cluster or application to another region
**Are you currently working around this issue?**
Using opensource tools like velero, portworks.
Contributor guide
Research direction
Start by reviewing the EKS request and its stated cross-region migration goal, then compare the mentioned Velero and Portworx workarounds. No repository files or tests are named; done would require a defined service or process that can migrate an existing EKS cluster or workload to another region.
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