Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-9085

Document scaling down Hypershift NodePools

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • No

      Create an informative issue (See each section, incomplete templates/issues won't be triaged)

      Using the current documentation as a model, please complete the issue template. 

      Note: Doc team updates the current version and the two previous versions (n-2). For earlier versions, we will address only high-priority, customer-reported issues for releases in support.

      Prerequisite: Start with what we have

      Always look at the current documentation to describe the change that is needed. Use the source or portal link for Step 4:

       - Use the Customer Portal: https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes

       - Use the GitHub link to find the staged docs in the repository: https://github.com/stolostron/rhacm-docs 

      Describe the changes in the doc and link to your dev story

      Provide info for the following steps:

      1. - [x] Mandatory Add the required version to the Fix version/s field.

      2. - [x] Mandatory Choose the type of documentation change.

            - [ ] New topic in an existing section or new section
            - [x] Update to an existing topic: Perhaps here? https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.9/html/clusters/cluster_mce_overview#scaling-the-nodepool

       

      3. - [x] Mandatory for GA content:
                  
             - [x] Add steps and/or other important conceptual information here: 

      See procedure here https://github.com/openshift/hypershift/pull/2944/files#diff-810b5963bbf74f39cd6c937a907fecd7944621bf71453bea21c2ff416a0f358d            
             - [x] Add Required access level for the user to complete the task here: Administrator
             

             - [x] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)

      Ensure changes took place: nodeDrainTimeout > 0s 

      oc get nodepool -n <namespace> <nodepool name> -ojsonpath='{.spec.nodeDrainTimeout}' 

           
           
             - [x] Add link to dev story here: Based off original issue https://issues.redhat.com/browse/MGMT-15368

       

      4. - [x] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:

      Based off original issue https://issues.redhat.com/browse/MGMT-15368

            sdudhgao@redhat.com Servesha Dudhgaonkar
            cchun@redhat.com Crystal Chun
            David Huynh David Huynh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: