Description of problem: In a ROKS cluster, the ClusterAutoScalerOperatorDown alert is firing because the ClusterAutoScaler operator is not installed. No alert should fire. Machine Autoscalers appears as an entry under Compute in the UI. Machine Autoscalers should not appear in the UI because machines are managed outside of the cluster.
Verified on 4.5.0-0.nightly-2020-03-23-222213 On OCP cluster, the alert ClusterAutoscalerOperatorDown could successfully fire when the cluster-autoscaler operator is down. On console ui, the machine autoscaler is well displayed. This is good to move to verified as long as it's verified in 4.5 IBMROKS.
Verified on 4.5.0-0.nightly-2020-03-23-222213
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409