Open Stef16Robbe opened 2 months ago
This happens on linux as well.
We ran into the same issue. If you have nested kustomizations, it will break.
Previous structure that worked prior to this version.
kubernetes/qualityenv/kustomization.yaml kubernetes/qualityenv/build-test/kustomization.yaml
Running "kustomize localize qualityenv/build-test localized/qualityenv-build-test --scope ." breaks.
If you flatten the folder structure it will work.
basically we had to work around by changing our structure to
kubernetes/qualityenv/kustomization.yaml kubernetes/qualityenv-build-test/kustomization.yaml
and run kustomize localize qualityenv-build-test localized/qualityenv-build-test --scope .
Hi there, @Stef16Robbe! Thanks for reporting this issue.
I was unable to reproduce it on MacOS, even with a latest head build. Would you be able to provide a minimal example that replicates the problem described?
/triage needs-information
What happened?
I added this local reference in my Kustomize file (MacOS):
It is a relative path towards
/var/folders/2b/ryb_dw7j1gg183b46_ppt5sr0000gn/T/folder
, which exists, and contains a Kustomize file that builds successfully on it's own (usingkustomize build "../../../../../var/folders/2b/ryb_dw7j1gg183b46_ppt5sr0000gn/T/folder"
works fine)But when I try to refer to it in a Kustomize file (shown above), I get an error:
The problem is that, for some reason, now all the sudden, Kustomize is looking in
/Users
?/Users/var/folders/2b/ryb_dw7j1gg183b46_ppt5sr0000gn/T/folder
does indeed not exist, but it's not the path I've given to Kustomize.It probably has something to do with symlinking on Mac, but I'm confused as to why it does work when building the file directly, but not when it's referred to in another Kustomize file.
What did you expect to happen?
A successful build
How can we reproduce it (as minimally and precisely as possible)?
os.TempDir()
Expected output
N/A
Actual output
An error
Kustomize version
v5.4.3
Operating system
MacOS