Add ability to configure ViNO flavors
ViNO configures application behavior using configMaps generated inside of various kustomization.yaml files [0]; however, we cannot modify them in Treasuremap because they live in the upstream folder. This change adds a mechanism for configuring flavors using patches. Other application configMaps can be overridden the same way. The new default values added for the multi-tenant type are configured for the stl3 site; however, operators can override these values for downstream environments. [0] https://opendev.org/airship/vino/src/branch/master/config/manager/kustomization.yaml Closes #170 Signed-off-by: Drew Walters <andrew.walters@att.com> Change-Id: I73668b15a652cf28b366154a53e62970311d61b8
This commit is contained in:
parent
b20777dd7d
commit
f35d7bd45d
|
@ -4,4 +4,9 @@ resources:
|
|||
- ../../../../function/sip
|
||||
- ../../../../function/synclabeller
|
||||
- ../../../../function/vino
|
||||
- ../../../../function/helm-chart-repository/
|
||||
- ../../../../function/helm-chart-repository/
|
||||
patchesStrategicMerge:
|
||||
# NOTE: ViNO uses Kustomize's configMapGenerator feature to configure various
|
||||
# application behaviors. Override them below using patches.
|
||||
# https://opendev.org/airship/vino/src/branch/master/config/manager/kustomization.yaml
|
||||
- patches/vino-flavors.yaml
|
||||
|
|
|
@ -0,0 +1,15 @@
|
|||
apiVersion: v1
|
||||
kind: ConfigMap
|
||||
metadata:
|
||||
name: flavors
|
||||
data:
|
||||
flavors.yaml: |
|
||||
flavors:
|
||||
controlPlane:
|
||||
vcpus: 4
|
||||
memory: 16
|
||||
rootSize: 128
|
||||
worker:
|
||||
vcpus: 16
|
||||
memory: 64
|
||||
rootSize: 256
|
Loading…
Reference in New Issue