-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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.
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
Can kustomizations configMapGenerator use the file in parent folder, thanks. #5749
Comments
This issue is currently awaiting triage. SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Then I want to try another solution like:
I wish it can come out correct value, like
However, it still show variable as below, not show
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
Ok, for security point of view, this does not work by design. |
However, we have one work around, with flux2 gitrepository.
Thus, you can use ../ in kustomize folder.
|
Eschewed features
What would you like to have added?
Why is this needed?
can we use the files in parent folder, or any workarround for this? thanks.
Can you accomplish the motivating task without this feature, and if so, how?
we have to move all files in same folder of kustomization.yaml
However, in real case, this is not true.
What other solutions have you considered?
copy duplicate files in kustomization.yaml, the code structure is ugly.
Anything else we should know?
No response
Feature ownership
The text was updated successfully, but these errors were encountered: