Running EKS control plane and data plane on premises with an Outposts local cluster

A 3 things to consider fromr question requirement control plane location - onprem data plane location - onprem management - AWS EKS anywhere it managed by customer so BD out https://anywhere.eks.amazonaws.com/docs/concepts/eksafeatures/#comparing-amazon-eks-anywhere-to-amazon-eks Extended clusters – Run the Kubernetes control plane in an AWS Region and nodes on your Outpost. Local clusters – Run the Kubernetes control plane and nodes on your Outpost https://docs.aws.amazon.com/eks/latest/userguide/eks-deployment-options.html https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts.html

The correct answer is A. Install an AWS Outposts server in the on-premises data center. Deploy Amazon EKS by using a local cluster configuration on the Outposts server for the production workloads. The key requirement is that the company needs an AWS managed solution for Kubernetes management. While EKS Anywhere provides a consistent Kubernetes experience with Amazon EKS, it is a self-managed solution where the customer is responsible for managing the underlying infrastructure and control plane. On the other hand, AWS Outposts allows running AWS services, including Amazon EKS, on-premises. When deploying Amazon EKS on an Outposts server using a local cluster configuration, the EKS control plane and data plane reside on the Outposts server in your data center, meeting the requirement of having the production workloads on-premises. Additionally, Amazon EKS on Outposts is fully managed by AWS, handling provisioning, upgrading, and lifecycle management of the Kubernetes control plane, providing the least operational overhead.

With EKS LOCAL clusters on Outposts, you can run the Amazon EKS control plane and data plane entirely on the Outposts hardware on-premises.Also, it's an AWS managed solution.

It's A, EKS Everywhere = Operational Overhead, and it said it needs to be managed by AWS

B Option A (AWS Outposts with local EKS cluster): While this can run EKS on premises, managing an AWS Outposts server and the associated EKS infrastructure might involve more overhead compared to EKS Anywhere. Option C (AWS Outposts with extended EKS cluster): Similar to option A, this involves managing the Outposts server and integrating it with your on-premises environment, which could increase the complexity and operational overhead. Option D (AWS Outposts with EKS Anywhere): This combines managing an Outposts server with deploying EKS Anywhere, which adds unnecessary complexity and overhead compared to deploying EKS Anywhere directly on the company's hardware.

EKS anywhere!!!

Vote A because by using outpostM EKS is AWS managed service but running on local. Question require AWS managed solution for Kubernetes management. If EKS Anywhere with control plane on prem not AWS cloud, then it's self managed cluster.

A - Control Plane has to be on-prem (not case for Outpost)

B - Correct. The requirement is to use on-premise hardware with AWS managed EKS that means EKS Anywhere which leverages on-premise hardware with full control over both the control plane and data plane

A - correct.

Option A: requirement is ask for AWS Managed Solution and AWS Outpost give you that option https://docs.aws.amazon.com/managedservices/latest/userguide/outposts.html Not Option B : Unlike Amazon EKS in AWS Cloud, EKS Anywhere is a user-managed product that runs on user-managed infrastructure. You are responsible for cluster lifecycle operations and maintenance of your EKS Anywhere clusters. https://anywhere.eks.amazonaws.com/docs/overview/

https://anywhere.eks.amazonaws.com/docs/concepts/eksafeatures/#:~:text=With%20Amazon%20EKS%20on%20Outposts,with%20EKS%20Anywhere%20automation%20tooling.

Correct answer is A. It is not C because EKS Anywhere cluster is a customer-managed product that runs on customer-managed infrastructure. Ref: https://aws.amazon.com/eks/eks-anywhere/faqs/

Correct answer is A You can use Amazon EKS to run on-premises Kubernetes applications on AWS Outposts. You can deploy Amazon EKS on Outposts in the following ways: Extended clusters – Run the Kubernetes control plane in an AWS Region and nodes on your Outpost. Local clusters – Run the Kubernetes control plane and nodes on your Outpost. https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts.html

The correct answer is A: when deploying EKS on an Outpost server in a local cluster configuration, the control plane and data plane reside on-premises, but the control plane is AWS-managed. B is incorrect. Although for EKS-A, the control plane and data plane reside on-premises, it is not AWS-managed but completely customer-managed (both control plane and data plane). C is incorrect because in an extended cluster configuration on AWS Outpost, the control plane runs inside the AWS cloud, not on the outpost server on-premises. D is incorrect because you do not combine EKS-A and Outpost.

Answer is B. The requirement is that both control plane and data plane will reside on premise. If you deploy EKS using extended cluster the control plane lies within AWS region. You need a local cluster for the control plane to reside on outpost. Please refer to url below. https://docs.aws.amazon.com/eks/latest/userguide/eks-outposts.html

https://docs.aws.amazon.com/eks/latest/userguide/eks-deployment-options.html

This option provides an AWS-managed solution for Kubernetes management on-premises without the additional complexity of managing an Outposts server.

C is the answer.

C provides an AWS-managed solution for Kubernetes management with minimal operational overhead, as it leverages the capabilities of AWS Outposts and Amazon EKS for on-premises deployment. Avoid additional complexity introduced by deploying EKS Anywhere or managing hardware independently in the on-premises DC. Deploying Amazon EKS using an extended cluster configuration on the Outposts server enables the company to have an EKS cluster with the control plane and data plane residing on-premises.