Skip to content
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

hotfix(privatek8s): no upgrade_settings for spot instances node pools #730

Merged
merged 1 commit into from
Jun 18, 2024

Conversation

smerle33
Copy link
Collaborator

fixup #727 no upgrade_settings for spot instances :

"code": "InvalidParameter",
09:28:29  │   "details": null,
09:28:29  │   "message": "The value of parameter agentPoolProfile.upgrade.maxSurge is invalid. Error details: Spot pools can't set max surge. Please see https://aka.ms/aks-naming-rules for more details.",
09:28:29  │   "subcode": "",
09:28:29  │   "target": "agentPoolProfile.upgrade.maxSurge"

@smerle33 smerle33 requested review from a team and dduportal June 18, 2024 08:14
Copy link
Contributor

@dduportal dduportal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Plan: 0 to add, 2 to change, 0 to destroy.

@dduportal dduportal merged commit 1bbc8da into jenkins-infra:main Jun 18, 2024
3 checks passed
smerle33 added a commit that referenced this pull request Jun 18, 2024
following #730 need some formatting
dduportal added a commit that referenced this pull request Jun 18, 2024
…r-ending updated attribute (#732)

Follow up of #727 , #730 and #731

This fixes the never-ending changed attribute `upgrade_settings {}` for
the 2 Spot node pools on `privatek8s`.

It follows the tip found in
hashicorp/terraform-provider-azurerm#24020 (comment)
to avoid having all of our plans trying to change the 2 node pools.

Signed-off-by: Damien Duportal <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants