-
Notifications
You must be signed in to change notification settings - Fork 176
add the option to set tags on karpenter EC2 instances per node pool #10170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Conversation
|
Can you confirm this will not force the node rotation and only new nodes will have the new tags? |
99% sure that it does not trigger a rotation because we don't have drift enabled in Karpenter. We do some check in CLM to determine if rotation is needed but I don't think it checks for tags. (I would confirm via a pet cluster :)) |
I can also add one tag in one of the dev clusters after merge to see if the nodes are rotated. Or do you recommend to do it in pet cluster? |
Deployment ChecklistThis change falls under the deployment policy. 💁 Since Nov 10th, we are in the RED deployment zone. This means all changes released to production must adhere to the following requirements:
👉 Regardless of which boxes you click in this comment, merge/deployment will not be blocked. |
|
I tested this solution and the instances were tagged with the new tag without forcing the rotation of the instances by Karpenter. |
add the option to set tags on karpenter EC2 instances per node pool