Skip to content

Chart Bump

Production Change

Change Summary

Upgrade our helm chart.

Change Details

  1. Services Impacted - All GitLab services deployed into Kubernetes
  2. Change Technician - @skarbek
  3. Change Reviewer - @hphilipps
  4. Time tracking - 1.5 hours
  5. Downtime Component - 0

Detailed steps for the change

Pre-Change Steps - steps to be completed before execution of the change

Estimated Time to Complete (mins) - 30 minutes

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 60 minutes

Post-Change Steps - steps to take to verify the change

Estimated Time to Complete (mins) - 5 minutes

  • Validate Green Pipeline for production application

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 20 minutes

Monitoring

Key metrics to observe

There is no change to the application during this rollout, only our helm chart and it's configuration. So long as we have passing piplines, we will have a good change deployment. If any pipeline fails for any reason, we should immediately investigate to validate it wasn't a harmless error. Rollback should occur if a service fails to come up due to the introduced configuration changes of this upgrade.

Summary of infrastructure changes

  • Does this change introduce new compute instances? No
  • Does this change re-size any existing compute instances? No
  • Does this change introduce any additional usage of tooling like Elastic Search, CDNs, Cloudflare, etc? No

Changes checklist

  • This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
  • This issue has the change technician as the assignee.
  • Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Necessary approvals have been completed based on the Change Management Workflow.
  • Change has been tested in staging and results noted in a comment on this issue.
  • A dry-run has been conducted and results noted in a comment on this issue.
  • SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
  • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
  • There are currently no active incidents.
Edited by John Skarbek