Create `auto-deploy-image` with Helm 3 support
Problem to solve
Auto DevOps users can start using Helm version 3 to automatically deploy their applications to Kubernetes clusters. With the release of Helm 3 last year, Helm 2 is nearing it end of life. The current GitLab release adds support to Helm 3 based releases. Upgrading from Helm 2 to Helm 3 is coming in a future release.
Helm 2 based releases will be deprecated in GitLab 14.0, but upgrading is highly recommended as Helm 2 might not be supported by then.
Use cases
As an Auto DevOps user, in order to be tiller-less and future-proof, I would like to use Helm3 to deploy my apps.
Intended users
User experience goal
User can use Helm 3 to deploy apps using Auto DevOps.
Proposal
Make a pre-release of auto-deploy-image with Helm 3 support without any 2to3 migration at all, to enable early adopter testing
Further details
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Is this a cross-stage feature?
Links / references
Edited by Viktor Nagy (GitLab)