Discussed in #2459
Originally posted by atatevyan March 5, 2026
What would you like to be added?
As a new user adopting Helmfile, the current documentation lacks a clear explanation of the core data-flow architecture.
To a beginner, the tool's behavior feels "hidden" rather than intuitive.
It misses a lot of important aspects. For example:
No word about how Helmfile merges values: in releases: , and in general.
No word about root level values: block, and how to use it.
Why is this needed?
Without these details, users are forced to rely on trial-and-error or scouring third-party blog posts. Documenting the "internal logic" of how Helmfile assembles a final manifest will significantly lower the barrier to entry.
Please, consider revising most of the documentation as it is barely usable for a beginner like me.
Discussed in #2459
Originally posted by atatevyan March 5, 2026
What would you like to be added?
As a new user adopting Helmfile, the current documentation lacks a clear explanation of the core data-flow architecture.
To a beginner, the tool's behavior feels "hidden" rather than intuitive.
It misses a lot of important aspects. For example:
No word about how Helmfile merges values: in releases: , and in general.
No word about root level values: block, and how to use it.
Why is this needed?
Without these details, users are forced to rely on trial-and-error or scouring third-party blog posts. Documenting the "internal logic" of how Helmfile assembles a final manifest will significantly lower the barrier to entry.
Please, consider revising most of the documentation as it is barely usable for a beginner like me.