-
Notifications
You must be signed in to change notification settings - Fork 476
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
feat: enable precondition on default_node_pool
for autoscaling with node pool type
#484
feat: enable precondition on default_node_pool
for autoscaling with node pool type
#484
Conversation
@microsoft-github-policy-service agree |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep 1 change per PR.
I added some comments to the new condition.
The old condition is correct, and should also be kept in place together with the new one you are proposing.
@lonegunmanb we should check with the product team if anyone is still actually using AvailabilitySet
instead of VirtualMachineScaleSets
. Because most customers are using multiple node pools we could just enforce the use of VirtualMachineScaleSets
for the sake of simplicity.
5df4274
to
5ebd001
Compare
5ebd001
to
406f1a3
Compare
public_network_access_enabled
attributedefault_node_pool
for autoscaling with node pool type
Potential Breaking Changes in 406f1a3: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ishuar for opening this pr! Almost LGTM but only one comment.
Btw, apology for our latest merged pr but now we have code conflict, would you please rebase your branch with the latest main branch? Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ishuar, LGTM!
Describe your changes
Incorrect precondition on node poolsdefault_node_pool
for autoscaling with node pool type.Enable autoscaling only when the node_pool type is VirtualMachineScaleSets, otherwise throw an error.
✅ The below workflow is expected.
The Module had a bug with incorrect precondition on resourceazurerm_kubernetes_cluster_node_pool
at herevariable
agents_type
is not relevant toazurerm_kubernetes_cluster_node_pool
, only applicable todefault_node_pool
in theazurerm_kubernetes_cluster
resource.It might be working because of the default value of
agents_type
variable set toVirtualMachineScaleSets
, ref @ herebut if the value is updated, additional node pools are not possible to create.
If we make following change to multiple_node_pools example. ( adding
agents_type = "Iamfake"
). The plan fails.Click to view the plan with updated value
public_network_access_enabled
As the azure provider config is
version = ">= 3.80.0, < 4.0"
public_network_access_enabled is deprecated and not passed to azure API, hence can be removed and cause no effect in the last version released on main branch.Issue number
N/A
#000
Checklist before requesting a review
CHANGELOG.md
fileThanks for your cooperation!