Helm
Hard
Architecture
Where does Helm 3 store release information by default?
Select your answer:
Show answer and explanation
Answer: In Secrets of type helm.sh/release.v1 in the release's namespace
Explanation
Each release revision is a Secret named sh.helm.release.v1.<release>.v<revision> that holds the chart, values and rendered manifest in compressed, encoded form. Helm 2 kept releases in ConfigMaps managed by Tiller in kube-system. The HELM_DRIVER environment variable switches storage to ConfigMaps, memory or SQL.
More hard Helm questions
- A chart has a pre-upgrade Job hook with no helm.sh/hook-delete-policy annotation. What happens to the Job left from the previous upgrade when the hook runs again?
- What does the annotation helm.sh/resource-policy: keep do on a resource in a chart?
- Which values from the parent chart can a subchart named 'redis' read?
- values.yaml contains host: "{{ .Release.Name }}.example.com". What do you write in a template so the output contains the release name instead of the literal braces?
- What is the purpose of the 'helm verify' command?
- What is the purpose of the 'helm get hooks' command?