autopilot.costgraph.ai/. Set them on a workload (Deployment, StatefulSet,
DaemonSet, Job, CronJob or Argo Rollout) or on its namespace.
For each key the first value found wins, in this order:
- The workload annotation.
- The namespace annotation.
- The built-in default.
via also has a cluster setting, global.autopilot.defaultVia in the operator chart. It applies between the namespace annotation and the built-in default.
Settings that come from an annotation show as locked in CostGraph, marked “set in Git”.
Keys
The change window only limits reductions. Increases and out-of-memory bumps are applied at any time.
Invalid values
A bad value affects that key only. AutoPilot ignores it, uses the next level down (the namespace annotation, then the default), and reports the problem on the workload in CostGraph. Everything else still applies. Unknown keys under the prefix are reported as warnings. For example,cpu.max: two is ignored and the namespace or default CPU maximum
applies, while a valid memory.max on the same workload still takes effect.