Epic Goal

• Allow users to manage Alertmanager for user-defined alerts and have the feature being fully supported.

Why is this important?

• Users want to configure alert notifications without admin intervention.
• The feature is currently Tech Preview, it should be generally available to benefit a bigger audience.

Scenarios

1. As a cluster admin, I can deploy an Alertmanager service dedicated for user-defined alerts (e.g. separated from the existing  Alertmanager already used for platform alerts).
2. As an application developer, I can silence alerts from the OCP console.
3. As an application developer, I'm not allowed to configure invalid AlertmanagerConfig objects.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• The AlertmanagerConfig CRD is v1beta1
• The validating webhook service checking AlertmanagerConfig resources is highly-available.

Dependencies (internal and external)

1. Prometheus operator upstream should migrate the AlertmanagerConfig CRD from v1alpha1 to v1beta1
2. Console enhancements likely to be involved (see below).

Previous Work (Optional):

1. Part of the feature is available as Tech Preview (MON-880).

Open questions:

1. Coordination with the console team to support the Alertmanager service dedicated for user-defined alerts.
2. Migration steps for users that are already using the v1alpha1 CRD.

Done Checklist

 * CI - CI is running, tests are automated and merged.
 * Release Enablement <link to Feature Enablement Presentation>
 * DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
 * DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
 * DEV - Downstream build attached to advisory: <link to errata>
 * QE - Test plans in Polarion: <link or reference to Polarion>
 * QE - Automated tests merged: <link or reference to automated tests>
 * DOC - Downstream documentation merged: <link to meaningful PR>