AKS: default max pods && autoscale node group default subnet #1153
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We ran into issues when updating the cluster to use Cilium network policy where both node pools with
Max Pods = 110does not leave enough room in the /24 subnet. This configuration situation would likely cause issues in other upgrade operations states as well.The intent of these changes is to reduce that risk by:
systemandautoscalednode pools (This should still be adequate for default use cases).autoscalednode pool to use a different subnet than thesystemnode pool.The result is that each node pool would use its own subnet and each subnet would have space for up to 5 nodes (10 nodes total by default).