.TH "GCLOUD_CONTAINER_FLEET_CLUSTERUPGRADE_UPDATE" 1



.SH "NAME"
.HP
gcloud container fleet clusterupgrade update \- update the clusterupgrade feature for a fleet within a given project



.SH "SYNOPSIS"
.HP
\f5gcloud container fleet clusterupgrade update\fR [\fB\-\-default\-upgrade\-soaking\fR=\fIDEFAULT_UPGRADE_SOAKING\fR] [\fB\-\-remove\-upgrade\-soaking\-overrides\fR\ |\ \fB\-\-add\-upgrade\-soaking\-override\fR=\fIADD_UPGRADE_SOAKING_OVERRIDE\fR\ \fB\-\-upgrade\-selector\fR=[\fIname\fR=\fINAME\fR],[\fIversion\fR=\fIVERSION\fR]] [\fB\-\-reset\-upstream\-fleet\fR\ |\ \fB\-\-upstream\-fleet\fR=\fIUPSTREAM_FLEET\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

Update the clusterupgrade feature for a fleet within a given project.



.SH "EXAMPLES"

To update the clusterupgrade feature for the current fleet, run:

.RS 2m
$ gcloud container fleet clusterupgrade update \e
    \-\-default\-upgrade\-soaking=DEFAULT_UPGRADE_SOAKING
.RE



.SH "FLAGS"

.RS 2m
.TP 2m
\fB\-\-default\-upgrade\-soaking\fR=\fIDEFAULT_UPGRADE_SOAKING\fR

Note: This flag only applies to Rollout Sequencing v1, not Rollout Sequencing v2
(which uses custom stages). If using Rollout Sequencing v1 and this flag is not
provided, a default value of 7 days will be used.

Configures the default soaking duration for each upgrade propagating through the
current fleet to become "COMPLETE". Soaking begins after all clusters in the
fleet are on the target version, or after 30 days if all cluster upgrades are
not complete. Once an upgrade state becomes "COMPLETE", it will automatically be
propagated to the downstream fleet. Max is 30 days.

To configure Rollout Sequencing for a fleet, this attribute must be set. To do
this while specifying a default soaking duration of 7 days, run:

.RS 2m
$ gcloud container fleet clusterupgrade update \e
    \-\-default\-upgrade\-soaking=7d
.RE

.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-remove\-upgrade\-soaking\-overrides\fR

Removes soaking time overrides for all upgrades propagating through the current
fleet. Consequently, all upgrades will follow the soak time configured by
\f5\-\-default\-upgrade\-soaking\fR until new overrides are configured with
\f5\-\-add_upgrade_soaking_override\fR and \f5\-\-upgrade_selector\fR.

To remove all configured soaking time overrides, run:

.RS 2m
$ gcloud container fleet clusterupgrade update \e
    \-\-remove\-upgrade\-soaking\-overrides
.RE

.TP 2m

Upgrade soaking override.

Defines a specific soaking time override for a particular upgrade propagating
through the current fleet that supercedes the default soaking duration
configured by \f5\-\-default\-upgrade\-soaking\fR.

To set an upgrade soaking override of 12 hours for the upgrade with name,
\f5k8s_control_plane\fR, and version, \f51.23.1\-gke.1000\fR, run:

.RS 2m
$ gcloud container fleet clusterupgrade update               \e
    \-\-add\-upgrade\-soaking\-override=12h               \e
    \-\-upgrade\-selector=name="k8s_control_plane",\e
version="1.23.1\-gke.1000"
.RE



.RS 2m
.TP 2m
\fB\-\-add\-upgrade\-soaking\-override\fR=\fIADD_UPGRADE_SOAKING_OVERRIDE\fR

Overrides the soaking time for a particular upgrade name and version propagating
through the current fleet. Set soaking to 0 days to bypass soaking and
fast\-forward the upgrade to the downstream fleet.

See \f5$ gcloud topic datetimes\fR for information on duration formats.

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

.TP 2m
\fB\-\-upgrade\-selector\fR=[\fIname\fR=\fINAME\fR],[\fIversion\fR=\fIVERSION\fR]

Name and version of the upgrade to be overridden where version is a full GKE
version. Currently, name can be either \f5k8s_control_plane\fR or
\f5k8s_node\fR.

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

.RE
.RE
.sp
.TP 2m

At most one of these can be specified:


.RS 2m
.TP 2m
\fB\-\-reset\-upstream\-fleet\fR

Clears the relationship between the current fleet and its upstream fleet in the
rollout sequence.

To remove the link between the current fleet and its upstream fleet, run:

.RS 2m
$ gcloud container fleet clusterupgrade update \-\-reset\-upstream\-fleet
.RE

.TP 2m
\fB\-\-upstream\-fleet\fR=\fIUPSTREAM_FLEET\fR

The upstream fleet. GKE will finish upgrades on the upstream fleet before
applying the same upgrades to the current fleet.

To configure the upstream fleet, run:

.RS 2m
$ gcloud container fleet clusterupgrade update             \e
    \-\-upstream\-fleet={upstream_fleet}
.RE


.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 "NOTES"

These variants are also available:

.RS 2m
$ gcloud alpha container fleet clusterupgrade update
.RE

.RS 2m
$ gcloud beta container fleet clusterupgrade update
.RE