imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-13 00:18:35 +00:00
Code Activity

gcloud: Wed Mar 23 08:27:29 UTC 2022

Browse source
This commit is contained in:
Automated 2022-03-23 08:27:29 +00:00
parent 971306823a
commit cd34e797ae
109 changed files with 1563 additions and 627 deletions
Download patch file Download diff file Expand all files Collapse all files

14
gcloud/beta/auth/application-default/print-access-token
View file

@ -43,15 +43,15 @@ DESCRIPTION
FLAGS
--scopes=SCOPE,[SCOPE,...]
The scopes to authorize for. By default
[https://www.googleapis.com/auth/cloud-platform] scopes are used. The
list of possible scopes can be found at:
The scopes to authorize for. This flag is supported for user accounts
and service accounts only. The list of possible scopes can be found at:
https://developers.google.com/identity/protocols/googlescopes.
This flag is not for end-user accounts. The scopes of end-user
credentials cannot change after authorization. To request a different
set of scopes for end-user accounts, rerun gcloud auth
application-default login --scopes.
For end-user accounts, the provided scopes must be from ['openid',
'https://www.googleapis.com/auth/userinfo.email',
'https://www.googleapis.com/auth/cloud-platform'], or the scopes
previously specified through gcloud auth application-default login
--scopes.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

16
gcloud/beta/auth/help
View file

@ -6,15 +6,21 @@ SYNOPSIS
DESCRIPTION
(BETA) The gcloud auth command group lets you grant and revoke
authorization to Google Cloud CLI (gcloud) to access Google Cloud.
authorization to Google Cloud CLI (gcloud CLI) to access Google Cloud.
Typically, when scripting Google Cloud CLI tools for use on multiple
machines, using gcloud auth activate-service-account is recommended.
For more information on authorization and credential types, see:
https://cloud.google.com/sdk/docs/authorizing.
For information about authorization and credential types, see Authorizing
the gcloud CLI (https://cloud.google.com/sdk/docs/authorizing). For
information about authorizing a service account, see Authorizing with a
service account
(https://cloud.google.com/sdk/docs/authorizing#authorizing_with_a_service_account).
While running gcloud auth commands, the --account flag can be specified to
any command to use that account without activation.
After running gcloud auth commands, you can run other commands with
--account=ACCOUNT to authenticate the command with the credentials of the
specified account. For information about --account and other gcloud CLI
global flags, see the gcloud CLI overview
(https://cloud.google.com/sdk/gcloud/reference).
EXAMPLES
To authenticate a user account with gcloud and minimal user output, run:

11
gcloud/beta/compute/backend-services/create
View file

@ -25,6 +25,7 @@ SYNOPSIS
oauth2-client-secret=OAUTH2-CLIENT-SECRET]]
[--idle-timeout-sec=IDLE_TIMEOUT_SEC]
[--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"]
[--locality-lb-policy=LOCALITY_LB_POLICY]
[--logging-sample-rate=LOGGING_SAMPLE_RATE] [--max-ttl=MAX_TTL]
[--[no-]negative-caching] [--negative-caching-policy=[[CODE=TTL],...]]
[--network=NETWORK] [--port-name=PORT_NAME] [--protocol=PROTOCOL]
@ -306,7 +307,9 @@ FLAGS
--idle-timeout-sec=IDLE_TIMEOUT_SEC
Specifies how long to keep a connection tracking table entry while
there is no matching traffic (in seconds).
there is no matching traffic (in seconds). Applicable only for backend
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"
Specifies the load balancer type. Choose EXTERNAL for load balancers
@ -319,6 +322,12 @@ FLAGS
LOAD_BALANCING_SCHEME must be one of: INTERNAL, EXTERNAL,
INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, INTERNAL_MANAGED.
--locality-lb-policy=LOCALITY_LB_POLICY
The load balancing algorithm used within the scope of the locality.
LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN,
LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV,
WEIGHTED_MAGLEV.
--logging-sample-rate=LOGGING_SAMPLE_RATE
This field can only be specified if logging is enabled for the backend
service. The value of the field must be a float in the range [0, 1].

11
gcloud/beta/compute/backend-services/update
View file

@ -20,6 +20,7 @@ SYNOPSIS
[--iap=disabled|enabled,[oauth2-client-id=OAUTH2-CLIENT-ID,
oauth2-client-secret=OAUTH2-CLIENT-SECRET]]
[--idle-timeout-sec=IDLE_TIMEOUT_SEC]
[--locality-lb-policy=LOCALITY_LB_POLICY]
[--logging-sample-rate=LOGGING_SAMPLE_RATE] [--port-name=PORT_NAME]
[--protocol=PROTOCOL] [--[no-]request-coalescing]
[--security-policy=SECURITY_POLICY]
@ -224,7 +225,15 @@ FLAGS
--idle-timeout-sec=IDLE_TIMEOUT_SEC
Specifies how long to keep a connection tracking table entry while
there is no matching traffic (in seconds).
there is no matching traffic (in seconds). Applicable only for backend
service-based network load balancers and internal TCP/UDP load
balancers as part of a connection tracking policy.
--locality-lb-policy=LOCALITY_LB_POLICY
The load balancing algorithm used within the scope of the locality.
LOCALITY_LB_POLICY must be one of: INVALID_LB_POLICY, ROUND_ROBIN,
LEAST_REQUEST, RING_HASH, RANDOM, ORIGINAL_DESTINATION, MAGLEV,
WEIGHTED_MAGLEV.
--logging-sample-rate=LOGGING_SAMPLE_RATE
This field can only be specified if logging is enabled for the backend

6
gcloud/beta/compute/instances/create
View file

@ -29,7 +29,7 @@ SYNOPSIS
[--min-cpu-platform=PLATFORM] [--min-node-cpu=MIN_NODE_CPU]
[--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]]
[--network-performance-configs=[PROPERTY=VALUE,...]]
[--network-tier=NETWORK_TIER]
[--network-tier=NETWORK_TIER] [--node-project=NODE_PROJECT]
[--post-key-revocation-action-type=POLICY] [--preemptible]
[--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE]
[--private-network-ip=PRIVATE_NETWORK_IP]
@ -631,6 +631,10 @@ FLAGS
NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The
default value is PREMIUM.
--node-project=NODE_PROJECT
The name of the project with shared sole tenant node groups to create
an instance in.
--post-key-revocation-action-type=POLICY
Specifies the behavior of the instance when the KMS key of one of its
attached disks is revoked. The default is noop. POLICY must be one of:

6
gcloud/beta/compute/instances/resume
View file

@ -67,8 +67,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute instances resume
$ gcloud alpha compute instances resume

15
gcloud/beta/compute/instances/suspend
View file

@ -13,12 +13,11 @@ DESCRIPTION
while it is in the RUNNING state. A suspended instance will be put in
SUSPENDED state.
Note: A suspended instance can be resumed by running the gcloud beta
compute instances resume command.
Note: A suspended instance can be resumed by running the gcloud compute
instances resume command.
Beta restrictions: Suspending a Preemptible VM is not supported and will
result in an API error. Suspending a VM that is using CSEK or GPUs is not
supported and will result in an API error.
Limitations: See this feature's restrictions at
https://cloud.google.com/compute/docs/instances/suspend-resume-instance#limitations
EXAMPLES
To suspend an instance named test-instance, run:
@ -72,8 +71,10 @@ GCLOUD WIDE FLAGS
Run $ gcloud help for details.
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud compute instances suspend
$ gcloud alpha compute instances suspend

5
gcloud/beta/compute/network-endpoint-groups/create
View file

@ -56,7 +56,7 @@ FLAGS
network is used if unspecified.
This is only supported for NEGs with endpoint type gce-vm-ip-port,
non-gcp-private-ip-port, or gce-vm-ip.
non-gcp-private-ip-port, gce-vm-ip, or private-service-connect.
--network-endpoint-type=NETWORK_ENDPOINT_TYPE; default="gce-vm-ip-port"
Determines the spec of endpoints attached to this group.
@ -104,8 +104,7 @@ FLAGS
private-service-connect
The network endpoint corresponds to a service outside the VPC,
accessed via Private Service Connect. The network, subnet, and
default port must not be set.
accessed via Private Service Connect.
NETWORK_ENDPOINT_TYPE must be one of: gce-vm-ip-port,
internet-ip-port, internet-fqdn-port, non-gcp-private-ip-port,

17
gcloud/beta/compute/sole-tenancy/node-groups/create
View file

@ -8,7 +8,9 @@ SYNOPSIS
[--description=DESCRIPTION] [--maintenance-policy=MAINTENANCE_POLICY]
[--maintenance-window-start-time=START_TIME] [--zone=ZONE]
[--autoscaler-mode=AUTOSCALER_MODE
: --max-nodes=MAX_NODES --min-nodes=MIN_NODES] [GCLOUD_WIDE_FLAG ...]
: --max-nodes=MAX_NODES --min-nodes=MIN_NODES]
[--share-setting=SHARE_SETTING : --share-with=PROJECT,[PROJECT,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Create a Compute Engine node group.
@ -100,6 +102,19 @@ OPTIONAL FLAGS
The minimum size of the node group. Default is 0 and must be an
integer value smaller than or equal to --max-nodes.
Manage the properties of a shared setting
--share-setting=SHARE_SETTING
Specify if this node group is shared; and if so, the type of sharing:
share with specific projects or folders. SHARE_SETTING must be one
of: projects, organization, local.
This flag must be specified if any of the other arguments in this
group are specified.
--share-with=PROJECT,[PROJECT,...]
A list of specific projects this node group should be shared with.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

10
gcloud/beta/compute/sole-tenancy/node-groups/list
View file

@ -3,9 +3,9 @@ NAME
Engine node groups
SYNOPSIS
gcloud beta compute sole-tenancy node-groups list [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
gcloud beta compute sole-tenancy node-groups list [--share-settings]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta compute sole-tenancy node-groups list displays all
@ -28,6 +28,10 @@ EXAMPLES
$ gcloud beta compute sole-tenancy node-groups list \
--filter="region:( us-central1 europe-west1 )"
FLAGS
--share-settings
If provided, shows details for the share setting
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.

17
gcloud/beta/compute/sole-tenancy/node-groups/update
View file

@ -7,7 +7,9 @@ SYNOPSIS
[--node-template=NODE_TEMPLATE] [--zone=ZONE]
[--add-nodes=ADD_NODES | --delete-nodes=[NODE,...]]
[--autoscaler-mode=AUTOSCALER_MODE
--max-nodes=MAX_NODES --min-nodes=MIN_NODES] [GCLOUD_WIDE_FLAG ...]
--max-nodes=MAX_NODES --min-nodes=MIN_NODES]
[--share-setting=SHARE_SETTING : --share-with=PROJECT,[PROJECT,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Compute Engine node group.
@ -77,6 +79,19 @@ FLAGS
The minimum size of the node group. Default is 0 and must be an
integer value smaller than or equal to --max-nodes.
Manage the properties of a shared setting
--share-setting=SHARE_SETTING
Specify if this node group is shared; and if so, the type of sharing:
share with specific projects or folders. SHARE_SETTING must be one
of: projects, organization, local.
This flag must be specified if any of the other arguments in this
group are specified.
--share-with=PROJECT,[PROJECT,...]
A list of specific projects this node group should be shared with.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

24
gcloud/beta/compute/url-maps/validate
View file

@ -2,7 +2,8 @@ NAME
gcloud beta compute url-maps validate - validate a URL map
SYNOPSIS
gcloud beta compute url-maps validate [--source=SOURCE]
gcloud beta compute url-maps validate
[--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--source=SOURCE]
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -16,6 +17,27 @@ EXAMPLES
$ gcloud beta compute url-maps validate --source=<path-to-file>
FLAGS
--load-balancing-scheme=LOAD_BALANCING_SCHEME
Specifies the load balancer type(s) this validation request is for. Use
EXTERNAL_MANAGED for HTTP/HTTPS External Global Load Balancer with
Advanced Traffic Management. Use EXTERNAL for Classic HTTP/HTTPS
External Global Load Balancer.
Other load balancer types are not supported. For more information,
refer to Choosing a load balancer
(https://cloud.google.com/load-balancing/docs/choosing-load-balancer/).
If unspecified, the load balancing scheme will be inferred from the
backend service resources this URL map references. If that can not be
inferred (for example, this URL map only references backend buckets, or
this URL map is for rewrites and redirects only and doesn't reference
any backends), EXTERNAL will be used as the default type.
If specified, the scheme must not conflict with the load balancing
scheme of the backend service resources this URL map references.
LOAD_BALANCING_SCHEME must be one of: EXTERNAL, EXTERNAL_MANAGED.
--source=SOURCE
Path to a YAML file containing configuration export data. The YAML file
must not contain any output-only fields. Alternatively, you may omit

10
gcloud/beta/config/get
View file

@ -619,11 +619,11 @@ AVAILABLE PROPERTIES
context_aware
use_client_certificate
If True, use client certificate to authorize user device using
Context-aware access. Some services may not support client
certificate authorization. If a command sends requests to such
services, the client certificate will not be validated. Run gcloud
topic client-certificate for list of services supporting this
feature.
Context-aware access. This includes user login as well. Some
services may not support client certificate authorization. If a
command sends requests to such services, the client certificate
will not be validated. Run gcloud topic client-certificate for list
of services supporting this feature.
dataflow
disable_public_ips

10
gcloud/beta/config/help
View file

@ -651,11 +651,11 @@ AVAILABLE PROPERTIES
context_aware
use_client_certificate
If True, use client certificate to authorize user device using
Context-aware access. Some services may not support client
certificate authorization. If a command sends requests to such
services, the client certificate will not be validated. Run gcloud
topic client-certificate for list of services supporting this
feature.
Context-aware access. This includes user login as well. Some
services may not support client certificate authorization. If a
command sends requests to such services, the client certificate
will not be validated. Run gcloud topic client-certificate for list
of services supporting this feature.
dataflow
disable_public_ips

10
gcloud/beta/config/list
View file

@ -653,11 +653,11 @@ AVAILABLE PROPERTIES
context_aware
use_client_certificate
If True, use client certificate to authorize user device using
Context-aware access. Some services may not support client
certificate authorization. If a command sends requests to such
services, the client certificate will not be validated. Run gcloud
topic client-certificate for list of services supporting this
feature.
Context-aware access. This includes user login as well. Some
services may not support client certificate authorization. If a
command sends requests to such services, the client certificate
will not be validated. Run gcloud topic client-certificate for list
of services supporting this feature.
dataflow
disable_public_ips

10
gcloud/beta/config/set
View file

@ -666,11 +666,11 @@ AVAILABLE PROPERTIES
context_aware
use_client_certificate
If True, use client certificate to authorize user device using
Context-aware access. Some services may not support client
certificate authorization. If a command sends requests to such
services, the client certificate will not be validated. Run gcloud
topic client-certificate for list of services supporting this
feature.
Context-aware access. This includes user login as well. Some
services may not support client certificate authorization. If a
command sends requests to such services, the client certificate
will not be validated. Run gcloud topic client-certificate for list
of services supporting this feature.
dataflow
disable_public_ips

10
gcloud/beta/config/unset
View file

@ -627,11 +627,11 @@ AVAILABLE PROPERTIES
context_aware
use_client_certificate
If True, use client certificate to authorize user device using
Context-aware access. Some services may not support client
certificate authorization. If a command sends requests to such
services, the client certificate will not be validated. Run gcloud
topic client-certificate for list of services supporting this
feature.
Context-aware access. This includes user login as well. Some
services may not support client certificate authorization. If a
command sends requests to such services, the client certificate
will not be validated. Run gcloud topic client-certificate for list
of services supporting this feature.
dataflow
disable_public_ips

118
gcloud/beta/container/fleet/memberships/generate-gateway-rbac Normal file
View file

@ -0,0 +1,118 @@
NAME
gcloud beta container fleet memberships generate-gateway-rbac - generate
RBAC policy files for connected clusters by the user
SYNOPSIS
gcloud beta container fleet memberships generate-gateway-rbac
[--anthos-support] [--apply] [--context=CONTEXT]
[--kubeconfig=KUBECONFIG] [--membership=MEMBERSHIP]
[--rbac-output-file=RBAC_OUTPUT_FILE] [--revoke] [--role=ROLE]
[--users=USERS] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta container fleet memberships generate-gateway-rbac
generates RBAC policies to be used by Connect Gateway API.
Upon success, this command will write the output RBAC policy to the
designated local file in dry run mode.
Override RBAC policy: Y to override previous RBAC policy, N to stop. If
overriding the --role, Y will clean up the previous RBAC policy and then
apply the new one.
EXAMPLES
The current implementation supports multiple modes:
Dry run mode to generate the RBAC policy file, and write to local
directory:
$ gcloud beta container fleet memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin --rbac-output-file=./rbac.yaml
Dry run mode to generate the RBAC policy, and print on screen:
$ gcloud beta container fleet memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin
Anthos support mode, generate the RBAC policy file with read-only
permission for TSE/Eng to debug customers' clusters:
$ gcloud beta container fleet memberships generate-gateway-rbac \
--membership=my-cluster --anthos-support
Apply mode, generate the RBAC policy and apply it to the specified cluster:
$ gcloud beta container fleet memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin --context=my-cluster-contex \
--kubeconfig=/home/user/custom_kubeconfig --apply
Revoke mode, revoke the RBAC policy for the specified users:
$ gcloud beta container fleet memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin --context=my-cluster-contex \
--kubeconfig=/home/user/custom_kubeconfig --apply
FLAGS
--anthos-support
If specified, this command will generate RBAC policy file for anthos
support.
--apply
If specified, this command will generate RBAC policy and apply to the
specified cluster.
--context=CONTEXT
The cluster context as it appears in the kubeconfig file. You can get
this value from the command line by running command: kubectl config
current-context.
--kubeconfig=KUBECONFIG
The kubeconfig file containing an entry for the cluster. Defaults to
$KUBECONFIG if it is set in the environment, otherwise defaults to
$HOME/.kube/config.
--membership=MEMBERSHIP
Membership name to assign RBAC policy with.
--rbac-output-file=RBAC_OUTPUT_FILE
If specified, this command will execute in dry run mode and write to
the file specified with this flag: the generated RBAC policy will not
be applied to Kubernetes clusters,instead it will be written to the
designated local file.
--revoke
If specified, this command will revoke the RBAC policy for the
specified users.
--role=ROLE
Namespace scoped role or cluster role.
--users=USERS
User's email address or service account email address.
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha container fleet memberships generate-gateway-rbac

3
gcloud/beta/container/fleet/memberships/help
View file

@ -23,6 +23,9 @@ COMMANDS
describe
(BETA) Describe a membership.
generate-gateway-rbac
(BETA) Generate RBAC policy files for connected clusters by the user.
get-credentials
(BETA) Fetch credentials for a Fleet-registered cluster to be used in
Connect Gateway.

118
gcloud/beta/container/hub/memberships/generate-gateway-rbac Normal file
View file

@ -0,0 +1,118 @@
NAME
gcloud beta container hub memberships generate-gateway-rbac - generate RBAC
policy files for connected clusters by the user
SYNOPSIS
gcloud beta container hub memberships generate-gateway-rbac
[--anthos-support] [--apply] [--context=CONTEXT]
[--kubeconfig=KUBECONFIG] [--membership=MEMBERSHIP]
[--rbac-output-file=RBAC_OUTPUT_FILE] [--revoke] [--role=ROLE]
[--users=USERS] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) gcloud beta container hub memberships generate-gateway-rbac
generates RBAC policies to be used by Connect Gateway API.
Upon success, this command will write the output RBAC policy to the
designated local file in dry run mode.
Override RBAC policy: Y to override previous RBAC policy, N to stop. If
overriding the --role, Y will clean up the previous RBAC policy and then
apply the new one.
EXAMPLES
The current implementation supports multiple modes:
Dry run mode to generate the RBAC policy file, and write to local
directory:
$ gcloud beta container hub memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin --rbac-output-file=./rbac.yaml
Dry run mode to generate the RBAC policy, and print on screen:
$ gcloud beta container hub memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin
Anthos support mode, generate the RBAC policy file with read-only
permission for TSE/Eng to debug customers' clusters:
$ gcloud beta container hub memberships generate-gateway-rbac \
--membership=my-cluster --anthos-support
Apply mode, generate the RBAC policy and apply it to the specified cluster:
$ gcloud beta container hub memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin --context=my-cluster-contex \
--kubeconfig=/home/user/custom_kubeconfig --apply
Revoke mode, revoke the RBAC policy for the specified users:
$ gcloud beta container hub memberships generate-gateway-rbac \
--membership=my-cluster \
--users=foo@example.com,\
test-acct@test-project.iam.gserviceaccount.com \
--role=clusterrole/cluster-admin --context=my-cluster-contex \
--kubeconfig=/home/user/custom_kubeconfig --apply
FLAGS
--anthos-support
If specified, this command will generate RBAC policy file for anthos
support.
--apply
If specified, this command will generate RBAC policy and apply to the
specified cluster.
--context=CONTEXT
The cluster context as it appears in the kubeconfig file. You can get
this value from the command line by running command: kubectl config
current-context.
--kubeconfig=KUBECONFIG
The kubeconfig file containing an entry for the cluster. Defaults to
$KUBECONFIG if it is set in the environment, otherwise defaults to
$HOME/.kube/config.
--membership=MEMBERSHIP
Membership name to assign RBAC policy with.
--rbac-output-file=RBAC_OUTPUT_FILE
If specified, this command will execute in dry run mode and write to
the file specified with this flag: the generated RBAC policy will not
be applied to Kubernetes clusters,instead it will be written to the
designated local file.
--revoke
If specified, this command will revoke the RBAC policy for the
specified users.
--role=ROLE
Namespace scoped role or cluster role.
--users=USERS
User's email address or service account email address.
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 beta and might change without notice. This
variant is also available:
$ gcloud alpha container hub memberships generate-gateway-rbac

3
gcloud/beta/container/hub/memberships/help
View file

@ -23,6 +23,9 @@ COMMANDS
describe
(BETA) Describe a membership.
generate-gateway-rbac
(BETA) Generate RBAC policy files for connected clusters by the user.
get-credentials
(BETA) Fetch credentials for a Fleet-registered cluster to be used in
Connect Gateway.

4
gcloud/beta/functions/deploy
View file

@ -153,14 +153,14 @@ FLAGS
◆ nodejs10: Node.js 10
◆ nodejs12: Node.js 12
◆ nodejs14: Node.js 14
◆ nodejs16: Node.js 16 (preview)
◆ nodejs16: Node.js 16
◆ php74: PHP 7.4
◆ python37: Python 3.7
◆ python38: Python 3.8
◆ python39: Python 3.9
◆ go111: Go 1.11
◆ go113: Go 1.13
◆ go116: Go 1.16 (preview)
◆ go116: Go 1.16
◆ java11: Java 11
◆ java17: Java 17 (preview)
◆ dotnet3: .NET Framework 3

15
gcloud/beta/memcache/instances/create
View file

@ -7,6 +7,9 @@ SYNOPSIS
--node-count=NODE_COUNT --node-cpu=NODE_CPU --node-memory=NODE_MEMORY
[--async] [--authorized-network=AUTHORIZED_NETWORK]
[--display-name=DISPLAY_NAME] [--labels=KEY=VALUE]
[--maintenance-window-day=MAINTENANCE_WINDOW_DAY]
[--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION]
[--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME]
[--memcached-version=MEMCACHED_VERSION] [--parameters=KEY=VALUE]
[--zones=[ZONES,...]] [GCLOUD_WIDE_FLAG ...]
@ -87,6 +90,18 @@ OPTIONAL FLAGS
--labels=KEY=VALUE
List of label KEY=VALUE pairs to add.
--maintenance-window-day=MAINTENANCE_WINDOW_DAY
The day of week when the window starts, e.g. sunday.
MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday,
sunday, thursday, tuesday, wednesday.
--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION
Duration of the maintenance window in integer hours, e.g 4.
--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME
Hour of day (0 to 23) for the start of maintenance window, in UTC time
zone.
--memcached-version=MEMCACHED_VERSION
Optional major version of Memcached software to use with the instance.
If not provided, default of "1.5" will be used. MEMCACHED_VERSION must

3
gcloud/beta/memcache/instances/help
View file

@ -36,6 +36,9 @@ COMMANDS
list
(BETA) List Memorystore Memcached instances.
reschedule-maintenance
(BETA) Reschedule maintenance window for a Memcache instance.
update
(BETA) Update a Memorystore Memcached instance.

90
gcloud/beta/memcache/instances/reschedule-maintenance Normal file
View file

@ -0,0 +1,90 @@
NAME
gcloud beta memcache instances reschedule-maintenance - reschedule
maintenance window for a Memcache instance
SYNOPSIS
gcloud beta memcache instances reschedule-maintenance
(INSTANCE : --region=REGION) --reschedule-type=RESCHEDULE_TYPE
[--async] [--schedule-time=SCHEDULE_TIME] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Reschedule maintenance window for a Memcache instance.
EXAMPLES
To reschedule maintenance window for an instance with the name
'my-memcache-instance' in region 'us-central-1' with next available window,
run:
$ gcloud beta memcache instances reschedule-maintenance \
my-memcache-instance --region=us-central1 \
--reschedule-type=next-available-window
POSITIONAL ARGUMENTS
Instance resource - Arguments and flags that specify the Cloud Memorystore
for Memcache instance you want to reschedule maintenance window. 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 project attribute:
◆ provide the argument instance on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
INSTANCE
ID of the instance or fully qualified identifier for the instance. To
set the instance attribute:
▸ provide the argument instance on the command line.
This positional must be specified if any of the other arguments in
this group are specified.
--region=REGION
The name of the Memcached region of the instance. Overrides the
default memcache/region property value for this command invocation.
To set the region attribute:
▸ provide the argument instance on the command line with a fully
specified name;
▸ provide the argument --region on the command line;
▸ set the property memcache/region.
REQUIRED FLAGS
--reschedule-type=RESCHEDULE_TYPE
Reschedule type to use for the reschedule maintenance window.
RESCHEDULE_TYPE must be one of:
immediate
Reschedule the maintenance to perform now.
next-available-window
Reschedule the maintenance to the next available window.
specific-time
Reschedule the maintenance to a specific time.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--schedule-time=SCHEDULE_TIME
Time in RFC3339 format, for example: 2012-11-15T16:19:00.094Z
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.
API REFERENCE
This command uses the memcache/v1beta2 API. The full documentation for this
API can be found at: https://cloud.google.com/memorystore/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
$ gcloud alpha memcache instances reschedule-maintenance

24
gcloud/beta/memcache/instances/update
View file

@ -5,8 +5,11 @@ NAME
SYNOPSIS
gcloud beta memcache instances update (INSTANCE : --region=REGION)
(--parameters=KEY=VALUE | --display-name=DISPLAY_NAME
--labels=KEY=VALUE --node-count=NODE_COUNT) [--async]
[GCLOUD_WIDE_FLAG ...]
--labels=KEY=VALUE --node-count=NODE_COUNT --maintenance-window-any
| --maintenance-window-day=MAINTENANCE_WINDOW_DAY
--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION
--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME)
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update a Memcached instance with one or more of the following
@ -144,6 +147,23 @@ REQUIRED FLAGS
Number of memcache nodes in this instance. Valid values range from 1
to 20.
At most one of these can be specified:
--maintenance-window-any
Removes the user-specified maintenance window.
--maintenance-window-day=MAINTENANCE_WINDOW_DAY
The day of week when the window starts, e.g. 'sunday'.
MAINTENANCE_WINDOW_DAY must be one of: friday, monday, saturday,
sunday, thursday, tuesday, wednesday.
--maintenance-window-duration=MAINTENANCE_WINDOW_DURATION
Duration of the maintenance window in integer hours, e.g '4'.
--maintenance-window-start-time=MAINTENANCE_WINDOW_START_TIME
Hour of day (0 to 23) for the start of maintenance window, in UTC
time zone.
OPTIONAL FLAGS
--async
Return immediately, without waiting for the operation in progress to

25
gcloud/beta/redis/instances/create
View file

@ -6,6 +6,8 @@ SYNOPSIS
[--alternative-zone=ALTERNATIVE_ZONE] [--async]
[--connect-mode=CONNECT_MODE] [--display-name=DISPLAY_NAME]
[--enable-auth] [--labels=[KEY=VALUE,...]]
[--maintenance-window-day=MAINTENANCE_WINDOW_DAY]
[--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
[--network=NETWORK; default="default"]
[--persistence-mode=PERSISTENCE_MODE]
[--rdb-snapshot-period=RDB_SNAPSHOT_PERIOD]
@ -91,6 +93,16 @@ FLAGS
contain only hyphens (-), underscores (_), lowercase characters, and
numbers.
--maintenance-window-day=MAINTENANCE_WINDOW_DAY
Day of week for maintenance window, in UTC time zone.
MAINTENANCE_WINDOW_DAY must be one of: SUNDAY, MONDAY, TUESDAY,
WEDNESDAY, THURSDAY, FRIDAY, SATURDAY. MAINTENANCE_WINDOW_DAY must be
one of: day-of-week-unspecified, friday, monday, saturday, sunday,
thursday, tuesday, wednesday.
--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR
Hour of day (0 to 23) for maintenance window, in UTC time zone.
--network=NETWORK; default="default"
The name of the Google Compute Engine network to which the instance
will be connected. If left unspecified, the default network will be
@ -167,10 +179,15 @@ FLAGS
The replica count of the instance.
--reserved-ip-range=RESERVED_IP_RANGE
The CIDR range of internal addresses that are reserved for this
instance. For example, 10.0.0.0/29 or 192.168.0.0/29. Range must be
unique and non-overlapping with existing ranges in the network. If left
unspecified, the service will automatically pick an available range.
For DIRECT_PEERING mode, the CIDR range of internal addresses that are
reserved for this instance. Range must be unique and non-overlapping
with existing subnets in an authorized network. For
PRIVATE_SERVICE_ACCESS mode, the name of an IP address range allocated
for the private service access connection. If not provided, the service
will choose an unused /29 block, for example, 10.0.0.0/29 or
192.168.0.0/29. If READ_REPLICAS_ENABLED is used for the
--read-replicas-mode flag, then the block size required for this flag
is /28.
--size=SIZE; default=1
The memory size of the instance in GiB. If not provided, size of 1 GiB

6
gcloud/beta/redis/instances/reschedule-maintenance
View file

@ -84,8 +84,10 @@ API REFERENCE
API can be found at: https://cloud.google.com/memorystore/docs/redis/
NOTES
This command is currently in beta and might change without notice. This
variant is also available:
This command is currently in beta and might change without notice. These
variants are also available:
$ gcloud redis instances reschedule-maintenance
$ gcloud alpha redis instances reschedule-maintenance

21
gcloud/beta/redis/instances/update
View file

@ -11,7 +11,11 @@ SYNOPSIS
[--remove-redis-config=[KEY,...]] [--replica-count=REPLICA_COUNT]
[--secondary-ip-range=SECONDARY_IP_RANGE] [--size=SIZE]
[--update-labels=[KEY=VALUE,...]] [--update-redis-config=KEY=VALUE]
[--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
[--clear-labels | --remove-labels=[KEY,...]]
[--maintenance-window-any
| --maintenance-window-day=MAINTENANCE_WINDOW_DAY
--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(BETA) Update the metadata and/or configuration parameters of a Redis
@ -179,6 +183,21 @@ FLAGS
silently ignored. If --update-labels is also specified then
--update-labels is applied first.
At most one of these can be specified:
--maintenance-window-any
Removes the user-specified maintenance window.
--maintenance-window-day=MAINTENANCE_WINDOW_DAY
Day of week for maintenance window, in UTC time zone.
MAINTENANCE_WINDOW_DAY must be one of: SUNDAY, MONDAY, TUESDAY,
WEDNESDAY, THURSDAY, FRIDAY, SATURDAY. MAINTENANCE_WINDOW_DAY must be
one of: day-of-week-unspecified, friday, monday, saturday, sunday,
thursday, tuesday, wednesday.
--maintenance-window-hour=MAINTENANCE_WINDOW_HOUR
Hour of day (0 to 23) for maintenance window, in UTC time zone.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

15
gcloud/beta/secrets/update
View file

@ -7,6 +7,8 @@ SYNOPSIS
[--add-topics=[ADD-TOPICS,...] | --clear-topics
| --remove-topics=[REMOVE-TOPICS,...]]
[--clear-labels | --remove-labels=[KEY,...]]
[--clear-version-aliases | --remove-version-aliases=[KEY,...]
| --update-version-aliases=[KEY=VALUE,...]]
[--expire-time=EXPIRE-TIME | --remove-expiration | --ttl=TTL]
[--next-rotation-time=NEXT_ROTATION_TIME --remove-next-rotation-time
--remove-rotation-period
@ -123,6 +125,19 @@ FLAGS
silently ignored. If --update-labels is also specified then
--update-labels is applied first.
Version Aliases
At most one of these can be specified:
--clear-version-aliases
Remove all Version Aliases.
--remove-version-aliases=[KEY,...]
List of Version Aliases to be removed.
--update-version-aliases=[KEY=VALUE,...]
List of key-value pairs to set as Version Aliases.
Expiration.
At most one of these can be specified:

10
gcloud/beta/secrets/versions/access
View file

@ -21,11 +21,11 @@ EXAMPLES
--format='get(payload.data)' | tr '_-' '/+' | base64 -d
POSITIONAL ARGUMENTS
Version resource - Numeric secret version to access or latest to use the
latest version. 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 project
attribute:
Version resource - Numeric secret version to access or a configured alias
(including 'latest' to use the latest version). 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 project attribute:
◆ provide the argument VERSION on the command line with a fully
specified name;
◆ provide the argument --project on the command line;

10
gcloud/beta/secrets/versions/describe
View file

@ -16,11 +16,11 @@ EXAMPLES
$ gcloud beta secrets versions describe 123 --secret=my-secret
POSITIONAL ARGUMENTS
Version resource - Numeric secret version to describe or latest to use the
latest version. 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 project
attribute:
Version resource - Numeric secret version to describe or a configured
alias (including 'latest' to use the latest version). 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 project attribute:
◆ provide the argument VERSION on the command line with a fully
specified name;
◆ provide the argument --project on the command line;

7
gcloud/beta/sql/instances/patch
View file

@ -107,7 +107,12 @@ FLAGS
The database engine type and versions. If left unspecified, no changes
occur. See the list of database versions at
https://cloud.google.com/sql/docs/mysql/admin-api/rest/v1beta4/SqlDatabaseVersion.
DATABASE_VERSION must be one of: MYSQL_8_0_18, MYSQL_8_0_26.
DATABASE_VERSION must be one of: MYSQL_5_6, MYSQL_5_7, MYSQL_8_0,
POSTGRES_9_6, POSTGRES_10, POSTGRES_11, POSTGRES_12, POSTGRES_13,
POSTGRES_14, SQLSERVER_2017_EXPRESS, SQLSERVER_2017_WEB,
SQLSERVER_2017_STANDARD, SQLSERVER_2017_ENTERPRISE,
SQLSERVER_2019_EXPRESS, SQLSERVER_2019_WEB, SQLSERVER_2019_STANDARD,
SQLSERVER_2019_ENTERPRISE, MYSQL_8_0_18, MYSQL_8_0_26.
--deny-maintenance-period-end-date=DENY_MAINTENANCE_PERIOD_END_DATE
Date when the deny maintenance period ends, that is 2021-01-10.

16
gcloud/beta/sql/operations/list
View file

@ -10,6 +10,22 @@ SYNOPSIS
DESCRIPTION
(BETA) Lists all instance operations for the given Cloud SQL instance.
EXAMPLES
To list operations for instances with ID "prod-instance" , run:
$ gcloud beta sql operations list --instance=prod-instance
To list operations for instances with ID "prod-instance" that have 10
results, run:
$ gcloud beta sql operations list --instance=prod-instance --limit=10
To list operations for instances with ID "prod-instance" that have 10
results in a page, run:
$ gcloud beta sql operations list --instance=prod-instance \
--page-size=10
REQUIRED FLAGS
--instance=INSTANCE, -i INSTANCE
Cloud SQL instance ID.