Description of problem:

If you manually modify the deployments in the monitoring namespace (blackbox-exporter, grafana, prometheus) to zero pods, rhods-operator doesn't change it back to the defaults

I'm not sure if this is a bug or just an unsupported configuration, but in the redhat-ods-applications namespace the deployment sizes are restored automatically by the operator after a manual change.

Note: If the monitoring pods are killed or deleted, they are restored automatically. It's after a manual change of the deployment sizes that they are not restored (so it might not be an issue)

Steps to Reproduce

1. Install RHODS 1.17
2. In OpenShift Console, go to Workloads > Deployments and select the redhat-ods-monitoring project
3. Scale down blackbox-exporter to  to 0 pods
4. Wait a few minutes
5. Verify if blackbox-exporter deployment size have been restored automatically to the default size
6. Repeat the previous steps for grafana and prometheus deployments

Actual results:

blackbox-exporter/grafana/prometheus still have 0 pods after a few minutes

Expected results:

blackbox-exporter/grafana/prometheus to have the default number of pods

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

RHODS 1.17 RC

Workaround:

Manually scale up deployment

Additional info: