Skip to main content
If you install Astro Private Cloud into an environment where administrators enforce strict resource allocations, you might be restricted to a set of namespaces and can’t create or change quotas or limit ranges. If the data plane internal API runs with roles that don’t include permissions on resource quotas and limit ranges, Airflow Deployments fail when the APC API applies them. To avoid this, set resourceManagement.resourceQuotas.enabled to false:
You can also set it for a single cluster, Workspace, or Deployment with config governance. The next time each affected Deployment updates, APC removes its ResourceQuota and LimitRange. For what else changes, see Turn off quota and limit range management.
When you set resourceManagement.resourceQuotas.enabled: false, all Pods running in the APC application can consume unlimited resources on the nodes that they’re scheduled on, which can lead to cluster-wide instability. Astronomer strongly recommends that you manage your own resourceQuotas and limitRanges when you turn this setting off.
In APC 1.x, this setting was disableManageResourceQuotasAndLimitRanges: true. APC 2.x doesn’t read it. If it’s still in your Helm values, APC ignores it and keeps managing quotas and limit ranges. See Upgrade to Astro Private Cloud 2.0 from 1.x.