imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 06:47:12 +00:00
Code Activity

gcloud: Wed Jun 29 09:00:05 UTC 2022

Browse source
This commit is contained in:
Automated 2022-06-29 09:00:05 +00:00
parent 8b80260bd9
commit cf5ab60e4a
Failed to extract signature
195 changed files with 4700 additions and 413 deletions
Download patch file Download diff file Expand all files Collapse all files

19
gcloud/alpha/container/aws/clusters/update
View file

@ -7,8 +7,9 @@ SYNOPSIS
[--admin-users=USER,[USER,...]] [--async]
[--cluster-version=CLUSTER_VERSION]
[--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN]
[--instance-type=INSTANCE_TYPE] [--role-arn=ROLE_ARN]
[--role-session-name=ROLE_SESSION_NAME]
[--iam-instance-profile=IAM_INSTANCE_PROFILE]
[--instance-type=INSTANCE_TYPE] [--logging=COMPONENT,[COMPONENT,...]]
[--role-arn=ROLE_ARN] [--role-session-name=ROLE_SESSION_NAME]
[--root-volume-iops=ROOT_VOLUME_IOPS]
[--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN]
[--root-volume-size=ROOT_VOLUME_SIZE]
@ -71,9 +72,23 @@ FLAGS
--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN
Amazon Resource Name (ARN) of the AWS KMS key to encrypt the user data.
--iam-instance-profile=IAM_INSTANCE_PROFILE
Name or ARN of the IAM instance profile associated with the cluster.
--instance-type=INSTANCE_TYPE
AWS EC2 instance type for the control plane's nodes.
--logging=COMPONENT,[COMPONENT,...]
Set the components that have logging enabled.
Examples:
$ gcloud alpha container aws clusters update --logging=SYSTEM
$ gcloud alpha container aws clusters update \
--logging=SYSTEM,WORKLOAD
COMPONENT must be one of: SYSTEM, WORKLOAD.
--role-arn=ROLE_ARN
Amazon Resource Name (ARN) of the IAM role to assume when managing AWS
resources.

4
gcloud/alpha/container/aws/node-pools/update
View file

@ -6,6 +6,7 @@ SYNOPSIS
gcloud alpha container aws node-pools update
(NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async]
[--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN]
[--iam-instance-profile=IAM_INSTANCE_PROFILE]
[--node-version=NODE_VERSION] [--root-volume-iops=ROOT_VOLUME_IOPS]
[--root-volume-kms-key-arn=ROOT_VOLUME_KMS_KEY_ARN]
[--root-volume-size=ROOT_VOLUME_SIZE]
@ -71,6 +72,9 @@ FLAGS
--config-encryption-kms-key-arn=CONFIG_ENCRYPTION_KMS_KEY_ARN
Amazon Resource Name (ARN) of the AWS KMS key to encrypt the user data.
--iam-instance-profile=IAM_INSTANCE_PROFILE
Name or ARN of the IAM instance profile associated with the node pool.
--node-version=NODE_VERSION
Kubernetes version to use for the node pool.

19
gcloud/alpha/container/azure/clusters/update
View file

@ -6,8 +6,9 @@ SYNOPSIS
gcloud alpha container azure clusters update
(CLUSTER : --location=LOCATION) --client=CLIENT
[--admin-users=USER,[USER,...]] [--async]
[--cluster-version=CLUSTER_VERSION] [--validate-only]
[--vm-size=VM_SIZE] [GCLOUD_WIDE_FLAG ...]
[--cluster-version=CLUSTER_VERSION]
[--logging=COMPONENT,[COMPONENT,...]] [--ssh-public-key=SSH_PUBLIC_KEY]
[--validate-only] [--vm-size=VM_SIZE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Update an Anthos cluster on Azure.
@ -76,6 +77,20 @@ FLAGS
--cluster-version=CLUSTER_VERSION
Kubernetes version to use for the cluster.
--logging=COMPONENT,[COMPONENT,...]
Set the components that have logging enabled.
Examples:
$ gcloud alpha container azure clusters update --logging=SYSTEM
$ gcloud alpha container azure clusters update \
--logging=SYSTEM,WORKLOAD
COMPONENT must be one of: SYSTEM, WORKLOAD.
--ssh-public-key=SSH_PUBLIC_KEY
SSH public key to use for authentication.
--validate-only
Validate the update of the cluster, but don't actually perform it.

55
gcloud/alpha/container/clusters/create
View file

@ -20,7 +20,7 @@ SYNOPSIS
[--disk-size=DISK_SIZE] [--disk-type=DISK_TYPE] [--enable-autorepair]
[--no-enable-autoupgrade] [--enable-binauthz] [--enable-cloud-logging]
[--enable-cloud-monitoring] [--enable-cloud-run-alpha]
[--enable-confidential-nodes] [--enable-cost-management]
[--enable-confidential-nodes] [--enable-cost-allocation]
[--enable-dataplane-v2] [--enable-gke-oidc] [--enable-gvnic]
[--enable-identity-service] [--enable-image-streaming]
[--enable-intra-node-visibility] [--enable-ip-alias]
@ -32,7 +32,7 @@ SYNOPSIS
[--enable-shielded-nodes] [--enable-stackdriver-kubernetes]
[--enable-vertical-pod-autoscaling]
[--identity-provider=IDENTITY_PROVIDER] [--image-type=IMAGE_TYPE]
[--issue-client-certificate]
[--ipv6-access-type=IPV6_ACCESS_TYPE] [--issue-client-certificate]
[--istio-config=[auth=MTLS_PERMISSIVE,...]] [--labels=[KEY=VALUE,...]]
[--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]] [--logging=[COMPONENT,...]]
[--machine-type=MACHINE_TYPE, -m MACHINE_TYPE]
@ -53,7 +53,7 @@ SYNOPSIS
[--release-channel=CHANNEL] [--security-group=SECURITY_GROUP]
[--services-ipv4-cidr=CIDR] [--services-secondary-range-name=NAME]
[--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot]
[--subnetwork=SUBNETWORK]
[--stack-type=STACK_TYPE] [--subnetwork=SUBNETWORK]
[--system-config-from-file=SYSTEM_CONFIG_FROM_FILE]
[--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE]
[--workload-metadata=WORKLOAD_METADATA] [--workload-pool=WORKLOAD_POOL]
@ -67,8 +67,12 @@ SYNOPSIS
--autoprovisioning-locations=ZONE,[ZONE,...]
--autoprovisioning-min-cpu-platform=PLATFORM --min-cpu=MIN_CPU
--min-memory=MIN_MEMORY
--autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-scopes=[SCOPE,
...]
--autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION --autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,
batch-percent=BATCH_NODE_PERCENTAGE,
batch-soak-duration=BATCH_SOAK_DURATION,...]
--enable-autoprovisioning-blue-green-upgrade
| --enable-autoprovisioning-surge-upgrade
--autoprovisioning-scopes=[SCOPE,...]
--autoprovisioning-service-account=AUTOPROVISIONING_SERVICE_ACCOUNT
--enable-autoprovisioning-autorepair
--enable-autoprovisioning-autoupgrade
@ -379,7 +383,7 @@ FLAGS
will create nodes using Confidential VM
https://cloud.google.com/compute/confidential-vm/docs/about-cvm.
--enable-cost-management
--enable-cost-allocation
Enable the cost management feature.
When enabled, you can get informational GKE cost breakdowns by cluster,
@ -531,6 +535,10 @@ FLAGS
$ gcloud container get-server-config
--ipv6-access-type=IPV6_ACCESS_TYPE
IPv6 access type of the subnetwork. Defaults to 'external'.
IPV6_ACCESS_TYPE must be one of: external, internal.
--issue-client-certificate
Issue a TLS client certificate with admin permissions.
@ -930,6 +938,10 @@ FLAGS
New nodes, including ones created by resize or recreate, will use spot
VM instances.
--stack-type=STACK_TYPE
IP stack type of the node VMs. Defaults to 'ipv4'. STACK_TYPE must be
one of: ipv4, ipv4-ipv6.
--subnetwork=SUBNETWORK
The Google Compute Engine subnetwork
(https://cloud.google.com/compute/docs/subnetworks) to which the
@ -1256,6 +1268,37 @@ FLAGS
Number of nodes that can be unavailable at the same time on
each upgrade of an autoprovisioned node pool.
--autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION
Time in seconds to be spent waiting during blue-green upgrade
before deleting the blue pool and completing the update. This
argument should be used in conjunction with
--enable-autoprovisioning-blue-green-upgrade to take effect.
--autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...]
Standard rollout policy options for blue-green upgrade. This
argument should be used in conjunction with
--enable-autoprovisioning-blue-green-upgrade to take effect.
Batch sizes are specfied by one of, batch-node-count or
batch-percent. The duration between batches is specified by
batch-soak-duration.
Example:
--standard-rollout-policy=batch-node-count=3,batch-soak-duration=60s
--standard-rollout-policy=batch-percent=0.05,batch-soak-duration=180s
Flag group to choose the top level upgrade option:
At most one of these can be specified:
--enable-autoprovisioning-blue-green-upgrade
Whether to use blue-green upgrade for the autoprovisioned
node pool.
--enable-autoprovisioning-surge-upgrade
Whether to use surge upgrade for the autoprovisioned node
pool.
Flags to specify identity for autoprovisioned nodes:
--autoprovisioning-scopes=[SCOPE,...]

45
gcloud/alpha/container/clusters/update
View file

@ -10,7 +10,7 @@ SYNOPSIS
| --database-encryption-key=DATABASE_ENCRYPTION_KEY
| --disable-database-encryption | --disable-default-snat
| --disable-workload-identity | --enable-autoscaling
| --enable-binauthz | --enable-cost-management | --enable-gke-oidc
| --enable-binauthz | --enable-cost-allocation | --enable-gke-oidc
| --enable-identity-service | --enable-image-streaming
| --enable-intra-node-visibility | --enable-l4-ilb-subsetting
| --enable-legacy-authorization
@ -51,8 +51,12 @@ SYNOPSIS
--autoprovisioning-locations=ZONE,[ZONE,...]
--autoprovisioning-min-cpu-platform=PLATFORM --max-cpu=MAX_CPU
--max-memory=MAX_MEMORY --min-cpu=MIN_CPU --min-memory=MIN_MEMORY
--autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-scopes=[SCOPE,
...]
--autoprovisioning-max-surge-upgrade=AUTOPROVISIONING_MAX_SURGE_UPGRADE --autoprovisioning-max-unavailable-upgrade=AUTOPROVISIONING_MAX_UNAVAILABLE_UPGRADE --autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION --autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,
batch-percent=BATCH_NODE_PERCENTAGE,
batch-soak-duration=BATCH_SOAK_DURATION,...]
--enable-autoprovisioning-blue-green-upgrade
| --enable-autoprovisioning-surge-upgrade
--autoprovisioning-scopes=[SCOPE,...]
--autoprovisioning-service-account=AUTOPROVISIONING_SERVICE_ACCOUNT
--enable-autoprovisioning-autorepair
--enable-autoprovisioning-autoupgrade
@ -181,7 +185,7 @@ REQUIRED FLAGS
--enable-binauthz
Enable Binary Authorization for this cluster.
--enable-cost-management
--enable-cost-allocation
Enable the cost management feature.
When enabled, you can get informational GKE cost breakdowns by
@ -189,7 +193,7 @@ REQUIRED FLAGS
BigQuery
(https://cloud.google.com/billing/docs/how-to/export-data-bigquery).
Use --no-enable-cost-management to disable this feature.
Use --no-enable-cost-allocation to disable this feature.
--enable-gke-oidc
(DEPRECATED) Enable GKE OIDC authentication on the cluster.
@ -855,6 +859,37 @@ REQUIRED FLAGS
Number of nodes that can be unavailable at the same time on
each upgrade of an autoprovisioned node pool.
--autoprovisioning-node-pool-soak-duration=AUTOPROVISIONING_NODE_POOL_SOAK_DURATION
Time in seconds to be spent waiting during blue-green upgrade
before deleting the blue pool and completing the update. This
argument should be used in conjunction with
--enable-autoprovisioning-blue-green-upgrade to take effect.
--autoprovisioning-standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...]
Standard rollout policy options for blue-green upgrade. This
argument should be used in conjunction with
--enable-autoprovisioning-blue-green-upgrade to take effect.
Batch sizes are specfied by one of, batch-node-count or
batch-percent. The duration between batches is specified by
batch-soak-duration.
Example:
--standard-rollout-policy=batch-node-count=3,batch-soak-duration=60s
--standard-rollout-policy=batch-percent=0.05,batch-soak-duration=180s
Flag group to choose the top level upgrade option:
At most one of these can be specified:
--enable-autoprovisioning-blue-green-upgrade
Whether to use blue-green upgrade for the autoprovisioned
node pool.
--enable-autoprovisioning-surge-upgrade
Whether to use surge upgrade for the autoprovisioned node
pool.
Flags to specify identity for autoprovisioned nodes:
--autoprovisioning-scopes=[SCOPE,...]

57
gcloud/alpha/container/node-pools/complete-upgrade Normal file
View file

@ -0,0 +1,57 @@
NAME
gcloud alpha container node-pools complete-upgrade - complete a node pool
upgrade
SYNOPSIS
gcloud alpha container node-pools complete-upgrade NAME [--cluster=CLUSTER]
[--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Complete a node pool upgrade.
Complete upgrade is a method used to skip the remaining node pool soaking
phase during blue-green node pool upgrades.
EXAMPLES
To complete an active upgrade in node-pool-1 in the cluster sample-cluster,
run:
$ gcloud alpha container node-pools complete-upgrade node-pool-1 \
--cluster=sample-cluster
POSITIONAL ARGUMENTS
NAME
Name of the node pool for which the upgrade is to be completed.
FLAGS
--cluster=CLUSTER
Cluster to which the node pool belongs. Overrides the default
container/cluster property value for this command invocation.
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.
GCLOUD WIDE FLAGS
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.
NOTES
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 complete-upgrade
$ gcloud beta container node-pools complete-upgrade

49
gcloud/alpha/container/node-pools/create
View file

@ -9,9 +9,9 @@ SYNOPSIS
[--disable-pod-cidr-overprovision] [--disk-size=DISK_SIZE]
[--disk-type=DISK_TYPE] [--enable-autoprovisioning]
[--enable-autorepair] [--no-enable-autoupgrade]
[--enable-confidential-nodes] [--enable-gvnic]
[--enable-image-streaming] [--image-type=IMAGE_TYPE]
[--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]]
[--enable-blue-green-upgrade] [--enable-confidential-nodes]
[--enable-gvnic] [--enable-image-streaming] [--enable-surge-upgrade]
[--image-type=IMAGE_TYPE] [--linux-sysctls=KEY=VALUE,[KEY=VALUE,...]]
[--machine-type=MACHINE_TYPE, -m MACHINE_TYPE]
[--max-pods-per-node=MAX_PODS_PER_NODE]
[--max-surge-upgrade=MAX_SURGE_UPGRADE; default=1]
@ -21,11 +21,15 @@ SYNOPSIS
[--min-cpu-platform=PLATFORM]
[--network-performance-configs=[PROPERTY=VALUE,...]]
[--node-group=NODE_GROUP] [--node-labels=[NODE_LABEL,...]]
[--node-locations=ZONE,[ZONE,...]] [--node-taints=[NODE_TAINT,...]]
[--node-version=NODE_VERSION] [--num-nodes=NUM_NODES; default=3]
[--placement-type=PLACEMENT_TYPE] [--preemptible]
[--sandbox=[type=TYPE]] [--shielded-integrity-monitoring]
[--shielded-secure-boot] [--spot]
[--node-locations=ZONE,[ZONE,...]]
[--node-pool-soak-duration=NODE_POOL_SOAK_DURATION]
[--node-taints=[NODE_TAINT,...]] [--node-version=NODE_VERSION]
[--num-nodes=NUM_NODES; default=3] [--placement-type=PLACEMENT_TYPE]
[--preemptible] [--sandbox=[type=TYPE]]
[--shielded-integrity-monitoring] [--shielded-secure-boot] [--spot]
[--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,
batch-percent=BATCH_NODE_PERCENTAGE,
batch-soak-duration=BATCH_SOAK_DURATION,...]]
[--system-config-from-file=SYSTEM_CONFIG_FROM_FILE]
[--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE]
[--workload-metadata=WORKLOAD_METADATA]
@ -135,6 +139,9 @@ FLAGS
Enabled by default, use --no-enable-autoupgrade to disable.
--enable-blue-green-upgrade
Changes node pool upgrade strategy to blue-green upgrade.
--enable-confidential-nodes
Enable confidential nodes for the node pool. Enabling Confidential
Nodes will create nodes using Confidential VM
@ -147,6 +154,9 @@ FLAGS
--enable-image-streaming
Specifies whether to enable image streaming on node pool.
--enable-surge-upgrade
Changes node pool upgrade strategy to surge upgrade.
--image-type=IMAGE_TYPE
The image type to use for the node pool. Defaults to server-specified.
@ -337,6 +347,13 @@ FLAGS
--cluster=sample-cluster \
--node-locations=us-central1-a,us-central1-b
--node-pool-soak-duration=NODE_POOL_SOAK_DURATION
Time in seconds to be spent waiting during blue-green upgrade before
deleting the blue pool and completing the upgrade.
$ gcloud alpha container node-pools create node-pool-1 \
--cluster=example-cluster --node-pool-soak-duration=600s
--node-taints=[NODE_TAINT,...]
Applies the given kubernetes taints on all nodes in the new node pool,
which can be used with tolerations for pod scheduling.
@ -416,6 +433,22 @@ FLAGS
New nodes, including ones created by resize or recreate, will use spot
VM instances.
--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...]
Standard rollout policy options for blue-green upgrade.
Batch sizes are specfied by one of, batch-node-count or batch-percent.
The duration between batches is specified by batch-soak-duration.
$ gcloud alpha container node-pools create node-pool-1 \
--cluster=example-cluster \
--standard-rollout-policy=batch-node-count=3,\
batch-soak-duration=60s
$ gcloud alpha container node-pools create node-pool-1 \
--cluster=example-cluster \
--standard-rollout-policy=batch-percent=0.3,\
batch-soak-duration=60s
--system-config-from-file=SYSTEM_CONFIG_FROM_FILE
Path of the YAML/JSON file that contains the node configuration,
including Linux kernel parameters (sysctls) and kubelet configs.

3
gcloud/alpha/container/node-pools/help
View file

@ -34,6 +34,9 @@ GROUPS
COMMANDS
COMMAND is one of the following:
complete-upgrade
(ALPHA) Complete a node pool upgrade.
create
(ALPHA) Create a node pool in a running cluster.

8
gcloud/alpha/container/node-pools/rollback
View file

@ -3,8 +3,8 @@ NAME
SYNOPSIS
gcloud alpha container node-pools rollback NAME [--async]
[--cluster=CLUSTER] [--region=REGION | --zone=ZONE, -z ZONE]
[GCLOUD_WIDE_FLAG ...]
[--cluster=CLUSTER] [--respect-pdb=RESPECT_PDB]
[--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Rollback a node-pool upgrade.
@ -32,6 +32,10 @@ FLAGS
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

44
gcloud/alpha/container/node-pools/update
View file

@ -14,17 +14,21 @@ SYNOPSIS
| --enable-autoprovisioning
--enable-autoscaling --max-nodes=MAX_NODES --min-nodes=MIN_NODES
| --enable-autorepair --enable-autoupgrade
| --max-surge-upgrade=MAX_SURGE_UPGRADE
--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE)
[--cluster=CLUSTER] [--region=REGION | --zone=ZONE, -z ZONE]
[GCLOUD_WIDE_FLAG ...]
| --enable-blue-green-upgrade --enable-surge-upgrade
--max-surge-upgrade=MAX_SURGE_UPGRADE
--max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE
--node-pool-soak-duration=NODE_POOL_SOAK_DURATION
--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,
batch-percent=BATCH_NODE_PERCENTAGE,
batch-soak-duration=BATCH_SOAK_DURATION,...]) [--cluster=CLUSTER]
[--region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) gcloud alpha container node-pools update updates a node pool in a
Google Kubernetes Engine cluster.
EXAMPLES
To turn on node auto repair in "node-pool-1" in the cluster
To turn on node autoupgrade in "node-pool-1" in the cluster
"sample-cluster", run:
$ gcloud alpha container node-pools update node-pool-1 \
@ -254,6 +258,12 @@ REQUIRED FLAGS
Upgrade settings
--enable-blue-green-upgrade
Changes node pool upgrade strategy to blue-green upgrade.
--enable-surge-upgrade
Changes node pool upgrade strategy to surge upgrade.
--max-surge-upgrade=MAX_SURGE_UPGRADE
Number of extra (surge) nodes to be created on each upgrade of the
node pool.
@ -286,6 +296,30 @@ REQUIRED FLAGS
Must be used in conjunction with '--max-surge-upgrade'.
--node-pool-soak-duration=NODE_POOL_SOAK_DURATION
Time in seconds to be spent waiting during blue-green upgrade
before deleting the blue pool and completing the upgrade.
$ gcloud alpha container node-pools update node-pool-1 \
--cluster=example-cluster --node-pool-soak-duration=600s
--standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...]
Standard rollout policy options for blue-green upgrade.
Batch sizes are specfied by one of, batch-node-count or
batch-percent. The duration between batches is specified by
batch-soak-duration.
$ gcloud alpha container node-pools update node-pool-1 \
--cluster=example-cluster \
--standard-rollout-policy=batch-node-count=3,\
batch-soak-duration=60s
$ gcloud alpha container node-pools update node-pool-1 \
--cluster=example-cluster \
--standard-rollout-policy=batch-percent=0.3,\
batch-soak-duration=60s
OPTIONAL FLAGS
--cluster=CLUSTER
The name of the cluster. Overrides the default container/cluster

4
gcloud/alpha/container/operations/cancel
View file

@ -47,7 +47,9 @@ NOTES
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. This variant is also available:
access allowlist. These variants are also available:
$ gcloud container operations cancel
$ gcloud beta container operations cancel