DeploymentSettings
Configure global Plural CD settings via the DeploymentSettings CRD
DeploymentSettings is the global configuration resource for Plural Continuous Deployment. It lives on your management cluster and drives Console-wide settings that are not tied to a single service or cluster: agent helm defaults, repository references, RBAC bindings, observability integrations, AI configuration, stack runner defaults, and more.
If you bootstrapped with plural up, you likely already have this resource defined at bootstrap/settings.yaml in your management repo.
Singleton resource
Only one DeploymentSettings resource is ever reconciled. The management controller watches for a resource with an exact identity:
Field | Required value |
|---|---|
metadata.name | global |
metadata.namespace | plrl-deploy-operator |
Any other name or namespace is ignored. The controller will not apply your spec to the Console API. Instead, check status.conditions on the resource — you should see a Synchronized condition set to False with a message similar to:
ignoring because of invalid name/namespace, only the global/plrl-deploy-operator DeploymentSettings will be reconciled
When the name and namespace are correct and the spec reconciles successfully, expect Synchronized=True and Ready=True on status.conditions.
Neutral:
Do not create multiple DeploymentSettings resources expecting them all to apply. Only global in plrl-deploy-operator is processed. Use a single manifest and merge all desired configuration into one spec.