-
Feature
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
False
-
-
False
-
Not Selected
Feature Overview
Currently, configuring Alertmanager to forward alerts to third-party endpoints or to add platform metrics for alerting is driven via ConfigMaps, as documented here:
. This approach limits flexibility and composability in GitOps workflows.
- ConfigMap-driven configuration is static and difficult to manage across environments.
- Overrides for alert thresholds or routing rules require custom tooling or manual intervention.
- Lack of CRD support prevents leveraging Kubernetes-native tooling like `kustomize`, `kubectl`, and GitOps pipelines for observability configuration.
...
Goals
Customer proposes enabling Kubernetes-native Custom Resource Definitions (CRDs) to manage these configurations, allowing for declarative management and kustomize-based overrides for tuning alarms and thresholds.
*Proposed Solution:*
- Introduce CRDs for:
- Alertmanager routing and receiver configuration.
- Platform metric selection and threshold definitions.
- Ensure these CRDs are compatible with existing RHACM observability components.
- Support `kustomize` overlays to allow environment-specific tuning of alerts and thresholds.
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
| Introduce CRDs for Alertmanager routing and receiver configuration as well as Platform metric selection and threshold definitions. | ||
| Support `kustomize` overlays to allow environment-specific tuning of alerts and thresholds. |
(Optional) Use Cases
*Use Case Example:*
A team managing multiple clusters wants to tune alert thresholds for CPU usage differently in dev vs. prod. With CRD support, they can use `kustomize` overlays to apply environment-specific configurations without modifying base manifests or building custom override systems.
Customer Considerations
*Benefits:*
- Declarative and version-controlled observability configuration.
- Seamless integration with GitOps workflows.
- Simplified customization and override mechanisms using native Kubernetes tooling.
- Improved maintainability and scalability of alerting configurations.
*Impact:*
- Enhances RHACM’s alignment with Kubernetes-native principles.
- Reduces operational overhead for multi-cluster observability management.
- Improves user experience for platform teams managing alerts and metrics.
