A startup company has developed its on-premises SAAS product using standard Kubernetes. Kubernetes has proved to be a success because of its feature of easily deploying, managing the worker nodes and managing containerized applications at scale. The R&D team also gained adequate Kubernetes experiences, including related tools like kubectl. Recently, the CTO of the company has proposed to migrate the whole product to the AWS platform. They need a managed service that runs Kubernetes on AWS without installing, operating, and maintaining their own Kubernetes control plane or nodes. How should they easily design the migration and manage Kubernetes with the least code modification?

Answer options:

A.Provision and run Kubernetes on powerful EC2 instance types such as c5 to fully manage the Kubernetes deployment.
B.Run Kubernetes in Amazon Elastic Kubernetes Service (EKS) without needing to provision or manage master instances.
C.In Amazon ECR, store, encrypt, and manage container images for fast deployment. Manage and run Kubernetes clusters in Amazon Elastic Container Service (ECS).
D.Configure and run Kubernetes in AWS Elastic Container Registry without having to manage servers or clusters.

Correct Answer – B
Option A is incorrect because this option should be used when you want to manage Kubernetes by yourself fully.
Option B is CORRECT because applications running on Amazon EKS are fully compatible with applications running on any standard Kubernetes environment, and can be easily migrated, whether running in on-premises datacenters or public clouds. With EKS, there is no need to refactor the code. According to https://docs.aws.amazon.com/eks/latest/userguide/what-is-eks.html, Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that you can use to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes.
Option C is incorrect because the appropriate service to manage and run Kubernetes should be EKS instead of ECS.
Option D is incorrect because AWS ECR is a docker registry service. It is not the service to manage the Kubernetes services.