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: minor createNamespace placement fix #246

Merged
merged 1 commit into from
Apr 21, 2021
+1 −1
Merged

docs: minor createNamespace placement fix #246

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
minor createNamespace docs fix 
Signed-off-by: Dan Slinky <dan-slinky@cookpad.jp>
  • Loading branch information
@dan-slinky-ckpd @hiddeco
dan-slinky-ckpd authored and hiddeco committed Apr 21, 2021
commit 362177dc9bba89260e2e29c86bba9d9f012aad23
2 changes: 1 addition & 1 deletion docs/spec/v2beta1/helmreleases.md
View file
Original file line number Diff line number Diff line change
@@ -1015,7 +1015,7 @@ The Helm storage is stored on the remote cluster in a namespace that equals to t
the HelmRelease, or the configured `spec.storageNamespace`. The release itself is made in a
namespace that equals to the namespace of the HelmRelease, or the configured `spec.targetNamespace`.
The namespaces are expected to exist, with the exception that `spec.targetNamespace` can be
created on demand by Helm when `spec.createNamespace` is set to `true`.
created on demand by Helm when `spec.install.createNamespace` is set to `true`.

Other references to Kubernetes resources in the HelmRelease, like ValuesReference resources,
are expected to exist on the reconciling cluster.