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
The documentation in the link below states that we should have at least one node running in a system node pool. I understand the importance of this constraint for running mission-critical pods.
When we have two system node pools in which one node pool has >=1 node and another node pool has 0 this constraint doesn't make sense.
Constraint should check all the system node pools to confirm the collective number of nodes is >=1 instead of checking this constraint for each node pool.
Is there any technical reason why this constraint needs to run on all the system node pools?
The text was updated successfully, but these errors were encountered:
The documentation in the link below states that we should have at least one node running in a system node pool. I understand the importance of this constraint for running mission-critical pods.
https://learn.microsoft.com/en-us/azure/aks/create-node-pools#limitations
When we have two system node pools in which one node pool has >=1 node and another node pool has 0 this constraint doesn't make sense.
Constraint should check all the system node pools to confirm the collective number of nodes is >=1 instead of checking this constraint for each node pool.
Is there any technical reason why this constraint needs to run on all the system node pools?
The text was updated successfully, but these errors were encountered: