Closed CathalOConnorRH closed 3 years ago
@CathalOConnorRH @obrienrobert can this be merged?
@CathalOConnorRH @obrienrobert can this be merged?
@pmccarthy I discussed this with @pb82 earlier today. Before it can be merged the Grafana Operator needs to be updated to 3.6.0 and the priority class name needs to be added to the CR.
@CathalOConnorRH @briangallagher the AMO does currently not work when installing it outside of RHMI. The reason is that the CRDs use Status
as a subresource, but the controllers do not use .Status().Update()
: https://github.com/integr8ly/application-monitoring-operator/blob/master/deploy/crds/applicationmonitoring.integreatly.org_applicationmonitorings_crd.yaml#L13 vs https://github.com/integr8ly/application-monitoring-operator/blob/420e778a34a42ac3aa7ec5182da30e86bd07fa97/pkg/controller/applicationmonitoring/applicationmonitoring_controller.go#L762
I think we should fix this, maybe not in this PR but in general as there are Teams that still use the AMO to deploy a monitoring stack.
Verified the priorityClassName
is added successfully to both the Prometheus and Alertmanager statefulSets
:
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: pb82
The full list of commands accepted by this bot can be found here.
The pull request process is described here
implement priorityClass by adding priorityClassName managed-service-priority to the statefulSet pod spec