Major Gitlab Upgrade 16.11.4 to 17.0.2

Steps required to perform Major Gitlab Upgrade 16.11.4 to 17.0.2 & Pre-requisites required before performing major upgrade.

We’re currently at 16.11.4 (7.11.4 chart version) and we’re having self managed Gitlab and configured using Helm and we’ve set up database on postgreSQL v14.
Request you to kindly share the steps like pre-upgrade, upgrade & post upgrade steps & checks.
And if we’ve any pending migration tasks (refer attached) does it causes issue during upgrade?
And how long the DB migration task does usually takes?
And if upgrade fails due to some migration issues(like some people are complaining on 17) what is the rollback plan with steps?

This is the first Major upgrade, I’m performing.

I really appreciate if you provide detailed answers along with links. Please remember ours is not omnibus installation it is Helm way.

Versions

Please select whether options apply, and add the version information.

• Self-managed
• GitLab.com SaaS

Versions

• GitLab (Web: /help or self-managed system information):

Helpful resources

1. Before opening a new topic, make sure to search for keywords in the forum search
2. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
3. Troubleshooting docs: Self-managed GitLab instances.

Thanks for taking the time to be thorough in your request, it really helps!