-
Notifications
You must be signed in to change notification settings - Fork 316
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
Allow exception for CriticalAddonsOnly taint on system nodepools (or all) #1833
Comments
@palma21 Are we saying, Is it good to go applying - CriticalAddonsOnly taint on default created system nodepool with AKS cluster?. We are having issues right now, we are using terraform. |
This is the ticket to support it. Right now we block it if the taints are applied to all pools. We'll make an exception for this one so you can apply it to all pools (or just the default one) |
Thank you @palma21 , Is there any ETA, when this would be resolved. Appreciate if this could be resolve sooner. |
Thank you for the feature request. I'm closing this issue as this feature has shipped and it hasn't had activity for 7 days. |
Follow up for #1484. To unblock automation like terraform to tag the first (and system) nodepool as well as allow for taints on all nodepools, AKS will always accept CriticalAddonsOnly
The text was updated successfully, but these errors were encountered: