--account <ACCOUNT> | Google Cloud Platform user account to use for invocation. Overrides the default *core/account* property value for this command invocation |
--billing-project <BILLING_PROJECT> | The Google Cloud Platform project that will be charged quota for operations performed in gcloud. If you need to operate on one project, but need quota against a different project, you can use this flag to specify the billing project. If both `billing/quota_project` and `--billing-project` are specified, `--billing-project` takes precedence. Run `$ gcloud config set --help` to see more information about `billing/quota_project` |
--cluster <CLUSTER> | The name of the cluster. Overrides the default *container/cluster* property value for this command invocation |
--configuration <CONFIGURATION> | The configuration to use for this command invocation. For more
information on how to use configurations, run:
`gcloud topic configurations`. You can also use the CLOUDSDK_ACTIVE_CONFIG_NAME environment
variable to set the equivalent of this flag for a terminal
session |
--enable-autoprovisioning | Enables Cluster Autoscaler to treat the node pool as if it was autoprovisioned.
+
Cluster Autoscaler will be able to delete the node pool if it's unneeded |
--enable-autorepair | Enable node autorepair feature for a node pool.
+
$ {command} node-pool-1 --cluster=example-cluster --enable-autorepair
+
See https://cloud.google.com/kubernetes-engine/docs/how-to/node-auto-repair for more info |
--enable-autoscaling | Enables autoscaling for a node pool.
+
Enables autoscaling in the node pool specified by --node-pool or
the default node pool if --node-pool is not provided |
--enable-autoupgrade | Sets autoupgrade feature for a node pool.
+
$ {command} node-pool-1 --cluster=example-cluster --enable-autoupgrade
+
See https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades for more info |
--flags-file <YAML_FILE> | A YAML or JSON file that specifies a *--flag*:*value* dictionary.
Useful for specifying complex flag values with special characters
that work with any command interpreter. Additionally, each
*--flags-file* arg is replaced by its constituent flags. See
$ gcloud topic flags-file for more information |
--flatten <KEY> | Flatten _name_[] output resource slices in _KEY_ into separate records
for each item in each slice. Multiple keys and slices may be specified.
This also flattens keys for *--format* and *--filter*. For example,
*--flatten=abc.def* flattens *abc.def[].ghi* references to
*abc.def.ghi*. A resource record containing *abc.def[]* with N elements
will expand to N records in the flattened output. This flag interacts
with other flags that are applied in this order: *--flatten*,
*--sort-by*, *--filter*, *--limit* |
--format <FORMAT> | Set the format for printing command output resources. The default is a
command-specific human-friendly output format. The supported formats
are: `config`, `csv`, `default`, `diff`, `disable`, `flattened`, `get`, `json`, `list`, `multi`, `none`, `object`, `table`, `text`, `value`, `yaml`. For more details run $ gcloud topic formats |
--help | Display detailed help |
--impersonate-service-account <SERVICE_ACCOUNT_EMAIL> | For this gcloud invocation, all API requests will be made as the given service account instead of the currently selected account. This is done without needing to create, download, and activate a key for the account. In order to perform operations as the service account, your currently selected account must have an IAM role that includes the iam.serviceAccounts.getAccessToken permission for the service account. The roles/iam.serviceAccountTokenCreator role has this permission or you may create a custom role. Overrides the default *auth/impersonate_service_account* property value for this command invocation |
--log-http | Log all HTTP server requests and responses to stderr. Overrides the default *core/log_http* property value for this command invocation |
--max-nodes <MAX_NODES> | Maximum number of nodes in the node pool.
+
Maximum number of nodes to which the node pool specified by --node-pool
(or default node pool if unspecified) can scale. Ignored unless
--enable-autoscaling is also specified |
--max-surge-upgrade <MAX_SURGE_UPGRADE> | Number of extra (surge) nodes to be created on each upgrade of the node pool.
+
Specifies the number of extra (surge) nodes to be created during this node
pool's upgrades. For example, running the following command will result in
creating an extra node each time the node pool is upgraded:
+
$ {command} node-pool-1 --cluster=example-cluster --max-surge-upgrade=1 --max-unavailable-upgrade=0
+
Must be used in conjunction with '--max-unavailable-upgrade' |
--max-unavailable-upgrade <MAX_UNAVAILABLE_UPGRADE> | Number of nodes that can be unavailable at the same time on each upgrade of the
node pool.
+
Specifies the number of nodes that can be unavailable at the same time during
this node pool's upgrades. For example, assume the node pool has 5 nodes,
running the following command will result in having 3 nodes being upgraded in
parallel (1 + 2), but keeping always at least 3 (5 - 2) available each time the
node pool is upgraded:
+
$ {command} node-pool-1 --cluster=example-cluster --max-surge-upgrade=1 --max-unavailable-upgrade=2
+
Must be used in conjunction with '--max-surge-upgrade' |
--min-nodes <MIN_NODES> | Minimum number of nodes in the node pool.
+
Minimum number of nodes to which the node pool specified by --node-pool
(or default node pool if unspecified) can scale. Ignored unless
--enable-autoscaling is also specified |
--node-locations <ZONE> | Set of zones in which the node pool's nodes should be located.
Changing the locations for a node pool will result in nodes being either created or removed
from the node pool, depending on whether locations are being added or removed.
+
Multiple locations can be specified, separated by commas. For example:
+
$ {command} node-pool-1 --node-locations=us-central1-a,us-central1-b |
--project <PROJECT_ID> | The Google Cloud Platform project ID to use for this invocation. If
omitted, then the current project is assumed; the current project can
be listed using `gcloud config list --format='text(core.project)'`
and can be set using `gcloud config set project PROJECTID`.
+
`--project` and its fallback `core/project` property play two roles
in the invocation. It specifies the project of the resource to
operate on. It also specifies the project for API enablement check,
quota, and billing. To specify a different project for quota and
billing, use `--billing-project` or `billing/quota_project` property |
--quiet | Disable all interactive prompts when running gcloud commands. If input
is required, defaults will be used, or an error will be raised.
Overrides the default core/disable_prompts property value for this
command invocation. This is equivalent to setting the environment
variable `CLOUDSDK_CORE_DISABLE_PROMPTS` to 1 |
--region <REGION> | Compute region (e.g. us-central1) for the cluster |
--trace-token <TRACE_TOKEN> | Token used to route traces of service requests for investigation of issues. Overrides the default *core/trace_token* property value for this command invocation |
--user-output-enabled | Print user intended output to the console. Overrides the default *core/user_output_enabled* property value for this command invocation. Use *--no-user-output-enabled* to disable |
--verbosity <VERBOSITY> | Override the default verbosity for this command. Overrides the default *core/verbosity* property value for this command invocation. _VERBOSITY_ must be one of: *debug*, *info*, *warning*, *error*, *critical*, *none* |
--workload-metadata <WORKLOAD_METADATA> | Type of metadata server available to pods running in the node pool. _WORKLOAD_METADATA_ must be one of:
+
*GCE_METADATA*::: Pods running in this node pool have access to the node's underlying Compute Engine Metadata Server.
*GKE_METADATA*::: Run the Kubernetes Engine Metadata Server on this node. The Kubernetes Engine Metadata Server exposes a metadata API to workloads that is compatible with the V1 Compute Metadata APIs exposed by the Compute Engine and App Engine Metadata Servers. This feature can only be enabled if Workload Identity is enabled at the cluster level.
:::
+ |
--zone <ZONE> | Compute zone (e.g. us-central1-a) for the cluster. Overrides the default *compute/zone* property value for this command invocation |