Skip to content

Draft: Support near zero-downtime upgrade

Hossein Pursultani requested to merge 6-zero-downtime-upgrade into main

What does this MR do?

This change introduces the workflow to automate the near-zero downtime upgrade as it is implemented in GitLab Operator V1.

The controller consults the status of the GitLab resource to distinguish between install and upgrade workflows. A basic heuristic is incorporated to avoid upgrade gaps which may result in an incosistent state of the GitLab instance.

Reference:

Author's Checklist

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • Ensure a release milestone is set.
  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • MR has a green pipeline on GitLab.com.
  • When ready for review, MR is labeled workflowready for review per the MR workflow.

Expected

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation is created or updated.
  • Tests are added.

Related issues

Closes #6

Edited by Hossein Pursultani

Merge request reports