Platform administrationManage data plane clusters

Override data plane cluster configurations

Cluster overrides let you customize and update cluster configurations.

Astro Private Cloud (APC) has two types of Deployment configurations that you can set at the data plane cluster level.

  • Default configuration: The base, system-provided configuration. You can override default values, but you cannot delete default keys.
  • Custom configuration: Your own additional keys and values. You can add, modify, or delete these keys.

Update your cluster

You can define cluster configurations when you first register a cluster or later by updating the cluster via the UI or Houston API.

  • Registration: The form includes an optional Cluster Override field. You can supply initial overrides when registering.
  • Edit: The cluster page contains your overall cluster information and a Deployment Configuration section.
    • Cluster Information: View and edit the cluster name.
    • Current Configuration: Read-only view of the default configurations.
    • Configuration Override: Editable area where you provide override values for base keys and/or add custom keys.
    • After you add overrides, the Current Configuration shows a read-only, git-style diff of added/modified values.
  • Houston API: If you automate cluster management, use the Houston API to update cluster metadata and connection secrets. Refer to your internal API client or see platform API docs.

Prerequisites

  • An APC control plane is installed and reachable.
  • You have System Admin permissions in the APC UI or access to the Houston API.
  • The data plane cluster is healthy and accessible from the control plane.

Update cluster information

Only the Cluster name is editable as a cluster property in the Cluster Information section. You must use Configuration Override to make changes to Deployment configurations by overriding the base Deployment configuration.

Override base configuration

Add your own keys and values to tailor behavior per cluster. You can’t delete default keys, but you can override their values to make custom configurations.

1

Select cluster

In the Clusters page, select the cluster where you want to override a configuration.

2

Find configuration to review

Search for the configuration that you want to edit in the Current Configuration.

Use ctrl+F or cmd+F on Mac to search for the config.
3

Edit Configuration Override

Click Edit to unlock Configuration Override. You can now make override edits.

4

Add new key and value

Add your new key and value to the Configuration Override.

  • To delete an override or a custom property, set its value to null in the Configuration Override. Do not remove the key; setting it to null removes the property. If you try to configure a default key with null in your Configuration Override, Astro Private Cloud does not allow you to save your changes, and prompts you to update your overrides with an accepted value.
  • Base Configuration keys cannot be deleted. You can only override their values because base configurations are the operational defaults.

Carefully check your configuration updates before you update your cluster, as these configuration changes can impact all cluster users.

5

Apply changes

Click Update cluster to apply your changes

Deployment config updates are not applied until each Deployment is individually updated.

6

Verify changes

  • Confirm cluster status is Healthy on the Clusters page in the Astro UI.
  • For Airflow Deployments in your updated cluster, trigger a small change and confirm Commander applies it as expected.
  • In Prometheus on the control plane, verify the cluster appears in federated targets.

Additional notes

  • Only the values defined under astronomer.houston.config.deployment can be overridden through Cluster configuration files. All other configurations must be updated in your values.yaml and applied using a Helm upgrade.
  • For example, to enable dagOnlyDeployment, update your values file and then perform a Helm upgrade. After that, make any necessary updates in the Cluster UI:
1global:
2  dagOnlyDeployment:
3    enabled: true
$helm upgrade <release-name> . -f values.yaml

Best practices

  • Keep overrides minimal. Prefer Base Config unless a cluster truly deviates.
  • Use consistent naming and comments for custom keys.
  • Review the diff in Current Configuration to validate the final effective settings before you Update Cluster.