This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
fix: correct defaults order for setting IPAddressCount #2358
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.
Reason for Change:
This fixes a regression that landed w/ #2274
The functional bug is this:
If you are using Azure CNI, and you are specifying a custom
IPAddressCount
for either master vm nodes or any node pool vms, those user-provided values will be overwritten by the aks-engine defaults.The IPAddressCount values in MasterProfile and each AgentPoolProfile depend (in part) upon the kublet configuration
--max-pods
; essentially these values are related and need to be configured in concert according to a deterministic ordinality.This PR moves the IPAddressCount default enforcement for both masters and pools to occur after the kubelet defaults codeflow.
The primary fix here is missing UT. :(
Issue Fixed:
Requirements:
Notes: