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: Clarify the Kustomize components relative paths requirement #861

Merged
merged 1 commit into from
May 12, 2023
Merged

docs: Clarify the Kustomize components relative paths requirement #861

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
6 changes: 3 additions & 3 deletions docs/spec/v1/kustomization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -493,11 +493,11 @@ metadata:
spec:
# ...omitted for brevity
components:
- ingress
- tls
- ../ingress
- ../tls
```

**Note:** The component paths must be local and relative to the source root.
**Note:** The components paths must be local and relative to the path specified by `.spec.path`.
Copy link
Contributor

Choose a reason for hiding this comment

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

What does "local" mean here? Is that an antonym to "remote"?

Copy link
Member

Choose a reason for hiding this comment

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

Yes, we disallow remote component bases.


**Warning:** Components are an alpha feature in Kustomize and are therefore
considered experimental in Flux. No guarantees are provided as the feature may
Expand Down