AgentConfiguration
Tune deployment agent behavior via the AgentConfiguration CRD
AgentConfiguration tunes how the Plural deployment agent runs on a given cluster. Unlike DeploymentSettings, which configures global Console settings from the management cluster, AgentConfiguration is applied on each agent cluster and controls local operator behavior: poll intervals, concurrency limits, image registry overrides for job pods, and websocket connectivity.
Use it when you need per-cluster tuning — for example, slowing stack polling on a large fleet member, capping concurrent stack run jobs, or pointing stack/sentinel/agent-run images at an internal registry.
Singleton resource
AgentConfiguration is cluster-scoped and a singleton. The deployment operator only reconciles a resource named default:
Field | Required value |
|---|---|
metadata.name | default |
metadata.namespace | (none — cluster-scoped) |
Resources with any other name are ignored. 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, only the default AgentConfiguration will be reconciled
When the name is correct and the spec is valid, expect Synchronized=True and Ready=True on status.conditions.
Neutral:
Do not create multiple AgentConfiguration resources expecting them all to apply. Only default is processed. Merge all desired settings into a single spec.