Application Settings

Presets, values.override.yaml, and the generated values.yaml

You're viewing a development version of manager, the latest released version is 1.6.2

Page not available in that version

The current page Application Settings doesn't exist in version 1.6.2 of the documentation for this product.

We can take you to the closest parent section instead: /docs/acd/components/manager/1.6.2/installation/

Overview

The CDN Manager is a Helm release, cdn-platform, configured by Helm values. deploy builds those values from three layers, each overriding the one before it:

Layer	File	Who writes it
1. Preset	`preset.yaml`, a link to a file on the ISO	AgileTV
2. Your overrides	`values.override.yaml`	You
3. Derived settings	worked out from `group_vars/all.yaml` and the `certs/` folder	`deploy`

deploy merges them into /etc/acd/deploy/values.yaml on every run and installs the release with that one file.

Most sites need nothing beyond the preset and their site settings.

Presets

The preset is the complete starting configuration, chosen once with deploy init and remembered for every later run:

Preset	Command	ISO file	Use it for
Production	`deploy init prod` (the default)	`values-production.yaml`	Production clusters of three or more machines. Replicated services are spread across machines, with production resource sizing.
Lab	`deploy init lab`	`values-lab.yaml`	A single-machine lab, demonstration or acceptance test. Single replicas and small resource requests.

The preset is read from the ISO through the preset.yaml link, never copied. A new release’s ISO therefore brings its own defaults with it. This is also why the ISO must be mounted whenever you run deploy.

Overriding Settings

Write only the settings you want to change in /etc/acd/deploy/values.override.yaml, keeping the same nesting as in the preset. It starts empty. For example, to make the manager log in more detail while you investigate a problem:

cdn-manager:
  manager:
    logLevel: debug

Then run deploy. To undo it, remove the setting and run deploy again.

Warning: Set volume sizes before the first deploy. Helm cannot change the size of a persistent volume claim that already exists, so changing a size or persistence setting in values.override.yaml on an installed cluster does not resize the volume, and can make the upgrade fail. This applies to every component with storage, such as Kafka, VictoriaMetrics, PostgreSQL and Redis. Raising a retention setting also uses more disk, so check the volume has room first.

To find a setting, look it up in the preset on the ISO (/mnt/esb3027/values-production.yaml or /mnt/esb3027/values-lab.yaml), in the full reference /mnt/esb3027/values.yaml, or in the Configuration Guide.

Note: Some settings are derived and override anything in values.override.yaml: every manager hostname, Zitadel’s external domain, the TLS secret, and the list of CDN Directors whenever external_directors is not empty. Set those through manager_hostnames, external_directors and the certs/ folder instead.

The Generated values.yaml

/etc/acd/deploy/values.yaml holds the exact values the cluster received. Read it to see the result of the three layers.

Do not edit it: deploy rewrites it on every run, and stops with [ACD-VALUES-EDITED] if it was changed by hand. Move the change into values.override.yaml or group_vars/all.yaml, then delete values.yaml and run deploy again.