imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-17 14:26:34 +00:00
Code Activity

gcloud: Wed Mar 5 10:41:25 UTC 2025

Browse source
This commit is contained in:
Automated 2025-03-05 10:41:25 +00:00
parent a597993b2e
commit 6dc93282df
279 changed files with 4198 additions and 801 deletions
Download patch file Download diff file Expand all files Collapse all files

19
gcloud/beta/container/clusters/create
View file

@ -977,7 +977,7 @@ FLAGS
Set the components that have monitoring enabled. Valid component values
are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM
STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM, JOBSET
For more information, see
https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics
@ -1055,7 +1055,7 @@ FLAGS
on how to manage Pub/Sub topics and subscriptions. You can also use the
filter option to specify which event types you'd like to receive from
the following options: SecurityBulletinEvent, UpgradeEvent,
UpgradeAvailableEvent.
UpgradeInfoEvent, UpgradeAvailableEvent.
Examples:
@ -2237,10 +2237,17 @@ FLAGS
--maintenance-window-recurrence=FREQ=DAILY
--maintenance-window-end=TIME_STAMP
End time of the first window (can occur in the past). Must take
place after the start time. The difference in start and end time
specifies the length of each recurrence. See $ gcloud topic
datetimes for information on time formats.
The end time for calculating the duration of the maintenance
window, as expressed by the amount of time after the START_TIME, in
the same format. The value for END_TIME must be in the future,
relative to START_TIME. This only calculates the duration of the
window, and doesn't set when the maintenance window stops
recurring. Maintenance windows only stop recurring when they're
removed. See $ gcloud topic datetimes for information on time
formats.
This flag argument must be specified if any of the other arguments
in this group are specified.
This flag argument must be specified if any of the other arguments
in this group are specified.

2
gcloud/beta/container/clusters/create-auto
View file

@ -349,7 +349,7 @@ FLAGS
Set the components that have monitoring enabled. Valid component values
are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM
STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM, JOBSET
For more information, see
https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics

31
gcloud/beta/container/clusters/update
View file

@ -13,7 +13,9 @@ SYNOPSIS
| --containerd-config-from-file=PATH_TO_FILE
| --database-encryption-key=DATABASE_ENCRYPTION_KEY
| --disable-database-encryption | --disable-default-snat
| --disable-workload-identity | --enable-autoscaling
| --disable-workload-identity
| --[no-]enable-autopilot-compatibility-auditing
| --enable-autoscaling
| --[no-]enable-cilium-clusterwide-network-policy
| --enable-cost-allocation | --enable-fleet
| --enable-fqdn-network-policy | --enable-gke-oidc
@ -306,6 +308,13 @@ REQUIRED FLAGS
https://cloud.google.com/kubernetes-engine/docs/how-to/workload-identity
--[no-]enable-autopilot-compatibility-auditing
Enables the Autopilot Compatibility Auditing Feature. See
https://cloud.google.com/sdk/gcloud/reference/container/clusters/check-autopilot-compatibility.
Only applicable to clusters with version >= 1.32. Use
--enable-autopilot-compatibility-auditing to enable and
--no-enable-autopilot-compatibility-auditing to disable.
--enable-autoscaling
Enables autoscaling for a node pool.
@ -578,7 +587,8 @@ REQUIRED FLAGS
https://cloud.google.com/pubsub/docs/admin on how to manage Pub/Sub
topics and subscriptions. You can also use the filter option to
specify which event types you'd like to receive from the following
options: SecurityBulletinEvent, UpgradeEvent, UpgradeAvailableEvent.
options: SecurityBulletinEvent, UpgradeEvent, UpgradeInfoEvent,
UpgradeAvailableEvent.
Examples:
@ -898,7 +908,7 @@ REQUIRED FLAGS
Set the components that have monitoring enabled. Valid component
values are: SYSTEM, WORKLOAD (Deprecated), NONE, API_SERVER,
CONTROLLER_MANAGER, SCHEDULER, DAEMONSET, DEPLOYMENT, HPA, POD,
STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM
STATEFULSET, STORAGE, CADVISOR, KUBELET, DCGM, JOBSET
For more information, see
https://cloud.google.com/kubernetes-engine/docs/how-to/configure-metrics#available-metrics
@ -1015,10 +1025,17 @@ REQUIRED FLAGS
--maintenance-window-recurrence=FREQ=DAILY
--maintenance-window-end=TIME_STAMP
End time of the first window (can occur in the past). Must take
place after the start time. The difference in start and end time
specifies the length of each recurrence. See $ gcloud topic
datetimes for information on time formats.
The end time for calculating the duration of the maintenance
window, as expressed by the amount of time after the START_TIME,
in the same format. The value for END_TIME must be in the future,
relative to START_TIME. This only calculates the duration of the
window, and doesn't set when the maintenance window stops
recurring. Maintenance windows only stop recurring when they're
removed. See $ gcloud topic datetimes for information on time
formats.
This flag argument must be specified if any of the other
arguments in this group are specified.
This flag argument must be specified if any of the other
arguments in this group are specified.