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

Jump to bottom

docs: Clarify that targetNamespace namespace can be part of resources #896

Merged
merged 1 commit into from
Jun 23, 2023
Merged

docs: Clarify that targetNamespace namespace can be part of resources #896

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
3 changes: 2 additions & 1 deletion docs/spec/v1/kustomization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,8 @@ overrides the [Kustomize `namespace`](https://kubectl.docs.kubernetes.io/referen

While `.spec.targetNamespace` is optional, if this field is non-empty then the
Kubernetes namespace being pointed to must exist prior to the Kustomization
being applied, kustomize-controller will not create the namespace.
being applied or be defined by a manifest included in the Kustomization.
kustomize-controller will not create the namespace automatically.

### Suspend

Expand Down