Gitlab is currently under maintenance
We are migrating to Gitlab 17.0!
- ✔ 02%: installation of the maintenance page
- ✔ 05%: stop all gitlab services accessing the DB
- ✔ 25%: backup of the DB (it took 1 hour and 17 minutes)
- ✔ 30%: deployment of 2 new and updated postgresql pods
- ✔ 35%: gitlab chart upgrade to 17.0.x
- ✔ 50%: restoration of the db backup and migration to 17.0.1 (restoration started at 2024-06-03 12:26:55 UTC / finished at 2024-06-03 17:51:24 UTC)
- ✔ 55%: prepare the config for multiple database
- ✖ 80%: split of the db:
gitlab-rake gitlab:db:decomposition:migrate"GitLab database already running on two connections"🤔 - ✔ 80%: split of the db: manual steps
- ✔ 65%: manual backup of the db:
pg_dump -U gitlab -h postgresql-prod --format=d --jobs=4 --file=gitlab_db_backup.psql gitlab_production - ✔ 80%: manual restore of the CI db:
pg_restore -U gitlab -h postgresql-ci-prod --jobs=4 --dbname=gitlab_production_ci gitlab_db_backup.psql
- ✔ 85%: verify that the migration completed
- ✔ 90%: Post-migration and clean up
- ✔ 86%:
gitlab-rake gitlab:db:lock_writes - ✔ 88%:
gitlab-rake gitlab:db:truncate_legacy_tables:main (new size 25 GB) - ✔ 90%:
gitlab-rake gitlab:db:truncate_legacy_tables:ci (new size 248 GB)
- ➙ 95%: re-enable gitlab services
- · 97%: re-enable gitlab ingress
- · 100%: disabling the maintenance page 🎉