Open svscorp opened 1 month ago
Similar to #5674, this would require adding the missing path into api/internal/konfig/builtinpluginconsts/namereference.go
, along with a test case in api/krusty/namereference_test.go
.
Sample PR: https://github.com/kubernetes-sigs/kustomize/pull/5698
/triage accepted /help
@stormqueen1990: This request has been marked as needing help from a contributor.
Please ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help
command.
What happened?
I'm using Kustomize v5.2.1, and trying to add environment related suffix (i.e. -prod, -dev) using nameSuffix in overlays. When I deploy the configuration, I see resources such as pvc, service are properly deployed with the right naming (i.e. grafana-prod), but my deployment can't start, because it can't find the pvc with name "grafana".
My configuration: base/grafana-persistentvolumeclaim.yaml
base/kustomization.yaml
overlays/prod/kustomization.yaml
P.S> Also tried this approach, but this didn't work either https://github.com/kubernetes-sigs/kustomize/blob/master/examples/transformerconfigs/README.md P.S2> Using transformers, placed into the overlays like this - worked. But for me it looks like a workaround...
What did you expect to happen?
I was expecting, that nameSuffix will be properly applied and the claimName of the PVC in deployment template would also become suffixed with "-prod".
How can we reproduce it (as minimally and precisely as possible)?
The configuration can be used, as I wrote in the previous section.
Expected output
No response
Actual output
No response
Kustomize version
5.2.1
Operating system
None