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

Support rolling_upgrade_policy for vm module #234

Conversation

0x46616c6b
Copy link
Contributor

Background

I like to have the rolling_upgrade_policy options for the VM module configurable. This helps to reduce downtimes or inaccessibilities for TFE.

How Has This Been Tested

I forked the module and tested it in my production TFE environment. (I apply changes for TFE inside of TFE, so it is crucial not to have all VMs restarted at the same time.)

@0x46616c6b 0x46616c6b requested a review from a team as a code owner October 16, 2023 13:34
@nikolasrieble
Copy link
Contributor

I appreciate the PR @0x46616c6b, and apologize for only getting to the review so late.

If I understand this correctly, then using the rolling upgrade policy directly conflicts with our upgrade guidance.

If you have multiple TFE nodes up, they are coupled by the database. Having multiple nodes on different version will likely lead to conflicts, since database migrations might lead the schema changes.

That is why currently upgrading TFE requires the user to stop TFE completely - which conflicts with a rolling upgrade.

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