-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Another potential issue around kind:Namespace #5192
Comments
/assign @annasong20 |
Hi @pb-adrianbezzina, thank you for the issue report. The problem is that the name suffix transformer is hard-coded to skip all resources with The fix for this issue would be to change the current namespace GVK to reflect only the k8s built-in In the short term, we could hard-code this logic into the prefix, suffix transformers, much like in #5133. In the long run, though, I think it may be worth changing @natasha41575 would love to get your thoughts on the feasibility of this. /triage accepted |
After discussion, we've agreed that we'd consider changes to /unassign |
What happened?
I have the following manifest:
and with a transformer configured like so:
The transformation doesn't apply after a kustomize build - and the original manifest is the end result of the build
Seems to be similar to issue #5072 where having a resource of KIND namespace is confusing the kustomize command - if this is found to be a issue - would be wise to check all places there is logic around Kind: Namespace
What did you expect to happen?
Manifest:
and with a transformer configured like so:
New Manifest:
How can we reproduce it (as minimally and precisely as possible)?
Expected output
Actual output
Kustomize version
5.0.3
Operating system
Linux
The text was updated successfully, but these errors were encountered: