Scopes
Scopes hold configuration values which influence scaling. They define a uniform way of how to select which of the values gets used.
How It Works
The resulting value is always the one set by the most specific scope that has set that value.
This means Workload Scope > Namespace Scope > CLI Scope > ENV Scope > Default Scope.
Loading...Value Groups
Some values within in a scope set/define very similar properties (e.g. Force Downtime and Force Uptime; Downscale Period, Downtime, Upscale Period and Uptime)
These values are not all handled separately when choosing which scope to take the values from. Instead if one of them is set in a scope, the other values will be taken from the same scope.
Incompatibilities between values normally only occur between values in the same value group and therefore the values on that same scope.
Workload Scope
Defined by the annotations on the workload every scan.
The most specific scope. If a value gets set here it will be used for scaling.
Namespace Scope
Defined by the annotations on the namespace every scan.
Values set here can be overwritten by the workload scope
CLI Scope
Defined by the cli arguments at startup.
Values set here can be overwritten by the namespace and workload scope
Environment Scope
Defined by the environment variables at startup.
Values set here can be overwritten by the cli, the namespace and workload scope.
With the current setup it is not possible to update these values every scan, as the value of config maps is only passed in at creation of the deployment.
Default Scope
Holds the defaults for all values.
Values set here can be overwritten by all other scopes.