Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-13135

"Create ClusterAutoscaler" button when only one ClusterAutoscaler is allowed per cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Normal Normal
    • None
    • 4.12.z
    • Management Console
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • No
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      I am deploying OpenShift Dedicated (OSD) using OpenShift v4.12.14 

      Version-Release number of selected component (if applicable):

      v4.12.14 

      How reproducible:

      The issue is always reproducible. 

      Steps to Reproduce:

      1. Deploy OSD in either AWS or GCP (doesn't matter.)
      2. Login into OpenShift Console
      3. Search for ClusterAutoscaler API from "HOME > SEARCH" in the left navigation bar.
      4. 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.  

      Actual results:

       

      Expected results:

      As per OCP v4.12 documentation, there can be only one Cluster Autoscaler per cluster. So, I am not sure what are the use cases of showing a button to create additional ClusterAutoscalers. I would love to learn about the use cases (if any) for creating multiple ClusterAutoscalers.
      
      "Because the cluster autoscaler is scoped to the entire cluster, you can make only one cluster autoscaler for the cluster."
      
      https://docs.openshift.com/container-platform/4.12/machine_management/applying-autoscaling.html
      
      

      Additional info:

      There could be a use case to create a new ClusterAutoscaler when the default one is deleted. However, in that case, clicking "Create ClusterAutoscaler" should throw an error when the default ClusterAutoscaler still exists. 

              jhadvig@redhat.com Jakub Hadvig
              rh-ee-smulkutk Shreyans Mulkutkar
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: