rename metrics-exporter spec to monitoring#1098
rename metrics-exporter spec to monitoring#1098openshift-merge-robot merged 1 commit intored-hat-storage:masterfrom
Conversation
Monitoring spec is more generic and suited to our use case as we configure more than just a metrics-exporter. We want monitoring to be fully enabled or fully disabled. i.e. metrics-exporter, PrometheusRule, ServiceMonitor etc should all be managed via common parent spec. Signed-off-by: Umanga Chapagain <chapagainumanga@gmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jarrpa The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/cherry-pick release-4.7 |
|
@agarwal-mudit: #1098 failed to apply on top of branch "release-4.7": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Monitoring spec is more generic and suited to our use case
as we configure more than just a metrics-exporter.
We want monitoring to be fully enabled or fully disabled.
i.e. metrics-exporter, PrometheusRule, ServiceMonitor etc
should all be managed via common parent spec.
It will also enable future enhancements under "monitoring"
without making any breaking changes.
Signed-off-by: Umanga Chapagain chapagainumanga@gmail.com