Test plan for `alertmanager` component upgrade

Copy the following test plan to a comment of the merge request that upgrades the component.

## Test plan

- [ ] Performed a successful GitLab Enterprise Edition (EE) build on all supported platforms.
- [ ] Ran `qa-subset-test` CI/CD test job for both GitLab Enterprise Edition and GitLab Community Edition.
- [ ] Performed a successful GitLab Enterprise Community Edition (CE) build on dev.gitlab.org.
- [ ] Installed and verified that the component version has been upgraded.

  ```shell
  $ /opt/gitlab/embedded/bin/alertmanager --version
  ```

- [ ] Verified basic functionality.

  - [ ] Set `prometheus['listen_address'] = '0.0.0.0:9090'` in `/etc/gitlab/gitlab.rb` and run `sudo gitlab-ctl reconfigure`.

  - [ ] Shut down `gitaly` service:

       ```shell
       gitlab-ctl stop gitaly
       ```

  - [ ] Wait 5 minutes and check Prometheus console `http://<gitlab host>:9090/alerts?search=` for service down alert.

  - [ ] Start `gitaly` service:

       ```shell
       gitlab-ctl start gitaly
       ```

  - [ ]  Wait 5 minutes and check Prometheus console `http://<gitlab host>:9090/alerts?search=` for service back up.

Help & feedback

Docs

Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Join First Look to help shape new features.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.

Get Help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support

Test plan for alertmanager component upgrade