Upgrade to custom pod autoscaler v0.10.0
Closed this issue · 0 comments
jthomperoo commented
Upgrade to custom pod autoscaler v0.10.0
[v0.10.0] - 2020-01-22
Added
- Set up API to be versioned, starting with
v1
. - Can now manually trigger scaling through the API.
- Added extra
run_type
flag,api_dry_run
, for evaluations through the API indry_run
mode. - Added
apiConfig
to hold configuration for the REST API. - Added extra configuration options within
apiConfig
.enabled
- allows enabling or disabling the API, default enabled (true
).useHTTPS
- allows enabling or disabling HTTPS for the API, default off (false
).certFile
- cert file to be used if HTTPS is enabled.keyFile
- key file to be used if HTTPS is enabled.
Changed
- The
command
forshell
methods is now an array of arguments, rather than a string. - The
/api/v1/evaluation
endpoint now requiresPOST
rather thanGET
. - The
/api/v1/evaluation
endpoint now accepts an optional parameter,dry_run
. Ifdry_run
is true the evaluation will be retrieved in a read-only manner, the scaling will not occur. If it is false, or not provided, the evaluation will be retrieved and then used to apply scaling to the target. - Moved
port
andhost
configuration options into theapiConfig
settings.
[v0.9.0] - 2020-01-19
Added
- Support for other entrypoints other than
/bin/sh
, can specify an entrypoint for the shell command method. - Add logging library
glog
to allow logging at levels of severity and verbosity. - Can specify verbosity level of logs via the
logVerbosity
configuration option.
Changed
- Can scale ReplicaSets, ReplicationControllers and StatefulSets alongside Deployments.
- ResourceMetrics fields have
resourceName
andresource
rather thandeploymentName
anddeployment
. In JSON this means that only the resource name will be exposed via fieldresource
. - Uses scaling API rather than manually adjusting replica count on resource.
- Matches using match selector rather than incorrectly using resource labels and building a different selector.