1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-18 14:56:05 +00:00

gcloud: Wed Aug 23 10:30:46 UTC 2023

This commit is contained in:
Automated 2023-08-23 10:30:46 +00:00
parent 5f3d6bc974
commit f9edf67fe5
677 changed files with 22815 additions and 975 deletions

View file

@ -0,0 +1,87 @@
NAME
gcloud alpha container fleet clusterupgrade create - create the
clusterupgrade feature for a fleet within a given project
SYNOPSIS
gcloud alpha container fleet clusterupgrade create
[--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING]
[--upstream-fleet=UPSTREAM_FLEET]
[--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
--upgrade-selector=[name=NAME],[version=VERSION]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Create the clusterupgrade feature for a fleet within a given
project.
FLAGS
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
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:
$ gcloud alpha container fleet clusterupgrade create \
--default-upgrade-soaking=7d
--upstream-fleet=UPSTREAM_FLEET
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:
$ gcloud alpha container fleet clusterupgrade create \
--upstream-fleet={upstream_fleet}
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 `--default-upgrade-soaking`.
To set an upgrade soaking override of 12 hours for the upgrade with
name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
$ gcloud alpha container fleet clusterupgrade create \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
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 $ gcloud topic datetimes for information on duration formats.
This flag argument must be specified if any of the other arguments in
this group are specified.
--upgrade-selector=[name=NAME],[version=VERSION]
Name and version of the upgrade to be overridden where version is a
full GKE version. Currently, name can be either k8s_control_plane or
k8s_node.
This flag argument must be specified if any of the other arguments in
this group are specified.
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 $ gcloud help for details.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist.

View file

@ -0,0 +1,46 @@
NAME
gcloud alpha container fleet clusterupgrade describe - describe the
clusterupgrade feature for a fleet within a given project
SYNOPSIS
gcloud alpha container fleet clusterupgrade describe
[--show-linked-cluster-upgrade] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Describe the Fleet clusterupgrade feature used for configuring
fleet-based rollout sequencing.
EXAMPLES
To view the cluster upgrade feature information for the current fleet, run:
$ gcloud alpha container fleet clusterupgrade describe
FLAGS
--show-linked-cluster-upgrade
Shows the cluster upgrade feature information for the current fleet as
well as information for all other fleets linked in the same rollout
sequence (provided that the caller has permission to view the upstream
and downstream fleets). This displays cluster upgrade information for
fleets in the current fleet's rollout sequence in order of furthest
upstream to downstream.
To view the cluster upgrade feature information for the rollout
sequence containing the current fleet, run:
$ gcloud alpha container fleet clusterupgrade describe \
--show-linked-cluster-upgrade
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 $ gcloud help for details.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist.

View file

@ -0,0 +1,37 @@
NAME
gcloud alpha container fleet clusterupgrade - configure the Fleet
clusterupgrade feature
SYNOPSIS
gcloud alpha container fleet clusterupgrade COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This fleet feature is used to configure fleet-based rollout
sequencing.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
create
(ALPHA) Create the clusterupgrade feature for a fleet within a given
project.
describe
(ALPHA) Describe the clusterupgrade feature for a fleet within a given
project.
update
(ALPHA) Update the clusterupgrade feature for a fleet within a given
project.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist.

View file

@ -0,0 +1,115 @@
NAME
gcloud alpha container fleet clusterupgrade update - update the
clusterupgrade feature for a fleet within a given project
SYNOPSIS
gcloud alpha container fleet clusterupgrade update
[--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING]
[--remove-upgrade-soaking-overrides
| --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
--upgrade-selector=[name=NAME],[version=VERSION]]
[--reset-upstream-fleet | --upstream-fleet=UPSTREAM_FLEET]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) Update the clusterupgrade feature for a fleet within a given
project.
FLAGS
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
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:
$ gcloud alpha container fleet clusterupgrade update \
--default-upgrade-soaking=7d
At most one of these can be specified:
--remove-upgrade-soaking-overrides
Removes soaking time overrides for all upgrades propagating through
the current fleet. Consequently, all upgrades will follow the soak
time configured by --default-upgrade-soaking until new overrides are
configured with --add_upgrade_soaking_override and
--upgrade_selector.
To remove all configured soaking time overrides, run:
$ gcloud alpha container fleet clusterupgrade update \
--remove-upgrade-soaking-overrides
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 `--default-upgrade-soaking`.
To set an upgrade soaking override of 12 hours for the upgrade with
name, `k8s_control_plane`, and version, `1.23.1-gke.1000`, run:
$ gcloud alpha container fleet clusterupgrade update \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",\
version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
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 $ gcloud topic datetimes for information on duration formats.
This flag argument must be specified if any of the other arguments
in this group are specified.
--upgrade-selector=[name=NAME],[version=VERSION]
Name and version of the upgrade to be overridden where version is a
full GKE version. Currently, name can be either k8s_control_plane
or k8s_node.
This flag argument must be specified if any of the other arguments
in this group are specified.
At most one of these can be specified:
--reset-upstream-fleet
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:
$ gcloud alpha container fleet clusterupgrade update \
--reset-upstream-fleet
--upstream-fleet=UPSTREAM_FLEET
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:
$ gcloud alpha container fleet clusterupgrade update \
--upstream-fleet={upstream_fleet}
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 $ gcloud help for details.
NOTES
This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct
project, you might be trying to access an API with an invitation-only early
access allowlist.