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

#24898: azurerm_linux_virtual_machine_scale_set and azurerm_windows_virtual_machine_scale_set - support max_surge_instances for vmss rolling upgrades #24914

Merged
merged 1 commit into from May 6, 2024

Conversation

harshavmb
Copy link
Contributor

@harshavmb harshavmb commented Feb 16, 2024

Support max_surge_instances for azurerm_linux_virtual_machine_scale_set and azurerm_windows_virtual_machine_scale_set rolling upgrades.

Fixes #24898.

@katbyte katbyte changed the title #24898: Support max_surge for vmss rolling upgrades #24898: azurerm_linux_virtual_machine_scale_set and azurerm_windows_virtual_machine_scale_set - support max_surge for vmss rolling upgrades Feb 17, 2024
Copy link

This PR is being labeled as "stale" because it has not been updated for 30 or more days.

If this PR is still valid, please remove the "stale" label. If this PR is blocked, please add it to the "Blocked" milestone.

If you need some help completing this PR, please leave a comment letting us know. Thank you!

@github-actions github-actions bot added the stale label Mar 18, 2024
@stephybun
Copy link
Member

Any updates on this @harshavmb, or could we close this until you're ready to come back to this?

@github-actions github-actions bot removed the stale label Apr 15, 2024
@harshavmb
Copy link
Contributor Author

Hi @stephybun ,

I did give a pause on this PR as I felt max_surge is still a preview feature. I shall check the docs once again & rework on this.

@stephybun
Copy link
Member

@harshavmb if this is still in preview would you mind closing this PR. It can always be re-opened once it's gone GA and ready for review.

@harshavmb
Copy link
Contributor Author

Hi @stephybun ,

I did have another look on this. However, it's failing with below error when I run acceptance tests locally.

The subscription is not registered for Microsoft.Compute/MaxSurgeRollingUpgrade. Please enable this feature on the subscription.

RestAPI specs here, don't say this as a preview feature.

I could enable this feature at subscription level & I know this would work but don't think the acceptance tests run at your end will allow such tests.

Please have a say on this..

@stephybun
Copy link
Member

@harshavmb I've registered the feature on our test subs. If this is ready can you please move this PR out of draft?

@github-actions github-actions bot added size/S and removed size/XS labels Apr 22, 2024
@harshavmb harshavmb marked this pull request as ready for review April 22, 2024 12:54
@harshavmb harshavmb changed the title #24898: azurerm_linux_virtual_machine_scale_set and azurerm_windows_virtual_machine_scale_set - support max_surge for vmss rolling upgrades #24898: azurerm_linux_virtual_machine_scale_set and azurerm_windows_virtual_machine_scale_set - support max_surge_instances for vmss rolling upgrades Apr 22, 2024
@harshavmb harshavmb requested a review from katbyte April 22, 2024 12:57
@harshavmb
Copy link
Contributor Author

@stephybun / @katbyte ,

Over to you for review..

Copy link
Collaborator

@katbyte katbyte left a comment

Choose a reason for hiding this comment

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

Thanks @harshavmb - LGTM 🚂

@katbyte katbyte merged commit 5a006e2 into hashicorp:main May 6, 2024
33 checks passed
@github-actions github-actions bot added this to the v3.103.0 milestone May 6, 2024
katbyte added a commit that referenced this pull request May 6, 2024
@harshavmb harshavmb deleted the github-24898 branch May 7, 2024 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for using a rolling upgrade policy on a scale set that has MaxSurge enabled
3 participants