.TH "GCLOUD_EDGE\-CLOUD_CONTAINER_CLUSTERS_UPDATE" 1



.SH "NAME"
.HP
gcloud edge\-cloud container clusters update \- update an Edge Container cluster



.SH "SYNOPSIS"
.HP
\f5gcloud edge\-cloud container clusters update\fR (\fICLUSTER\fR\ :\ \fB\-\-location\fR=\fILOCATION\fR) [\fB\-\-async\fR] [\fB\-\-container\-default\-runtime\-class\fR=\fICONTAINER_DEFAULT_RUNTIME_CLASS\fR] [\fB\-\-offline\-reboot\-ttl\fR=\fIOFFLINE_REBOOT_TTL\fR] [\fB\-\-release\-channel\fR=\fIRELEASE_CHANNEL\fR] [\fB\-\-clear\-maintenance\-window\fR\ |\ \fB\-\-remove\-maintenance\-exclusion\-window\fR=\fIREMOVE_MAINTENANCE_EXCLUSION_WINDOW\fR\ |\ \fB\-\-add\-maintenance\-exclusion\-end\fR=\fIADD_MAINTENANCE_EXCLUSION_END\fR\ \fB\-\-add\-maintenance\-exclusion\-name\fR=\fIADD_MAINTENANCE_EXCLUSION_NAME\fR\ \fB\-\-add\-maintenance\-exclusion\-start\fR=\fIADD_MAINTENANCE_EXCLUSION_START\fR\ |\ \fB\-\-maintenance\-window\-end\fR=\fIMAINTENANCE_WINDOW_END\fR\ \fB\-\-maintenance\-window\-recurrence\fR=\fIMAINTENANCE_WINDOW_RECURRENCE\fR\ \fB\-\-maintenance\-window\-start\fR=\fIMAINTENANCE_WINDOW_START\fR] [\fB\-\-control\-plane\-kms\-key\fR=\fICONTROL_PLANE_KMS_KEY\fR\ |\ \fB\-\-use\-google\-managed\-key\fR] [\fB\-\-use\-google\-managed\-zone\-key\fR\ |\ \fB\-\-zone\-storage\-kms\-key\fR=\fIZONE_STORAGE_KMS_KEY\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Update an Edge Container cluster.



.SH "EXAMPLES"

To update the maintenance window recurrence rule of a cluster called
\'my\-cluster' in region us\-central1, run:

.RS 2m
$ gcloud edge\-cloud container clusters update my\-cluster \e
    \-\-location=us\-central1 \e
    \-\-maintenance\-window\-recurrence="FREQ=WEEKLY"
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m

Cluster resource \- Edge Container cluster to update. The arguments in this
group can be used to specify the attributes of this resource. (NOTE) Some
attributes are not given arguments in this group but can be set in other ways.

To set the \f5project\fR attribute:
.RS 2m
.IP "\(em" 2m
provide the argument \f5cluster\fR on the command line with a fully specified
name;
.IP "\(em" 2m
provide the argument \f5\-\-project\fR on the command line;
.IP "\(em" 2m
set the property \f5core/project\fR.
.RE
.sp

This must be specified.


.RS 2m
.TP 2m
\fICLUSTER\fR

ID of the cluster or fully qualified identifier for the cluster.

To set the \f5cluster\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5cluster\fR on the command line.
.RE
.sp

This positional argument must be specified if any of the other arguments in this
group are specified.

.TP 2m
\fB\-\-location\fR=\fILOCATION\fR

The global location name.

To set the \f5location\fR attribute:
.RS 2m
.IP "\(bu" 2m
provide the argument \f5cluster\fR on the command line with a fully specified
name;
.IP "\(bu" 2m
provide the argument \f5\-\-location\fR on the command line;
.IP "\(bu" 2m
set the property \f5edge_container/location\fR.
.RE
.sp


.RE
.RE
.sp

.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-async\fR

Return immediately, without waiting for the operation in progress to complete.

.TP 2m
\fB\-\-container\-default\-runtime\-class\fR=\fICONTAINER_DEFAULT_RUNTIME_CLASS\fR

If set, use the specified default container runtime class for the cluster.

.TP 2m
\fB\-\-offline\-reboot\-ttl\fR=\fIOFFLINE_REBOOT_TTL\fR

Specifies the maximum duration a node can reboot offline (without connection to
Google) and then rejoin its cluster to resume its designated workloads. This
duration is relative to the machine's most recent connection to Google. The
maximum allowed duration is 7 days. If left unspecified, the default 0 means not
allowed. The parameter should be an ISO 8601 duration string, for example,
"P1DT1H2M3S".

.TP 2m
\fB\-\-release\-channel\fR=\fIRELEASE_CHANNEL\fR

Release channel a cluster is subscribed to. It supports two values, NONE and
REGULAR. NONE is used to opt out of any release channel. Clusters subscribed to
the REGULAR channel will be automatically upgraded to versions that are
considered GA quality, and cannot be manually upgraded. \fIRELEASE_CHANNEL\fR
must be one of: \fBnone\fR, \fBregular\fR, \fBrelease\-channel\-unspecified\fR.

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-clear\-maintenance\-window\fR

If set, removes the maintenance window setting from the cluster. If any
exclusion windows exist, they must be removed beforehand as a maintenance policy
cannot exist without a maintenance window.

.TP 2m
\fB\-\-remove\-maintenance\-exclusion\-window\fR=\fIREMOVE_MAINTENANCE_EXCLUSION_WINDOW\fR

Name of the maintenance exclusion to remove.

.TP 2m

Add a maintenance exclusion window (all flags must be specified to add a valid
maintenance exclusion window). There can be a maximum of 3 exclusion windows set
at a given time. A maintenance exclusion window cannot be added in the absence
of a maintenance window.


.RS 2m
.TP 2m
\fB\-\-add\-maintenance\-exclusion\-end\fR=\fIADD_MAINTENANCE_EXCLUSION_END\fR

End time of the maintenance exclusion window in the RFC 3339
(https://www.rfc\-editor.org/rfc/rfc3339.txt) format. E.g.
"2021\-01\-01T00:00:00Z" or "2021\-01\-01T00:00:00\-05:00".

.TP 2m
\fB\-\-add\-maintenance\-exclusion\-name\fR=\fIADD_MAINTENANCE_EXCLUSION_NAME\fR

Unique name (per cluster) of the maintenance exclusion window that can be used
to remove it.

.TP 2m
\fB\-\-add\-maintenance\-exclusion\-start\fR=\fIADD_MAINTENANCE_EXCLUSION_START\fR

Start time of the maintenance exclusion window (can occur in the past) in the
RFC 3339 (https://www.rfc\-editor.org/rfc/rfc3339.txt) format. E.g.
"2021\-01\-01T00:00:00Z" or "2021\-01\-01T00:00:00\-05:00".

.RE
.sp
.TP 2m

Updates cluster maintenance window setting (more than one flags can be specified
from this group)


.RS 2m
.TP 2m
\fB\-\-maintenance\-window\-end\fR=\fIMAINTENANCE_WINDOW_END\fR

End time of the recurring cluster maintenance window in the RFC 3339
(https://www.rfc\-editor.org/rfc/rfc3339.txt) format. E.g.
"2021\-01\-01T00:00:00Z" or "2021\-01\-01T00:00:00\-05:00"

.TP 2m
\fB\-\-maintenance\-window\-recurrence\fR=\fIMAINTENANCE_WINDOW_RECURRENCE\fR

An RFC 5545 (https://tools.ietf.org/html/rfc5545#section\-3.8.5.3) recurrence
rule for how the cluster maintenance window recurs. They go on for the span of
time between the start and the end time. E.g. FREQ=WEEKLY;BYDAY=SU.

.TP 2m
\fB\-\-maintenance\-window\-start\fR=\fIMAINTENANCE_WINDOW_START\fR

Start time of the recurring cluster maintenance window in the RFC 3339
(https://www.rfc\-editor.org/rfc/rfc3339.txt) format. E.g.
"2021\-01\-01T00:00:00Z" or "2021\-01\-01T00:00:00\-05:00"

.RE
.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-control\-plane\-kms\-key\fR=\fICONTROL_PLANE_KMS_KEY\fR

If set, use the specified KMS key for the cluster control plane nodes
encryption.

.TP 2m
\fB\-\-use\-google\-managed\-key\fR

If set, use Google managed key for the cluster control plane nodes encryption.

.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-use\-google\-managed\-zone\-key\fR

If set, use Google managed key for zone storage encryption.

.TP 2m
\fB\-\-zone\-storage\-kms\-key\fR=\fIZONE_STORAGE_KMS_KEY\fR

If set, use the specified KMS key for zone storage encryption.


.RE
.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "API REFERENCE"

This command uses the \fBedgecontainer/v1\fR API. The full documentation for
this API can be found at: https://cloud.google.com/edge\-cloud



.SH "NOTES"

This variant is also available:

.RS 2m
$ gcloud alpha edge\-cloud container clusters update
.RE