-
Notifications
You must be signed in to change notification settings - Fork 730
Add namespace to kustomizations #302
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
Conversation
Without this change, these kustomiations fail to apply their patches with errors like: ``` Error: no matches for OriginalId apps_v1_StatefulSet|~X|kafka; no matches for CurrentId apps_v1_StatefulSet|~X|kafka; failed to find unique target for patch apps_v1_StatefulSet|kafka ```
Does |
For me |
Good point we should support GitOps flows. However then I can't reproduce the issue, with kustomize 2.0.3 which we stick with because it's the version built in to kubectl. What's your version of Kustomize? Maybe this is a change in Kustomize's behavior after all. |
What happens if you use a kustomize base that sets a |
I'm using kustomize 3.5.3 locally. Sorry, I see now that it wasn't clear that I was using the standalone kustomize vs. the version bundled with kubectl. If I create a new Kustomization, when using this patch, the namespace set in the Kustomization is applied:
When working on my fork, where the HEAD has the patch from this PR, if I check out to the previous commit to remove the patch,
|
Got it. The namespace in this PR identifies what to patch. With this diff the output from Kustomize 2.0.3 and 3.5.4 is equivalent, with or without a custom namespace name. |
Hi there. I had trouble using these variants without adding these bits.
Without this change, these kustomiations fail to apply their patches
with errors like: