https://rancher.com/ logo
#general
Title
# general
a

adamant-kite-43734

12/20/2022, 10:27 AM
This message was deleted.
a

agreeable-waiter-30020

12/20/2022, 11:28 AM
That is the intended behavior. When you import the EKS cluster as an EKS cluster, Rancher will take a snapshot of configuration. When it sees a difference in the intended state and the actual state, it will reconcile it. Rancher is supposed to “sync back” changes you make from the AWS console, but there is something happening here that is not doing that. I won’t speculate on that. The easiest way to fix this would be the following two options: 1. Remove the node group from the Rancher UI. That will set the desired state from Rancher and it won’t recreate the node group. 2. Import the cluster as a “generic” cluster instead of an EKS cluster. Rancher won’t reconcile in the same way and wont recreate nodes.
a

acceptable-printer-7134

12/20/2022, 12:07 PM
Thanks @agreeable-waiter-30020 that answers my query. Also what if i just give minimum IAM permissions to Rancher.
a

agreeable-waiter-30020

12/20/2022, 12:18 PM
That won’t change what Rancher tries to do, so you would likely see other errors.
a

acceptable-printer-7134

12/26/2022, 7:40 AM
got that. QQ - can i reimport the cluster as generic. hope it doesn't delete Eks cluster when i remove from rancher UI? @agreeable-waiter-30020
a

agreeable-waiter-30020

12/26/2022, 12:42 PM
If you imported the cluster and didn’t create it from Rancher, then Rancher will not delete it when you remove it from Rancher. Rancher should also clean up its resources from the EKS cluster. I would wait a little bit (like a half-hour) before importing it as generic to allow the cleanup to complete.
👍 1
3 Views