imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 20:36:39 +00:00
Code Activity

gcloud: Tue Jan 20 11:05:01 UTC 2026

Browse source
This commit is contained in:
Automated 2026-01-20 11:05:01 +00:00
parent bdd724fcf3
commit 582f364023
247 changed files with 5698 additions and 1205 deletions
Download patch file Download diff file Expand all files Collapse all files

23
gcloud/container/clusters/create
View file

@ -241,7 +241,7 @@ FLAGS
KubernetesDashboard, NetworkPolicy, NodeLocalDNS, ConfigConnector,
GcePersistentDiskCsiDriver, GcpFilestoreCsiDriver, BackupRestore,
GcsFuseCsiDriver, ParallelstoreCsiDriver, HighScaleCheckpointing,
LustreCsiDriver, RayOperator, CloudRun.
LustreCsiDriver, RayOperator, SlurmOperator, CloudRun.
--alpha-cluster-feature-gates=[FEATURE=true|false,...]
Selectively enable or disable Kubernetes alpha and beta
@ -398,7 +398,7 @@ FLAGS
--confidential-node-type=CONFIDENTIAL_NODE_TYPE
Enable confidential nodes for the cluster. Enabling Confidential Nodes
will create nodes using Confidential VM
https://cloud.google.com/compute/confidential-vm/docs/about-cvm.
https://docs.cloud.google.com/compute/docs/about-confidential-vm.
CONFIDENTIAL_NODE_TYPE must be one of: sev, sev_snp, tdx.
--containerd-config-from-file=PATH_TO_FILE
@ -578,7 +578,7 @@ FLAGS
--enable-confidential-nodes
Enable confidential nodes for the cluster. Enabling Confidential Nodes
will create nodes using Confidential VM
https://cloud.google.com/compute/confidential-vm/docs/about-cvm.
https://docs.cloud.google.com/compute/docs/about-confidential-vm.
--enable-confidential-storage
Enable confidential storage for the cluster. Enabling Confidential
@ -1649,7 +1649,10 @@ FLAGS
[65536,
2147483647]
vm.overcommit_memory Must be one of {0,
1, 2}
1, 2}. Not
supported on
machines with less
than 15 GB memory.
vm.overcommit_ratio Must be between
[0, 100]
vm.vfs_cache_pressure Must be between
@ -1707,9 +1710,15 @@ FLAGS
KEY VALUE
diskCount integer
Allocated hugepage size should not exceed 60% of available memory on
the node. For example, c2d-highcpu-4 has 8GB memory, total allocated
hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB.
The upper limit for total allocated hugepage size differs based upon
machine size.
◆ On machines with less than 30 GB memory: 60% of the total memory.
For example, on e2-standard-2 machine with 8 GB of memory, you can't
allocate more than 4.8 GB for hugepages.
◆ On machines with more than 30 GB memory: 80% of the total memory.
For example, on c4a-standard-8 machines with 32 GB of memory,
hugepages cannot exceed 25.6 GB.
1G hugepages are only available in following machine familes: c3, m2,
c2d, c3d, h3, m3, a2, a3, g2.