Draft: feat: Slim Upgrade methodology
What does this MR do?
- Introduces a set of tags which enable a reduced run of Ansible in order to accomplish an upgrade.
- The tag name
gitlab_application_upgrade
was chosen to signify this being targeted for upgrading only GitLab specifically. - This tag has been added for both omnibus and chart installations thus is able to upgrade either/both installation methods in the same run.
- Since Hybrid installs do not manage Post Deployment Migrations properly, this is still not contributing anything to Zero Downtime Upgrades.
- Since we are not orchestrating Geo, no changes occur to this area.
Related issues
gitlab-com/gl-infra/delivery#20067 (closed)
Author's checklist
When ready for review, the Author applies the workflowready for review label and mention @gl-quality/get-maintainers
:
- Merge request:
-
Corresponding Issue raised and reviewed by the GET maintainers team. -
Merge Request Title and Description are up-to-date, accurate, and descriptive -
MR targeting the appropriate branch -
MR has a green pipeline -
MR has no new security alerts in the widget from the Secret Detection
andIaC Scan (SAST)
jobs.
-
- Code:
-
Check the area changed works as expected. Consider testing it in different environment sizes (1k,3k,10k,etc.). -
Documentation created/updated in the same MR. -
If this MR adds an optional configuration - check that all permutations continue to work. - [-] For Terraform changes: set up a previous version environment, then run a
terraform plan
with your new changes and ensure nothing will be destroyed. If anything will be destroyed and this can't be avoided please add a comment to the current MR.
-
-
Create any follow-up issue(s) to support the new feature across other supported cloud providers or advanced configurations. Create 1 issue for each provider/configuration. Contact the Quality Enablement team if unsure.
Edited by John Skarbek