You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, now the labels and taints schemas are different for autoscaler_nodepools and agent_nodepools. I'm not convinced that this makes a lot of sense...
Is the plan to change all labels/taints to the new more verbose schema? Obviously as maintainers you're free to choose whichever schema you wish (although I personally prefer the original more concise string over the object), but in either case I think it should be consistent.
Thanks :)
The text was updated successfully, but these errors were encountered:
The new schema allows for easier implementation in the cluster-autoscaler codebase. (I had a pr merged for that as well)
Kubernetes labels are maps, and Taints are objects. So it was easier to make them more in line with Kubernetes.
But yeah I will open a PR to fix the wrong example :P
Description
The latest example values for
labels
andtaints
inautoscaler_nodepools
inkube.tf.example
seem wrong:From looking at the code I believe that it should be the following:
However, now the labels and taints schemas are different for
autoscaler_nodepools
andagent_nodepools
. I'm not convinced that this makes a lot of sense...Is the plan to change all labels/taints to the new more verbose schema? Obviously as maintainers you're free to choose whichever schema you wish (although I personally prefer the original more concise string over the object), but in either case I think it should be consistent.
Thanks :)
The text was updated successfully, but these errors were encountered: