I'm managing several EKS clusters through Rancher (version 2.12) and have run into a ton of frustrating problems while trying to update Node Groups. The clusters are created directly through Rancher rather than imported, and I'm left feeling like I'm missing something crucial in my setup. Here are the main issues I'm facing: sometimes adding a Node Group is successful and sometimes it's not, which feels pretty unpredictable. Also, I can't seem to change an existing Node Group; I have to create a new one for any updates. Lastly, I'm unable to choose subnets for the Node Group - I have to edit the Rancher cluster CRD object directly to manage that. Any insights or advice would be awesome!
2 Answers
Honestly, I've had the same experience. It’s often better to create your clusters using the EKS modules and then import them into Rancher. It could save you some headaches down the line.
Switching to Infrastructure as Code (IaC) with OpenTofu might be a good route. Managing Rancher within AWS can be tricky, and IaC can add a solid layer of control over your deployments.
Interesting, but how exactly would OpenTofu help me with managing my clusters?