Currently, we have three different source of truth for our alert manager routing configuration. These are: 1. https://gitlab.com/gitlab-com/runbooks/-/blob/master/alertmanager/alertmanager.yml.erb 1. https://gitlab.com/gitlab-cookbooks/gitlab-alertmanager/blob/master/templates/default/alertmanager.yml.erb 1. An encrypted file, manually stored in GCS, and not regularly updated. See https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/monitoring/-/blob/master/bin/k-ctl#L57 for details The first two are now relatively in check with one another, but effort needs to be made to unify all three routing configs. ## Proposal Add a pipeline to the runbooks repo to generate the config and store it encrypted in GCS. Then adapt the chef repo to use this GCS file, rather than the ERB directly. (Placeholder, more to follow) ------------------------------------------------------ Related: * https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/214 * https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/7071 * https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/9572 * https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-helmfiles/-/merge_requests/16 * https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/10045 cc @ggillies @skarbek @jarv @marin @craigf