git clone
cd control
Create namespace if need:
kubectl create namespace control
Make changes in values.yaml file and run command:
helm upgrade -i control -n control -f ./values.yaml .
N.B!
If you update up to chart version 0.3.9, you need to stop server application - just delete deployment for server.
After old version of server stoped you can upgrade to new chart version.
Dashboards are the files in mixins/dashboards/*.json; they are rendered as ConfigMaps (label grafana_dashboard: "true") and picked up by the Grafana sidecar. Manual edits in the Grafana UI are lost on Grafana restart. To change a dashboard (e.g. SIM API, mixins/dashboards/sim-api.json, uid sim_api_dashboard), open an MR to this chart, not edit it in the UI.
All of these are off by default; with the shipped values.yaml the chart renders exactly as before.
By default apiSecret, superAdminApiKey, auth.key and the app DB password
(global.db.secret.data.dbpwd) are taken from values and rendered into the server and
ctrl-sim-api ConfigMaps (and plain env of the init containers). To keep them out of
values and ConfigMaps, create a Secret and point the chart at it:
kubectl -n control create secret generic control-platform \
--from-literal=apiSecret=<...> \
--from-literal=superAdminApiKey=<...> \
--from-literal=saSecretKey=<...> \
--from-literal=dbpwd=<...>global:
control:
existingSecret:
name: control-platform
keys: # optional, these are the defaults
apiSecret: apiSecret
superAdminApiKey: superAdminApiKey
authKey: saSecretKey
dbPassword: dbpwdWith name set:
- server and ctrl-sim-api get
CONTROL_API_SECRET,CONTROL_SUPERADMIN_API_KEY,CONTROL_SA_SECRET_KEYandCONTROL_DB_PASSWORDassecretKeyRefenv vars, and their config files contain only the${...}placeholders; - control-tasks builds
CONTROL_TOKENfrom the Secret (<superAdminApiKeyPrifix>$(CONTROL_SUPERADMIN_API_KEY)) and readsCONFIG_SA_SECRETKEYfrom it;configSaSecretKeyis no longer written tocontrol-config-secret; DB_PASSWORD, thePGPASSWORDof the init containers, pgbouncer and thepostgres-post-installhook read the DB password from the Secret.
Still needed separately: global.db.secret.create: false with a pre-created
<release>-control-<db.secret.name> / -root Secret if the DB Secret must not be rendered
from values either. ufs and mf-api (both optional, off by default) still read auth.key
from values.
global:
control:
initResources:
requests: {cpu: 10m, memory: 16Mi}
limits: {cpu: 100m, memory: 64Mi}Applied to every InitWait.* init container, the postgres-post-install hook Pod and the
ufs / internal postgres / internal scylla init containers.
global.control.<server|frontend|realtime|widget|ctrl_sim_api|control_tasks>.pdb.enabled: truerenders apolicy/v1PDB (minAvailable: 1by default; setmaxUnavailableto use it instead — recommended for the single-replica control-tasks).global.control.<widget|ctrl_sim_api|control_tasks>.autoscaling.createHPA: truetogether withautoscaling.enabled: truerenders anautoscaling/v2HPA for components that had no HPA template.createHPAis separate so installs that already setenabled: truedo not get a new HPA on upgrade. control-tasks is a singleton by design (keepmaxReplicas: 1unless its cron locking has been confirmed).