-
Epic
-
Resolution: Done
-
Major
-
None
-
RolloutManager should create a ServiceMonitor
-
False
-
None
-
False
-
To Do
-
SECFLOWOTL-102 - Argo Rollouts managed by GitOps Operator
-
0% To Do, 0% In Progress, 100% Done
-
Before this update RolloutManager controller was not creating ServiceMonitor. This update supports creating ServiceMonitor using RolloutManager so that metrics from Rollouts will automatically be included in OpenShift monitoring.
-
-
Epic Goal
- RolloutManager controller needs to create a ServiceMonitor so that metrics from Rollouts will automatically be included in OpenShift monitoring.
- A service, argo-rollouts-metrics, is already created to provide access to metrics, it just needs to be connected to monitoring via a ServiceMonitor
Why is this important?
- Customers need to monitor components of the system including the Argo Rollouts which is deployed by the OpenShift GitOps Operator
Scenarios
- Deploy Rollouts into a namespace with RolloutManager and be able to monitor Argo Rollouts
Acceptance Criteria (Mandatory)
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- Rollout metrics appear in Observe > Metrics in OpenShift console.
Dependencies (internal and external)
- ...
Previous Work (Optional):
- ...
Open questions::
- ...
Done Checklist
- Acceptance criteria are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
- is documented by
-
RHDEVDOCS-6010 [Recurring task]: GitOps 1.13.0 release notes
-
- Closed
-
- links to
-
RHEA-2024:133299
Errata Advisory for Red Hat OpenShift GitOps v1.13.0