1. Proposed title of this feature request

Add UI validation for "Create ClusterAutoscaler" button when a Cluster Autoscaler is already present. 

2. What is the nature and description of the request?

Since there can be only one Cluster Autoscaler per cluster, it makes sense to add a UI validation check to not allow creating a new Cluster Autoscaler using "Create ClusterAutoscaler" button. To see this button:

• Go to the OpenShift Console and search for ClusterAutoscaler API from "HOME > SEARCH" in the left navigation bar.
• At this point you will only see the default ClusterAutoscaler. Now click the ClusterAutoscalers in "ClusterAutoscalers > ClusterAutoscaler details". Here you will see a blue button at the top right to create a new ClusterAutoscaler.

In the current form, when there is a default Cluster Autoscaler and user clicks the "Create ClusterAutoscaler" button, the UI allows user to make modifications to the YAML and hit "Create". It is only at the end of this workflow an error is returned. 

An error occurred  
admission webhook "regular-user-validation.managed.openshift.io" denied the request: Prevented from accessing Red Hat managed resources. This is in an effort to prevent harmful actions that may cause unintended consequences or affect the stability of the cluster. If you have any questions about this, please reach out to Red Hat support at https://access.redhat.com/support 

3. Why does the customer need this? (List the business requirements here)

This is not customer requested, but something to consider from UX perspective. 

4. List any affected packages or components.

OpenShift Console UI/UX