Pega AWS EKS Support

General
, , ,
1

AWS offers the Amazon Elastic Kubernetes Service (EKS) in the below 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.

Based on the reply on the other post

Based on the reply from Brett Allen from Pega, it is mentioned that Pega does not support AWS Fargate and the option to use managed node group is not tested but may work.

We are planning to use Option 2. Since the above post is over 3 years ago, could the team please help update if there are any changes to the above.

2

@BrettAllen is this a question you could answer?

3

@SaikatP5 @MarijeSchillern I’ve used managed node groups in my personal lab deployments since then with no issues and don’t see any reason they wouldn’t be suitable. If you’re satisfied with the AMI and other settings EKS uses for the managed group I don’t know of any issues with them.

4

@BrettAllen
Hi We’are plannning to impliment Client Managed Cloud on EKS, and We face same choice.

I understood that I can use managed node groups, but how about EKS Auto Mode or self-managed Karpenter?

Are EKS Auto Mode or self-managed Karpenter supported?

Also I’d like to know why fargate is not suitable.

what does persistent storage volumes that aren’t supported on EKS Fargate mean?

Thanks

5

@KEISUKE.T The persistent storage would have been required for Stream nodes back then. Now with externalized services that may not apply. However Fargate is not tested or specifically supported, nor is any other specific approach to building the cluster. Administration of the cluster is a client responsibility.

6

@BrettAllen
Thank you for your quick reply.
Do you know is there any documents in terms of persistent storage volumes for Stream node?
I’d like to know what technical limitations is.

From Pega’s point of view, is it acceptable to use Fargate as long as it is tested on the user’s side?