gcloud alpha container node-pools rollback - rollback a node-pool upgrade
gcloud alpha container node-pools rollback NAME [--async] [--cluster=CLUSTER] [--respect-pdb=RESPECT_PDB] [--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...]
(ALPHA) Rollback a node-pool upgrade.
Rollback is a method used after a canceled or failed node-pool upgrade. It makes a best-effort attempt to revert the pool back to its original state.
To roll back a canceled or failed upgrade in "node-pool-1" in the cluster "sample-cluster", run:
$ gcloud alpha container node-pools rollback node-pool-1 \ --cluster=sample-cluster
- NAME
The name of the node pool to rollback.
- --async
Return immediately, without waiting for the operation in progress to complete.
- --cluster=CLUSTER
The cluster from which to rollback the node pool. Overrides the default container/cluster property value for this command invocation.
- --respect-pdb=RESPECT_PDB
Indicates whether node pool rollbacks should respect pod disruption budgets.
- At most one of these can be specified:
- --region=REGION
Compute region (e.g. us-central1) for the cluster.
- --zone=ZONE, -z ZONE
Compute zone (e.g. us-central1-a) for the cluster. Overrides the default compute/zone property value for this command invocation.
These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, --help, --impersonate-service-account, --log-http, --project, --quiet, --trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct project, you might be trying to access an API with an invitation-only early access allowlist. These variants are also available:
$ gcloud container node-pools rollback
$ gcloud beta container node-pools rollback