Story (Required)

• The story adds a feature to enable the argo rollout UI extension in argocd-operator
• As a user trying to use argo rollout in the operator, I want the argo rollout UI to be present on the argoCD dashboard  .

Background and Approach (Required)

• Argo Rollouts is tech preview in OpenShift GitOps and does not include any UI in the OpenShift Console. While longer term a dynamic plugin for the console is needed, a short term measure for providing a UI would be to enable the Rollouts extension in the Argo CD UI that GitOps already delivers.
• Also users of the Argo CD UI will expect to see Rollouts available in the UI since this is the standard way to manage Rollouts for multi-tenant use cases in the upstream community
• To achieve this the CR will include a new field - enableRolloutUI. This toggle will add or remove these fields from the server deployment
• `server:

  initContainers:

    - name: rollout-extension

      image: quay.io/argoprojlabs/argocd-extension-installer:v0.0.1

      env:

      - name: EXTENSION_URL

        value: https://github.com/argoproj-labs/rollout-extension/releases/download/v0.3.4/extension.tar

      volumeMounts:

        - name: extensions

          mountPath: /tmp/extensions/

      securityContext:

        runAsUser: 1000

        allowPrivilegeEscalation: false

  volumeMounts:

    - name: extensions

      mountPath: /tmp/extensions/

  volumes:

    - name: extensions

      emptyDir: {}
'

Out of Scope

• Option to set the image and extension_url by the user

Dependencies

• <Describes what this story depends on. Dependent stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

• Users are able to enable and disable the argocd rollout UI in the argocd-operator bu the toggle given in the CR
• The required e2e and unit tests for this feature

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository/project.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.