I'm currently setting up EKS for a client and I'm very familiar with Kubernetes from my on-prem experiences. I've been looking into Karpenter and the option to run it on Fargate sounds appealing, but an issue I found on GitHub raises some serious concerns. It mentions that using EKS Fargate is not recommended for Karpenter due to a lack of native IAM Roles for Service Accounts (IRSA) support. In fact, it suggests that Fargate might be a dead end. A maintainer also noted that having two dedicated nodes just for Karpenter could actually be more efficient than using Fargate. Since my client has a large setup with hundreds of single-tenant applications across numerous accounts, the prospect of managing hundreds of Karpenter nodes is daunting. How much effort is really involved in managing a managed node group per cluster, especially when looking at 500 clusters? How much can I automate in this scenario? I'm trying to weigh that against the option of using Fargate for Karpenter, which I know has its own limitations, especially since auto mode isn't an option for us for specific reasons.
1 Answer
You might want to consider running EKS in Auto Mode. It comes with Karpenter out-of-the-box and can make things easier, especially for clients without dedicated DevOps support. It really simplifies day-to-day operations compared to managing individual nodes. Besides, people are saying Fargate has its limitations and Auto Mode has pretty much overshadowed it.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures