Story (Required)

NOTE: This feature came as a contribution from community. Creating this Jira to track it internally for downstream validation during release. ** 

Provide ability to add volumes and volume mounts to applicationset-controller deployment. The use-case described in github issue is to provide certs to appset controller for SCM, PR, & git generators but there could also be other use-case where this feature is useful. 

More details:

• https://github.com/redhat-developer/gitops-operator/issues/620 

Background and Approach (Required)

Provide option in ArgoCD CR to add vols and volume mounts to applicationset controller

Example:

apiVersion: argoproj.io/v1beta1
kind: ArgoCD
metadata:
  name: argocd-sample
spec:
 applicationSet:
    volumes:
      - name: empty-dir-volume
        emptyDir: {}
    volumeMounts:
      - name: empty-dir-volume
        mountPath: /etc/test

Out of Scope

• <Defines what is not included in this story.>

Dependencies

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

Acceptance Criteria (Mandatory)

• <Describe edge cases to consider when implementing the story and defining tests.>
• <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story.>

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• 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.