An installation-specific plan
Record the current version, deployment method, topology and dependencies. Identify the supported target, required stops, prerequisites and acceptance checks.
GitLab Upgrades
Plan a self-managed GitLab upgrade around your installation. Agree the version path, checks and recovery procedures before the maintenance window.
Read the case studyBefore the maintenance window
Version, topology and dependencies
Backups, restore and stop/go criteria
Instance, pipelines and integrations
A customer story
Financial services organisation
A financial services organisation was running GitLab on-premises at version 14. Ageing hardware, slow builds and unexpected downtime were affecting developers. Security patches had not been applied, newer features were out of reach, and an undetected HTTP vulnerability remained open in the network.
OTTRA upgraded the instance to the then-current GitLab release, restoring security patch coverage and unlocking AI features without increasing licensing costs. We established a rolling 12-month programme of zero-touch upgrades through a dedicated runner connected to the customer’s infrastructure. The customer controlled when upgrades ran; hypercare support and immediate rollback capability were part of that programme.
During the engagement, OTTRA identified and resolved the HTTP vulnerability. We also recommended moving from a High Availability configuration to a Geo instance on AWS reference architecture, significantly reducing monthly infrastructure costs while improving reliability.
Your deliverables
Several versions behind, facing required upgrade stops or unsure what depends on the instance? Start with its version and topology, using current GitLab guidance.
Record the current version, deployment method, topology and dependencies. Identify the supported target, required stops, prerequisites and acceptance checks.
Run the agreed sequence in the scheduled window. Check the instance, representative pipelines and important integrations against the plan.
Document the result, known issues, remaining actions and owners. Ongoing maintenance has its own schedule, responsibilities and support boundaries.
Agree access, backup and restore procedures, stop/go criteria and who can authorise recovery. Rehearsal needs depend on the environment.
Set the maintenance window, communications, validation and support coverage with the platform owners. Record the checks and hand over remaining actions. Further maintenance is a separate choice.
Your first conversation
Bring your GitLab version, installation method, topology, key integrations and available maintenance windows.
We agree scope, timing and cost before work starts.
Scroll to see allUse the left and right arrow keys to scroll.
Platform partner
Services partner
Certification
Certification
Member