Disable management of quotas and limitranges

If you install Astro Private Cloud into an environment where administrators have enforced strict resource allocations, you might be restricted to a set of namespaces and can’t adjust quotas or limitranges. If Commander runs with roles that don’t include permissions to access cluster limitrange or quotas, it can result in Airflow Deployment failures when Houston tries to pass extra_capacity requirements. To avoid this, set disableManageResourceQuotasAndLimitRanges to true to disable passing extra_capacity.

In APC 1.x, this setting is part of cluster configuration and must be saved in the Astro Private Cloud UI for the data plane cluster, not in values.yaml. A Helm upgrade doesn’t change a cluster’s saved value for this key. See Configure Astro Private Cloud and Data plane overrides for the model and the editing steps.

Set the override in the Astro Private Cloud UI

1. Sign in to the Astro Private Cloud UI as a System Admin.

2. Open Clusters and select the data plane cluster you want to update.

3. In the Deployment Configuration section, open Configuration Override.

4. Add the following override:

   1
   {
   2
     "deployments": {
   3
       "disableManageResourceQuotasAndLimitRanges": true
   4
     }
   5
   }

5. Save the change. The Current Configuration view shows a read-only diff of the added value.

To automate the change, use the updateCluster GraphQL mutation in the Houston API with the same JSON as deploymentsConfigOverride. See Data plane overrides for an example mutation.