15ecdb8033
Now an OpenStack driver for Kubernetes Cluster Autoscaler is being
proposed to support autoscaling when running k8s cluster on top of
OpenStack. However, currently there is no way in Magnum to let
the external consumer to control which node will be removed. The
alternative option is calling Heat API directly but obviously it
is not the best solution and it's confusing k8s community. So with
this patch, we're going to add a new API:
POST <ClusterID>/actions/resize
And the post body will be:
{
"node_count": 3,
"nodes_to_remove": ["dd9cc5ed-3a2b-11e9-9233-fa163e46bcc2"],
"nodegroup": "production_group"
}
The API will be working in a declarative way. For example, there
are 3 nodes in the cluser now, user can propose an API request
like above. Magnum will call Heat to remove the node
dd9cc5ed-3a2b-11e9-9233-fa163e46bcc2 firstly, then bring the node
count back to 3 again.
Task: 29563
Story: 2005052
Change-Id: I7e36ce82c3f442976cc498153950b19c56a1759f
12 lines
511 B
YAML
12 lines
511 B
YAML
---
|
|
features:
|
|
- |
|
|
Now an OpenStack driver for Kubernetes Cluster Autoscaler is being
|
|
proposed to support autoscaling when running k8s cluster on top of
|
|
OpenStack. However, currently there is no way in Magnum to let
|
|
the external consumer to control which node will be removed. The
|
|
alternative option is calling Heat API directly but obviously it
|
|
is not the best solution and it's confusing k8s community. So this
|
|
new API is being added into Magnum: POST <ClusterID>/actions/resize
|
|
|