Cluster parameters¶
The Settings → Cluster parameters tab.
Cluster parameters are typed text settings that drive the platform's behavior. Each parameter has:
- a type (cluster setting, Digdash license, API token…);
- a name (its key) and a value;
- a scope: global (empty namespace — applies everywhere, management restricted to platform administrators) or scoped to a namespace (managed by that namespace's admins, takes priority over the global value).
Examples of recognized settings¶
| Name | Effect |
|---|---|
USE_DIGDASH_BETA |
true to offer Digdash BETA versions in the version picker |
DIGDASH_QA_DATABASE_TYPES |
true to show database engines reserved for internal QA (MariaDB, PostgreSQL side-car) in the Digdash BI form |
DIGDASH_FILEBROWSER |
Default value of the File Browser option for Digdash deployments |
DEFAULT_DIGDASH_RAM |
Default memory suggested for a Digdash BI deployment |
GRAFANA_URL, PROMETHEUS_PUBLIC_URL, ALERTMANAGER_URL |
Public URLs of the monitoring tools (links on the Cluster page, the sidebar and the cards) — default https://grafana|prometheus|alertmanager.<domain> |
PROMETHEUS_URL |
Address of the internal Prometheus queried for volume usage and alerts (default: the service of the monitoring namespace) |
SPARK_JOB_GIT_IMAGE, SPARK_JOB_S3_IMAGE |
Images of the initContainers fetching a Spark job's source (Git repository / S3 object) — override on a cluster without Docker Hub access |
Sensitive values
A parameter's value is shown in plain text to anyone with access to its scope. Only put a secret there if the scope is appropriate.
Usage¶
The list can be filtered by namespace and by type; creation, editing and deletion happen directly in the table. A parameter created as a duplicate (same namespace, type and name) is rejected.