Skip to content

docs(chart_template_guide): point YAML Anchors at library charts#2117

Open
edu-diaz wants to merge 5 commits into
helm:mainfrom
edu-diaz:docs/yaml-anchors-library-charts-xref
Open

docs(chart_template_guide): point YAML Anchors at library charts#2117
edu-diaz wants to merge 5 commits into
helm:mainfrom
edu-diaz:docs/yaml-anchors-library-charts-xref

Conversation

@edu-diaz
Copy link
Copy Markdown

What

Adds a short info admonition at the end of the YAML Anchors appendix in the Chart Template Guide, linking to Library Charts.

Applied to both versioned_docs/version-3/chart_template_guide/yaml_techniques.md (current GA) and docs/chart_template_guide/yaml_techniques.md (next).

Why

The YAML Anchors section already warns that anchors are lost on the round-trip through Helm/Kubernetes, but it doesn't tell readers what to reach for instead. A common motivation for using anchors in chart templates is DRY — sharing snippets across charts. Library charts are exactly the Helm-native mechanism for that case, and they don't suffer from the round-trip pitfall the existing section describes.

A small cross-reference at the end of the section nudges readers toward the right tool when DRY is the goal, without disrupting the rest of the appendix.

Preview

ℹ️ Reaching for anchors as a DRY mechanism? For sharing snippets across charts, prefer library charts — they are designed for reuse and aren't affected by the round-trip pitfall described above.

Checklist

  • DCO sign-off on the commit
  • Same content mirrored across v3 (GA) and next (v4) so the page stays in sync
  • Uses the existing :::info admonition convention already used elsewhere in the v4 docs (e.g. docs/overview.md, docs/plugins/developer/index.mdx)
  • Internal link uses the repo's [text](/topics/library_charts.md) convention (matching e.g. chart_template_guide/subcharts_and_globals.md)

When readers reach the YAML Anchors appendix, a common motivation is
DRY-ing up shared snippets across charts. Library charts are the
Helm-native way to do that and aren't affected by the round-trip pitfall
the section already describes. Add a short info admonition at the end of
the section linking to /topics/library_charts.

Mirrored in both versioned_docs/version-3 and docs (next).

Signed-off-by: Eduardo Diaz <edudiazasencio@gmail.com>
Copy link
Copy Markdown
Contributor

@paigecalvert paigecalvert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @edu-diaz . I added some copy edits for style/clarity; otherwise this lgtm!

Comment thread docs/chart_template_guide/yaml_techniques.md Outdated
Comment thread docs/chart_template_guide/yaml_techniques.md Outdated
Comment thread docs/chart_template_guide/yaml_techniques.md Outdated
Comment thread versioned_docs/version-3/chart_template_guide/yaml_techniques.md Outdated
Comment thread versioned_docs/version-3/chart_template_guide/yaml_techniques.md Outdated
Comment thread versioned_docs/version-3/chart_template_guide/yaml_techniques.md Outdated
… admonition

Tighten the wording in the new YAML Anchors → library charts admonition
per review feedback: lead with the recommendation ("use library charts
instead of YAML anchors") and split the rationale into a second sentence.

Same change mirrored in docs/ (next) and versioned_docs/version-3 (GA).

Signed-off-by: Eduardo Diaz <edudiazasencio@gmail.com>
@edu-diaz
Copy link
Copy Markdown
Author

edu-diaz commented May 29, 2026

@paigecalvert hey thanks I applied your suggested changes

@edu-diaz edu-diaz requested a review from paigecalvert June 2, 2026 17:14
@paigecalvert paigecalvert requested a review from TerryHowe June 2, 2026 17:17
Copy link
Copy Markdown
Contributor

@paigecalvert paigecalvert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@TerryHowe this lgtm from a docs perspective. Could use your 👍 before merging to make sure you agree with the library charts recommendation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants