Configuration via Helm
This page covers how the Helm chart translates its values into the RMS
config.toml. For the configuration keys themselves and their defaults, see
Configuring RMS.
The Helm chart does not take a raw config.toml.
Instead it renders one from apiServer.* values into a ConfigMap
(rms-api-config) and mounts it read-only at /etc/rms/config.toml. The database
connection string is the only runtime override: it is built from Secret-backed
credentials and injected as DATABASE_URL, which supersedes the (empty)
[postgres] db_url in the ConfigMap so the password never lands in a ConfigMap.
Because RMS reads the file once at startup, the Deployment carries a
checksum/config annotation so config changes trigger a rollout.
The rendered config.toml groups keys into the same sections as the Rust config
structs. This table maps each Helm value to the config.toml key it produces:
See Deployment for install/upgrade workflows and
helm/README.md for
the exhaustive values reference.