Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8343

[OC CLI] oc adm upgrade status should provide output in different formats and useful subcommands

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • updates
    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      oc adm upgrade status command should provide output in different formats and useful subcommands

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

      The command together with `oc adm upgrade recommend` provide useful information before and during the upgrade activity. Customer has built automation to perform this critical task, now Customer is trying to improve the whole process so we are requesting this RFE.  

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

      I provide the customer feedback

      The command delivers very important and useful information for any cluster admin however this information is currently only consumable for humans. We have automated our cluster upgrades to the point that we usually perform them unattended by triggering them with a CronJob in the out-of-service hours. And while we base this automation on a similar information set as delivered by the “oc adm upgrade status” command, we still can’t use it because this information is not consumable for a computer without manually parsing its (undefined) format. I think it could be extremely useful if this command was expanded to offer the following capabilities:
      
      - Responses in json or yaml formats
      
      - Sub-Commands with which individual pieces of information can be extracted separately. For example, whether certain node-types have already been updated completely and whether the whole Cluster-Update (including worker node rollout) is finished etc. 

      4. List any affected packages or components.

      oc CLI

              rh-ee-smodeel Subin M
              rhn-support-gizzi Giovanni Luca Izzi
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                None
                None