Apply configuration changes
Change a configuration value on an existing CARTO Self-Hosted deployment and re-deploy, without changing the release version
Last updated
Was this helpful?
Change a configuration value on an existing CARTO Self-Hosted deployment and re-deploy, without changing the release version
Use this procedure to change a configuration value — a domain, database endpoint, storage bucket, SSO setting, AI key, and so on — on an existing deployment. This is an apply changes (reconfigure) operation: it re-deploys your installation with the new settings without moving to a new release version. To move to a newer version instead, see Updates.
For how configuration is structured and stored in each method, see How Configuration Works. For recommendations on tracking and securing it, see Manage configuration as code.
Configuration changes are made in the Admin Console.
Log in to the Admin Console.
Open the Config tab.
Edit the settings you need to change.
Click Save config.
Wait for the Preflight checks to complete.
Click the Deploy button to apply the new configuration.
Monitor progress in the Details section until all services are healthy.
The previous configuration stays available in the Version history tab, where you can review the diff between versions or redeploy an earlier one if needed.
Configuration changes are made in your customizations.yaml file. You do not need to update the chart or download a new customer package — that is only required for a version update.
1) Edit customizations.yaml with your change. For available overrides, see Advanced customizations.
2) (Recommended) Run the preflight checks to validate the change before applying it.
3) Apply the change with helm upgrade, passing all three files:
4) Commit the updated customizations.yaml to version control.
After applying, confirm the deployment is healthy:
Last updated
Was this helpful?
Was this helpful?
helm upgrade \
carto \
carto/carto \
-f carto-values.yaml \
-f carto-secrets.yaml \
-f customizations.yaml