We are currently implementing a new Pega application in a client-managed cloud. We use Amazon Web Services (AWS) as our cloud provider. On this basis, we use the Amazon Elastic Kubernetes Service (EKS) as our Kubernetes provider.      AWS offers the Amazon Elastic Kubernetes Service (EKS) in three main variants:

1. Classic EKS variant with self-managed worker nodes (https://docs.aws.amazon.com/eks/latest/userguide/worker.html). In this variant, the customer has to completely manage the EC2 instances for the Kubernetes data plane on which the Pods run.
2. EKS variant with managed node groups (https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html). Modified version of 1 at which AWS takes over large parts of the management of the EC2 instances for the Kubernetes Data Plane.
3. EKS on Fargate (https://docs.aws.amazon.com/eks/latest/userguide/fargate.html). As a customer, you don't have to manage the EC2 instances in the cluster yourself. You only specify the Pods here (e.g. with their memory requirements). AWS automatically allocates the underlying instances. As a customer, you have no direct access to these instances and you do not see them as such in your own AWS account.

Unfortunately, neither in the Platform Support Guide (https://community.pega.com/knowledgebase/documents/platform-support-guide-8x) nor on the Client-managed cloud page (https://community.pega.com/knowledgebase/articles/client-managed-cloud/cloud/client-managed-cloud) we found a reference to the EKS variant(s) supported  by Pega.

Hence my questions to Pega:

1. Can we assume that a Pega installation can work together with all three AWS EKS variants without problems?
2. Does Pega have any relevant experience and / or recommendations as to which of the three AWS EKS variants should best be used in conjunction with Pega?

We'd prefer to use the EKS on Fargate variant as AWS does all of the Data Plane management for us.

***Edited by Moderator Kayla to update Platform Capability tags****