mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Oct 15 10:52:53 UTC 2025
This commit is contained in:
parent
6f9bb9a0f0
commit
154ebc873d
299 changed files with 7497 additions and 3961 deletions
|
|
@ -43,7 +43,8 @@ SYNOPSIS
|
|||
[--enable-identity-service] [--enable-image-streaming]
|
||||
[--enable-insecure-kubelet-readonly-port]
|
||||
[--enable-intra-node-visibility] [--enable-ip-access]
|
||||
[--enable-ip-alias] [--enable-kubernetes-alpha]
|
||||
[--enable-ip-alias] [--enable-k8s-certs-via-dns]
|
||||
[--enable-k8s-tokens-via-dns] [--enable-kubernetes-alpha]
|
||||
[--enable-kubernetes-unstable-apis=API,[API,...]]
|
||||
[--enable-l4-ilb-subsetting] [--enable-legacy-authorization]
|
||||
[--enable-legacy-lustre-port] [--enable-logging-monitoring-system-only]
|
||||
|
|
@ -682,6 +683,14 @@ FLAGS
|
|||
you omit both --enable-ip-alias and --no-enable-ip-alias, the default
|
||||
is a VPC-native cluster.
|
||||
|
||||
--enable-k8s-certs-via-dns
|
||||
Enable K8s client certificates Authentication to the cluster's control
|
||||
plane over DNS-based endpoint.
|
||||
|
||||
--enable-k8s-tokens-via-dns
|
||||
Enable K8s Service Account tokens Authentication to the cluster's
|
||||
control plane over DNS-based endpoint.
|
||||
|
||||
--enable-kubernetes-alpha
|
||||
Enable Kubernetes alpha features on this cluster. Selecting this option
|
||||
will result in the cluster having all Kubernetes alpha API groups and
|
||||
|
|
|
|||
|
|
@ -21,7 +21,9 @@ SYNOPSIS
|
|||
[--enable-backup-restore] [--enable-cilium-clusterwide-network-policy]
|
||||
[--enable-confidential-nodes] [--enable-default-compute-class]
|
||||
[--enable-dns-access] [--enable-fleet] [--enable-google-cloud-access]
|
||||
[--enable-ip-access] [--enable-kubernetes-unstable-apis=API,[API,...]]
|
||||
[--enable-ip-access] [--enable-k8s-certs-via-dns]
|
||||
[--enable-k8s-tokens-via-dns]
|
||||
[--enable-kubernetes-unstable-apis=API,[API,...]]
|
||||
[--enable-legacy-lustre-port] [--enable-lustre-csi-driver]
|
||||
[--enable-master-global-access] [--enable-multi-networking]
|
||||
[--enable-ray-cluster-logging] [--enable-ray-cluster-monitoring]
|
||||
|
|
@ -308,6 +310,14 @@ FLAGS
|
|||
Enable access to the cluster's control plane over private IP and public
|
||||
IP if --enable-private-endpoint is not enabled.
|
||||
|
||||
--enable-k8s-certs-via-dns
|
||||
Enable K8s client certificates Authentication to the cluster's control
|
||||
plane over DNS-based endpoint.
|
||||
|
||||
--enable-k8s-tokens-via-dns
|
||||
Enable K8s Service Account tokens Authentication to the cluster's
|
||||
control plane over DNS-based endpoint.
|
||||
|
||||
--enable-kubernetes-unstable-apis=API,[API,...]
|
||||
Enable Kubernetes beta API features on this cluster. Beta APIs are not
|
||||
expected to be production ready and should be avoided in
|
||||
|
|
|
|||
|
|
@ -91,6 +91,7 @@ SYNOPSIS
|
|||
| --enable-l4-lb-firewall-reconciliation
|
||||
| --enable-authorized-networks-on-private-endpoint
|
||||
--enable-dns-access --enable-google-cloud-access --enable-ip-access
|
||||
--enable-k8s-certs-via-dns --enable-k8s-tokens-via-dns
|
||||
--enable-master-global-access --enable-private-endpoint
|
||||
--enable-master-authorized-networks
|
||||
--master-authorized-networks=NETWORK,[NETWORK,...]
|
||||
|
|
@ -1308,6 +1309,14 @@ REQUIRED FLAGS
|
|||
Enable access to the cluster's control plane over private IP and
|
||||
public IP if --enable-private-endpoint is not enabled.
|
||||
|
||||
--enable-k8s-certs-via-dns
|
||||
Enable K8s client certificates Authentication to the cluster's
|
||||
control plane over DNS-based endpoint.
|
||||
|
||||
--enable-k8s-tokens-via-dns
|
||||
Enable K8s Service Account tokens Authentication to the cluster's
|
||||
control plane over DNS-based endpoint.
|
||||
|
||||
--enable-master-global-access
|
||||
Use with private clusters to allow access to the master's private
|
||||
endpoint from any Google Cloud region or on-premises environment
|
||||
|
|
|
|||
|
|
@ -14,6 +14,7 @@ SYNOPSIS
|
|||
[--additional-pod-network=[subnetwork=SUBNETWORK_NAME,
|
||||
pod-ipv4-range=SECONDARY_RANGE_NAME,
|
||||
[max-pods-per-node=NUM_PODS],...]] [--async]
|
||||
[--autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION]]
|
||||
[--boot-disk-kms-key=BOOT_DISK_KMS_KEY]
|
||||
[--boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS]
|
||||
[--boot-disk-provisioned-throughput=BOOT_DISK_PROVISIONED_THROUGHPUT]
|
||||
|
|
@ -183,6 +184,23 @@ FLAGS
|
|||
Return immediately, without waiting for the operation in progress to
|
||||
complete.
|
||||
|
||||
--autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION]
|
||||
Autoscaled rollout policy options for blue-green upgrade.
|
||||
|
||||
wait-for-drain-duration
|
||||
(Optional) Time in seconds to wait after cordoning the blue pool
|
||||
before draining the nodes.
|
||||
|
||||
Examples:
|
||||
|
||||
$ gcloud beta container node-pools create node-pool-1 \
|
||||
--cluster=example-cluster --enable-blue-green-upgrade \
|
||||
--autoscaled-rollout-policy=""
|
||||
|
||||
$ gcloud beta container node-pools create node-pool-1 \
|
||||
--cluster=example-cluster --enable-blue-green-upgrade \
|
||||
--autoscaled-rollout-policy=wait-for-drain-duration=7200s
|
||||
|
||||
--boot-disk-kms-key=BOOT_DISK_KMS_KEY
|
||||
The Customer Managed Encryption Key used to encrypt the boot disk
|
||||
attached to each node in the node pool. This should be of the form
|
||||
|
|
|
|||
|
|
@ -24,11 +24,8 @@ SYNOPSIS
|
|||
| --storage-pools=STORAGE_POOL,[...]
|
||||
| --system-config-from-file=PATH_TO_FILE | --tags=[TAG,...]
|
||||
| --windows-os-version=WINDOWS_OS_VERSION
|
||||
| --workload-metadata=WORKLOAD_METADATA | --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,
|
||||
| --workload-metadata=WORKLOAD_METADATA
|
||||
| --autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION] --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,...]
|
||||
| --boot-disk-provisioned-iops=BOOT_DISK_PROVISIONED_IOPS
|
||||
|
|
@ -762,6 +759,23 @@ REQUIRED FLAGS
|
|||
|
||||
Upgrade settings
|
||||
|
||||
--autoscaled-rollout-policy=[wait-for-drain-duration=WAIT-FOR-DRAIN-DURATION]
|
||||
Autoscaled rollout policy options for blue-green upgrade.
|
||||
|
||||
wait-for-drain-duration
|
||||
(Optional) Time in seconds to wait after cordoning the blue
|
||||
pool before draining the nodes.
|
||||
|
||||
Examples:
|
||||
|
||||
$ gcloud beta container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --enable-blue-green-upgrade \
|
||||
--autoscaled-rollout-policy=""
|
||||
|
||||
$ gcloud beta container node-pools update node-pool-1 \
|
||||
--cluster=example-cluster --enable-blue-green-upgrade \
|
||||
--autoscaled-rollout-policy=wait-for-drain-duration=7200s
|
||||
|
||||
--enable-blue-green-upgrade
|
||||
Changes node pool upgrade strategy to blue-green upgrade.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue