Show AutoDevops Helm Releases
Type of issue
Problem to solve
Auto Devops documentation does not make it clear that it uses a local tiller (!22036 (merged)) to deploy charts. This leads to a surprising state for users as they expect to find their releases available in tiller after deployment and may end up checking the "gitlab-managed-apps" tiller as it is the only tiller mentioned on that page. How the auto-devops pipeline leverages helm in general is something that could be expanded on in the documentation.
Further details
This additional documentation inherently lies on the boundary in between gitlab AutoDevops and Helm/Kubernetes, it is to be geared towards more advanced users who want to understand the full pipeline instead of leaving the magic as a black box. I realize a crash course in helm is not really the point of this documentation but it feels like the docs currently stops just short of being able to show the user everything it actually deployed which is critical for diagnosing problems.
Proposal
Ideally there would be a section showing show a user how to stand up a local tiller to inspect the releases. This would help both the specific confusion above but also reduce the magic in the Auto Devops pipeline making its output more concert for users. Furthermore there are multiple references in the Auto Devops page saying:
"Caution: Your apps should not be manipulated outside of Helm (using Kubernetes directly.) This can cause confusion with Helm not detecting the change, and subsequent deploys with Auto DevOps can undo your changes. Also, if you change something and want to undo it by deploying again, Helm may not detect that anything changed in the first place, and thus not realize that it needs to re-apply the old config."
Their is not substantive follow up on how to go about editing releases, what you should expect if you do so and if you should at all.
Who can address the issue
Somone with an understanding of the auto-devops pipeline, helm and, possibly the auto-deploy-app chart.