Decouple secret from other replacements in workers-capm3
Keeping secrets separately gives an ability to use other replacements with alternative secret catalogues when current secret replacements are not desired.. Change-Id: I981f14249874bab1547f91a64144ac909c0cc69e Signed-off-by: Andrii Ostapenko <andrii.ostapenko@att.com>
This commit is contained in:
parent
f90c9efda8
commit
1e8f31a160
@ -0,0 +1,4 @@
|
||||
apiVersion: kustomize.config.k8s.io/v1beta1
|
||||
kind: Kustomization
|
||||
resources:
|
||||
- generated-secrets.yaml
|
@ -2,6 +2,5 @@ apiVersion: kustomize.config.k8s.io/v1beta1
|
||||
kind: Kustomization
|
||||
resources:
|
||||
- workers-env-vars.yaml
|
||||
- generated-secrets.yaml
|
||||
- networking.yaml
|
||||
- metal3machinetemplate_vars.yaml
|
||||
|
@ -2,3 +2,4 @@ apiVersion: kustomize.config.k8s.io/v1beta1
|
||||
kind: Kustomization
|
||||
resources:
|
||||
- ../../../../function/workers-capm3/replacements
|
||||
- ../../../../function/workers-capm3/replacements-secrets
|
||||
|
Loading…
Reference in New Issue
Block a user