Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Rendering the final Values locally #1127

Merged
merged 1 commit into from
Dec 11, 2024
Merged

docs: Rendering the final Values locally #1127

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions docs/spec/v2/helmreleases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1451,6 +1451,23 @@ Besides being reported in Events, the controller may also log reconciliation
errors. The Flux CLI offers commands for filtering the logs for a specific
HelmRelease, e.g. `flux logs --level=error --kind=HelmRelease --name=<release-name>.`

#### Rendering the final Values locally

When using multiple [values references](#values-references) in a
HelmRelease, it can be useful to inspect the final values computed from the various sources.
This can be done by pointing the Flux CLI to the in-cluster HelmRelease object:

```shell
flux debug hr <release-name> -n <namespace> --show-values
```

The command will output the final values by merging the in-line values from the HelmRelease
with the values from the referenced ConfigMaps and/or Secrets.

**Note:** The debug command will print sensitive information if Kubernetes Secrets
are referenced in the HelmRelease `.spec.valuesFrom` field, so exercise caution
when using this command.

## HelmRelease Status

### Events
Expand Down
Loading