2024-04-19: Delete unused omnibus secret in ops
Production Change
Change Summary
We migrated the ops.GitLab.net instance to kubernetes however we still have the old secrets in object storage which are not used:
$ gsutil ls gs://gitlab-ops-secrets/gitlab-omnibus-secrets
gs://gitlab-ops-secrets/gitlab-omnibus-secrets/ops.enc
$ vault kv list chef/env/ops/shared | rg 'omnibus'
gitlab-omnibus-secrets
Change Details
- Services Impacted - ServiceChef ServiceVault
-
Change Technician -
@sxuereb
- Change Reviewer - @pguinoiseau
- Time tracking - 10
- Downtime Component - none
Detailed steps for the change
Change Steps - steps to take to execute the change
Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes
-
Set label changein-progress /label ~change::in-progress
-
Move GCS secret to make sure it's not used anywhere: gsutil mv gs://gitlab-ops-secrets/gitlab-omnibus-secrets gs://gitlab-ops-secrets/gitlab-omnibus-secrets-bak
-
Delete Secrets in vault to make sure they are not used vault kv delete -versions 1,2,3,4,5,6 env/ops/shared/gitlab-omnibus-secrets
-
Wait at least 24h -
Delete GCS bucket gsutil rm -r gs://gitlab-ops-secrets/gitlab-omnibus-secrets-bak
-
Destroy Vault secret vault kv destroy -versions 1,2,3,4,5,6 chef/env/ops/shared/gitlab-omnibus-secrets vault kv metadata delete chef/env/ops/shared/gitlab-omnibus-secrets
-
Set label changecomplete /label ~change::complete
Rollback
Rollback steps - steps to be taken in the event of a need to rollback this change
Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes
-
Move GCS bucket back to the normal place gsutil mv gs://gitlab-ops-secrets/gitlab-omnibus-secrets-bak gs://gitlab-ops-secrets/gitlab-omnibus-secrets
-
Undelete secrets vault kv undelete -versions 1,2,3,4,5,6 chef/env/ops/shared/gitlab-omnibus-secrets
-
Set label changeaborted /label ~change::aborted
Monitoring
Key metrics to observe
N/A
Change Reviewer checklist
-
Check if the following applies: - The scheduled day and time of execution of the change is appropriate.
- The change plan is technically accurate.
- The change plan includes estimated timing values based on previous testing.
- The change plan includes a viable rollback plan.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
-
Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
- The change plan includes success measures for all steps/milestones during the execution.
- The change adequately minimizes risk within the environment/service.
- The performance implications of executing the change are well-understood and documented.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
- If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
- The change has a primary and secondary SRE with knowledge of the details available during the change window.
- The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
- The labels blocks deployments and/or blocks feature-flags are applied as necessary.
Change Technician checklist
-
Check if all items below are complete: - The change plan is technically accurate.
- This Change Issue is linked to the appropriate Issue and/or Epic
- 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.
- The change execution window respects the Production Change Lock periods.
- For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
- For C1 and C2 change issues, the 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.) - For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
- For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
- Release managers have been informed prior to any C1, C2, or blocks deployments change being rolled out. (In #production channel, mention
@release-managers
and this issue and await their acknowledgment.) - There are currently no active incidents that are severity1 or severity2
- If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.
Edited by Steve Xuereb