Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-3107

Add volume mount for ApplicationSet Controller Pod

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • 1.10.0
    • None
    • None
    • 5
    • False
    • None
    • False
    • Hide
      Before this feature, the users used to face "x509: certificate signed by unknown authority" when using scmProvider with GitLab. This feature adds the support for `Insecure` flag for scmProvider with Gitlab and also adds an option of mounting TLS certificate on the applicationSet controller and use that certificate for scmProvider with Gitlab.
      Show
      Before this feature, the users used to face "x509: certificate signed by unknown authority" when using scmProvider with GitLab. This feature adds the support for `Insecure` flag for scmProvider with Gitlab and also adds an option of mounting TLS certificate on the applicationSet controller and use that certificate for scmProvider with Gitlab.
    • GITOPS Sprint 3244, GITOPS Sprint 3245

      Story (Required)

      As a User, trying to create ApplicationSet with Gitlab SCM Provider and self-signed TLS CA cert,  I want to be able to mount my self-signed cert to the ApplicationSet-Controller pod and use that to connect to the repository.

      Background (Required)

      The feature for using TLS cert was implemented in ArgoCD 2.8 in the PR https://github.com/argoproj/argo-cd/pull/14348 . To support this feature, the operator needs to mount the cert file on the ApplicationSet-Controller pod on the path specified.

      Approach (Required)

      Take a CM from the user as an input for AppSet Pod and mount the CM on the Applicationset-Controller pod upon startup.

      Acceptance Criteria (Mandatory)

      • The PR is merged in ArgoCD Operator
      • The PR includes unit test and e2e tests for the same

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

            isequeir@redhat.com Ishita Sequeira
            isequeir@redhat.com Ishita Sequeira
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: