Skip to content

docs(nim): add nim-wfm chart parameter reference to the Helm guide - #59

Merged
ekrivovnv merged 1 commit into
egor/nim-docs-parityfrom
egor/nim-docs-helm-parameters
Oct 15, 2026
Merged

ekrivovnv merged 1 commit into
egor/nim-docs-parityfrom
egor/nim-docs-helm-parameters

Conversation

@ekrivovnv

Copy link
Copy Markdown
Owner

Summary

Adds a Chart parameters reference at the end of helm.md (Deployment, Autoscaling, Ingress, Probe, Helm test, Metrics, Models, Storage, Service), taken from the nim-wfm 1.3.0 chart README parameter tables (generated from the chart's @param annotations) and checked against its values.yaml. Parameters the chart marks legacy or deprecated are omitted. This closes the coverage gap with the parameter reference on the current NIM docs site, whose tables no longer match chart 1.3.0.

Review notes

  • Defaults are the chart's own, e.g. image.repository defaults to a non-Cosmos image and model.nimCache to /model-store; the page's example values override both.
  • Found while checking the existing page against the chart (not changed here):
    1. The Existing claim storage row needs persistence.enabled: true; otherwise the chart falls back to emptyDir.
    2. The chart has model.selection.type/variant/precision/performanceProfile for the Cosmos selectors; the page sets them through env, and the chart rejects setting the same selector in both places.
    3. Setting tolerations replaces the chart's default nvidia.com/gpu toleration.

Docs-only change; pages were not rendered locally.

🤖 Generated with Claude Code

Add a Chart parameters section at the end of the Helm guide. The
reference is generated from the nim-wfm 1.3.0 chart values (the chart
README Parameters tables and the @PARAM annotations in values.yaml),
grouped by the chart's own sections. Parameters the chart marks as
legacy or deprecated are omitted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ekrivovnv
ekrivovnv merged commit 510604f into egor/nim-docs-parity Oct 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant