Error: namespace transformation produces ID conflict
Opened this issue · 2 comments
Hello - I really appreciate this example. I am running into a namespace id conflict error out of Kustomize right away.
Can you tell me what version of kustomize, and k8s / kubectl you had this working under?
$ kubectl version Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.5", GitCommit:"5c99e2ac2ff9a3c549d9ca665e7bc05a3e18f07e", GitTreeState:"clean", BuildDate:"2021-12-16T08:38:33Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.4", GitCommit:"e6c093d87ea4cbb530a7b2ae91e54c0842d8308a", GitTreeState:"clean", BuildDate:"2022-03-06T21:32:53Z", GoVersion:"go1.17.7", Compiler:"gc", Platform:"linux/amd64"}
$ kustomize version {Version:kustomize/v4.5.4 GitCommit:cf3a452ddd6f83945d39d582243b8592ec627ae3 BuildDate:2022-03-28T23:06:20Z GoOs:darwin GoArch:amd64}
Hey, so the issue is that at some point kustomize changed its behavior and now you cannot create multiple namespaces just like that, see here: kubernetes-sigs/kustomize#3156
but if you comment this line you should be good to go:
https://github.com/kainlite/ts-operator/blob/master/resources/kustomization.yaml#L8
I will need to figure out the best way to do that but for now you should be able to get it working, worst case scenario you will have to create the workers namespace by hand
Thank you for your response, I appreciate it. I'll get to trying this at the end of the week and will circle back if I figure out anything that might be helpful.