How VMware Tanzu CloudHealth modernized container workloads from self-managed Kubernetes to Amazon Elastic Kubernetes Service
Containers Blog
This article discusses how VMware Tanzu CloudHealth migrated their container workloads from self-managed Kubernetes clusters running on kOps to AWS managed Amazon Elastic Kubernetes Service (Amazon EKS).
Specifically, the article covers:
- Previous self-managed K8s clusters and related challenges with kOps
- Key drivers to move to a managed solution like Amazon EKS
- Key technical prerequisite evaluation like Kubernetes versions, security, networking, tooling, and node groups
- Migration execution strategy and walkthrough
- Lessons learned during and after the migration
- Conclusion highlighting the benefits achieved by migrating to Amazon EKS
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Mar 14
2024
2024
How VMware Tanzu CloudHealth migrated from self-managed Kafka to Amazon MSK
Sep 17
2024
2024
Unlocking Transformative Benefits of Modernizing VMware workloads to Red Hat OpenShift on AWS
Feb 8
2024
2024
Observing Kubernetes workloads on AWS Fargate with AWS managed open-source services
Jan 22
2024
2024
VMware’s Cloud Journey: AWS Account Management at Scale
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.