Pega Amazon Elastic Kubernetes Service (EKS) Support
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:
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.
This is correct, test clusters are usually created using eksctl which creates unmanaged node groups. Managed node groups are likely to be fine as well. Fargate would not be suitable because we require persistent storage volumes that aren't supported on EKS Fargate.