<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=18438) </details> <!--IssueSummary end--> ### Description Project variables are great (and getting better), but they're not automatically passed through to code running in production under Kubernetes with Auto Deploy, for example. We should come up with some conventions for passing variables to Kubernetes secrets and Helm chart configuration. We likely don't want to pass *all* project variables automatically to k8s and helm, and we certainly don't want to pass all *environment* variables as these contain other content. One suggestion is to take anything with the prefix of `k8s_` and store those variables (with the prefix stripped) as Kubernetes secrets. Likewise, anything with `chart_` could be passed to the `helm upgrade` command. With environment-specific variables (gitlab-ce#27722), this will be more valuable. In the absence of that, we could even map `k8s_production_*` automatically to the production environment, for example. ### Proposal ### Links / references * gitlab-ce#27722 * Inspiration: https://medium.com/opszero/deploying-kubernetes-secrets-with-circleci-23c5496a1027 ### Documentation blurb (Write the start of the documentation of this feature here, include: 1. Why should someone use it; what's the underlying problem. 2. What is the solution. 3. How does someone use this During implementation, this can then be copied and used as a starter for the documentation.) <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION --> *This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.* <!-- triage-serverless v3 PLEASE DO NOT REMOVE THIS SECTION -->