Last modified March 2, 2022
'gsctl update nodepool' command reference
gsctl and the REST API are being phased out. We don't have an end-of-life date yet. However, we recommend to familiarize yourself with our Management API and the kubectl gs plugin as a future-proof replacement. We provide a migration page to help you with the transition.
The gsctl update nodepool
command allows modifying a node pool, such as editing the scaling range and the name.
Usage
The command is called with the cluster and node pool ID as a positional argument,
separated by a slash. The --name
flag is used to set a new name.
Example for renaming a node pool:
gsctl update nodepool f01r4/op1dl --name "New node pool name"
Here, f01r4
is the cluster ID and op1dl
is the node pool ID.
You can also use the cluster’s name for identifying the cluster:
gsctl update nodepool "Cluster name"/opdl --name "New node pool name"
Example for adjusting the scaling limits:
- Autoscaling enabled (AWS and Azure 13.1.0 or newer)
gsctl update nodepool f01r4/op1dl --nodes-min 3 --nodes-max 20
- No Autoscaling
gsctl update nodepool f01r4/op1dl --nodes-min 6 --nodes-max 6
Related
gsctl create nodepool
- Add a node pool to a clustergsctl list nodepools
- List all node pools of a clustergsctl update nodepool
- Modify a node poolgsctl delete nodepool
- Delete a node pool
Need help, got feedback?
We listen to your Slack support channel. You can also reach us at support@giantswarm.io. And of course, we welcome your pull requests!