Kustomize: What is the replacement for `bases`?
I see bases is deprecated. What is the replacement?
tamalsaha
All 6 comments
If I understand correctly, resources can be used to point to a directory containing a kustomization.yaml for these purposes.
chancez
on 4 Mar 2020
@chancez correct -- you can specify bases as resources
pwittrock
on 10 Mar 2020
https://github.com/kubernetes-sigs/kustomize/issues/776#issuecomment-461459130 demonstrates they have some notable differences. Bases seems to be the better option for what I'm trying to do and several other uses I've seen.
Update: I guess this is only an issue in the version of kustomize shipped with kubectl 1.18.
MikaelSmith
on 19 May 2020
But if you define bases with resources it requires the base to be "in or below" which is a bad idea if you wont dublicate base per env. How am I supposed to put base within dev or prod?
MyRepo
├───base
│ ├───db
│ ├───frontend
│ ├───service1
│ ├───service2
└───env
│ ├───dev
│ ├───prod
tolgaingenc
on 30 Jun 2020
Can someone please confirm if this is/will be fixed by 1.19?
coderatchet
on 9 Sep 2020
@coderatchet Added an explanation on this ticket (as far as i can work it out) https://github.com/kubernetes/kubectl/issues/891#issuecomment-731238572
timhughes
on 20 Nov 2020
Related issues
monopole
·
3Comments
karlmutch
·
5Comments
lionelvillard
·
4Comments
sidps
·
5Comments
nicks
·
3Comments
Most helpful comment
But if you define bases with resources it requires the base to be "in or below" which is a bad idea if you wont dublicate base per env. How am I supposed to put base within dev or prod?
MyRepo
├───base
│ ├───db
│ ├───frontend
│ ├───service1
│ ├───service2
└───env
│ ├───dev
│ ├───prod