Summary
The README template emitted into every multi-level helmfile bundle still tells operators to look for crds.yaml and releases.yaml — files that don't exist after the DAG-stratification work in #926. The actual sub-helmfiles are level-0.yaml … level-N.yaml.
Location
pkg/bundler/deployer/helmfile/templates/README.md.tmpl lines 26-31, inside the {{ if .HasCRDLayer }} block:
For bundles that include CRD-owning charts,
`helmfile.yaml` is a thin orchestration document with a `helmfiles:` list:
`crds.yaml` is processed first to register CRDs, then `releases.yaml`
installs every chart that consumes them. `helmfile` runs the sub-helmfiles
sequentially, so `helmfile diff` against a fresh cluster no longer fails
to resolve CRD kinds before any release is installed (see issue #914).
The same stale text is baked into the golden at pkg/bundler/deployer/helmfile/testdata/upstream_helm_only/README.md lines 25-30.
The opening framing ("For bundles that include CRD-owning charts…") is also no longer accurate — the gate is now "DAG produced >1 level", which any recipe with two unrelated components linked by a dependencyRef would also trigger.
Impact
Operators reading the auto-generated README in their bundle will hunt for files the bundler doesn't emit. The deployment itself works (helmfile.yaml is correct), but the docs mislead.
Acceptance Criteria
Related
Summary
The README template emitted into every multi-level helmfile bundle still tells operators to look for
crds.yamlandreleases.yaml— files that don't exist after the DAG-stratification work in #926. The actual sub-helmfiles arelevel-0.yaml…level-N.yaml.Location
pkg/bundler/deployer/helmfile/templates/README.md.tmpllines 26-31, inside the{{ if .HasCRDLayer }}block:The same stale text is baked into the golden at
pkg/bundler/deployer/helmfile/testdata/upstream_helm_only/README.mdlines 25-30.The opening framing ("For bundles that include CRD-owning charts…") is also no longer accurate — the gate is now "DAG produced >1 level", which any recipe with two unrelated components linked by a
dependencyRefwould also trigger.Impact
Operators reading the auto-generated README in their bundle will hunt for files the bundler doesn't emit. The deployment itself works (helmfile.yaml is correct), but the docs mislead.
Acceptance Criteria
{{ if .HasCRDLayer }}block intemplates/README.md.tmplto describe the stratified layout: one sub-helmfile per dependency level (level-0.yamlfirst,level-1.yamlnext, …), processed sequentially byhelmfile.readmeData.HasCRDLayerand the relatedsplitLayoutlocal inhelmfile.goto something likeHasSubHelmfiles/stratified— the current name claims something the field no longer means.pkg/bundler/deployer/helmfile/testdata/upstream_helm_only/README.mdviago test -update ./pkg/bundler/deployer/helmfile/....Related