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

Adding Rollout Restart function to the OpenShift Console

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • openshift-4.12
    • None
    • None
    • None
    • False
    • False
    • 0
    • 0% 0%

    Description

      1. Proposed title of this feature request
      Adding Rollout Restart function to the OpenShift Console

      2. What is the nature and description of the request?
      Currently, from the OpenShift console, for the resource "deploymentconfigs" we can only start and pause the rollout, and for the resource "deployment" we can only resume the rollout. None of the resources (deployment & deployment config) has this option to restart the rollout. So, that is the reason why the customer wants this functionality to perform the same action from the CLI as well as the OpenShift console.

      3. Why does the customer need this? (List the business requirements here)
      The customer wants developers who are not fluent with the oc tool and terminal utilities, can use the console instead of the terminal to restart deployment, just like we use to do it through CLI using the command "oc rollout restart deploy/<deployment-name>".

      Usually when developers change the config map that deployment uses they have to restart pods. Currently, the developers have to use the oc rollout restart deployment command. The customer wants the functionality to get this button/menu to perform the same action from the console as well.

      4. List any affected packages or components.
      OpenShift console will be updated to allow rollout restart deployment from the console itself.

      Attachments

        Issue Links

          Activity

            People

              amobrem Ali Mobrem
              rhn-support-mmarkand Mridul Markandey
              Votes:
              2 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: