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

gcloud: Wed May 18 08:41:01 UTC 2022

Browse source
This commit is contained in:
Automated 2022-05-18 08:41:01 +00:00
parent 379049f21a
commit 9f95235d93
258 changed files with 7569 additions and 441 deletions
Download patch file Download diff file Expand all files Collapse all files

51
gcloud/compute/backend-services/add-service-bindings Normal file
View file

@ -0,0 +1,51 @@
NAME
gcloud compute backend-services add-service-bindings - add service bindings
to a backend service
SYNOPSIS
gcloud compute backend-services add-service-bindings BACKEND_SERVICE_NAME
--service-bindings=SERVICE_BINDING,[...] [--global | --region=REGION]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Add service bindings to a backend service.
EXAMPLES
To add a service binding to a backend service, run:
$ gcloud compute backend-services add-service-bindings NAME \
--service-bindings=SERVICE_BINDING1 --global
POSITIONAL ARGUMENTS
BACKEND_SERVICE_NAME
Name of the backend service to operate on.
REQUIRED FLAGS
--service-bindings=SERVICE_BINDING,[...]
List of service binding names to be added to the backend service.
OPTIONAL FLAGS
At most one of these can be specified:
--global
If set, the backend service is global.
--region=REGION
Region of the backend service to operate on. Overrides the default
compute/region property value for this command invocation.
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
These variants are also available:
$ gcloud alpha compute backend-services add-service-bindings
$ gcloud beta compute backend-services add-service-bindings

6
gcloud/compute/backend-services/create
View file

@ -29,6 +29,7 @@ SYNOPSIS
[--[no-]negative-caching] [--negative-caching-policy=[[CODE=TTL],...]]
[--network=NETWORK] [--port-name=PORT_NAME] [--protocol=PROTOCOL]
[--[no-]request-coalescing] [--serve-while-stale=SERVE_WHILE_STALE]
[--service-bindings=SERVICE_BINDING,[...]]
[--session-affinity=SESSION_AFFINITY]
[--signed-url-cache-max-age=SIGNED_URL_CACHE_MAX_AGE]
[--subsetting-policy=SUBSETTING_POLICY; default="NONE"]
@ -477,6 +478,11 @@ FLAGS
Set this to zero (0) to disable serve-while-stale.
--service-bindings=SERVICE_BINDING,[...]
List of service bindings to be attached to this backend service. Can
only be set if load balancing scheme is INTERNAL_SELF_MANAGED. If set,
lists of backends and health checks must be both empty.
--session-affinity=SESSION_AFFINITY
The type of session affinity to use. Supports both TCP and UDP.
SESSION_AFFINITY must be one of:

6
gcloud/compute/backend-services/help
View file

@ -27,6 +27,9 @@ COMMANDS
add-backend
Add a backend to a backend service.
add-service-bindings
Add service bindings to a backend service.
add-signed-url-key
Add Cloud CDN Signed URL key to a backend service.
@ -60,6 +63,9 @@ COMMANDS
remove-backend
Remove a backend from a backend service.
remove-service-bindings
Remove service bindings from a backend service.
update
Update a backend service.

51
gcloud/compute/backend-services/remove-service-bindings Normal file
View file

@ -0,0 +1,51 @@
NAME
gcloud compute backend-services remove-service-bindings - remove service
bindings from a backend service
SYNOPSIS
gcloud compute backend-services remove-service-bindings
BACKEND_SERVICE_NAME --service-bindings=SERVICE_BINDING,[...]
[--global | --region=REGION] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Remove service bindings from a backend service.
EXAMPLES
To remove a service binding from a backend service, run:
$ gcloud compute backend-services remove-service-bindings NAME \
--service-bindings=SERVICE_BINDING1 --global
POSITIONAL ARGUMENTS
BACKEND_SERVICE_NAME
Name of the backend service to operate on.
REQUIRED FLAGS
--service-bindings=SERVICE_BINDING,[...]
List of service binding names to be removed from the backend service.
OPTIONAL FLAGS
At most one of these can be specified:
--global
If set, the backend service is global.
--region=REGION
Region of the backend service to operate on. Overrides the default
compute/region property value for this command invocation.
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
These variants are also available:
$ gcloud alpha compute backend-services remove-service-bindings
$ gcloud beta compute backend-services remove-service-bindings

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

@ -42,6 +42,7 @@ SYNOPSIS
[--[no-]negative-caching | --no-negative-caching-policies
| --negative-caching-policy=[[CODE=TTL],...]]
[--serve-while-stale=SERVE_WHILE_STALE | --no-serve-while-stale]
[--service-bindings=SERVICE_BINDING,[...] | --no-service-bindings]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -687,6 +688,16 @@ FLAGS
--no-serve-while-stale
Clears serve while stale value.
At most one of these can be specified:
--service-bindings=SERVICE_BINDING,[...]
List of service bindings to be attached to this backend service. Can
only be set if load balancing scheme is INTERNAL_SELF_MANAGED. If
set, lists of backends and health checks must be both empty.
--no-service-bindings
No service bindings should be attached to the backend service.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

11
gcloud/compute/forwarding-rules/create
View file

@ -14,8 +14,8 @@ SYNOPSIS
| --target-ssl-proxy=TARGET_SSL_PROXY
| --target-tcp-proxy=TARGET_TCP_PROXY
| --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access]
[--description=DESCRIPTION] [--ip-protocol=IP_PROTOCOL]
[--is-mirroring-collector]
[--description=DESCRIPTION] [--disable-automate-dns-zone]
[--ip-protocol=IP_PROTOCOL] [--is-mirroring-collector]
[--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK]
[--network-tier=NETWORK_TIER]
[--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION]
@ -173,6 +173,13 @@ OPTIONAL FLAGS
--description=DESCRIPTION
Optional textual description for the forwarding rule.
--disable-automate-dns-zone
If specified, then a DNS zone will not be auto-generated for this
Private Service Connect forwarding rule. This can only be specified if
the forwarding rule's target is a service attachment
(--target-service-attachment=SERVICE_ATTACHMENT) or Google APIs bundle
(--target-google-apis-bundle=API_BUNDLE)
--ip-protocol=IP_PROTOCOL
IP protocol that the rule will serve. The default is TCP.

4
gcloud/compute/images/import
View file

@ -189,8 +189,8 @@ OPTIONAL FLAGS
windows-10-x86-byol, windows-2008r2, windows-2008r2-byol,
windows-2012, windows-2012-byol, windows-2012r2, windows-2012r2-byol,
windows-2016, windows-2016-byol, windows-2019, windows-2019-byol,
windows-7-x64-byol, windows-7-x86-byol, windows-8-x64-byol,
windows-8-x86-byol.
windows-2022, windows-2022-byol, windows-7-x64-byol,
windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,

12
gcloud/compute/instances/bulk/create
View file

@ -26,6 +26,7 @@ SYNOPSIS
[--min-count=MIN_COUNT] [--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]
[--post-key-revocation-action-type=POLICY] [--preemptible]
[--provisioning-model=PROVISIONING_MODEL]
@ -526,6 +527,17 @@ OPTIONAL FLAGS
Specifies the Network Interface Controller (NIC) type for the
interface. NIC_TYPE must be one of: GVNIC, VIRTIO_NET.
--network-performance-configs=[PROPERTY=VALUE,...]
Configures network performance settings for the instance. If this flag
is not specified, the instance will be created with its default network
performance configuration.
total-egress-bandwidth-tier
Total egress bandwidth is the available outbound bandwidth from a
VM, regardless of whether the traffic is going to internal IP or
external IP destinations. The following tier values are allowed:
[DEFAULT,TIER_1]
--network-tier=NETWORK_TIER
Specifies the network tier that will be used to configure the instance.
NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. The

5
gcloud/compute/instances/import
View file

@ -165,8 +165,9 @@ OPTIONAL FLAGS
ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol,
windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012,
windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016,
windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol,
windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol.
windows-2016-byol, windows-2019, windows-2019-byol, windows-2022,
windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol,
windows-8-x64-byol, windows-8-x86-byol.
--private-network-ip=PRIVATE_NETWORK_IP
Specifies the RFC1918 IP to assign to the instance. The IP should be in

41
gcloud/compute/instances/set-scheduling
View file

@ -6,7 +6,10 @@ SYNOPSIS
gcloud compute instances set-scheduling INSTANCE_NAME
[--clear-min-node-cpu] [--maintenance-policy=MAINTENANCE_POLICY]
[--min-node-cpu=MIN_NODE_CPU] [--[no-]preemptible]
[--[no-]restart-on-failure] [--zone=ZONE]
[--provisioning-model=PROVISIONING_MODEL] [--[no-]restart-on-failure]
[--zone=ZONE]
[--clear-instance-termination-action
| --instance-termination-action=INSTANCE_TERMINATION_ACTION]
[--clear-node-affinities | --node=NODE
| --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP]
[GCLOUD_WIDE_FLAG ...]
@ -58,6 +61,19 @@ FLAGS
instances can not be restarted and will not migrate. Use --preemptible
to enable and --no-preemptible to disable.
--provisioning-model=PROVISIONING_MODEL
Specifies provisioning model, which determines price, obtainability,
and runtime for the VM instance. PROVISIONING_MODEL must be one of:
SPOT
Spot VMs are spare capacity; Spot VMs are discounted to have much
lower prices than standard VMs but have no guaranteed runtime. Spot
VMs are the new version of preemptible VM instances, except Spot
VMs do not have a 24-hour maximum runtime.
STANDARD
Default. Standard provisioning model for VM instances, which has
user-controlled runtime but no Spot discounts.
--[no-]restart-on-failure
The instances will be restarted if they are terminated by Compute
Engine. This does not affect terminations performed by the user. This
@ -88,6 +104,29 @@ FLAGS
Alternatively, the zone can be stored in the environment variable
CLOUDSDK_COMPUTE_ZONE.
Instance Termination Action
At most one of these can be specified:
--clear-instance-termination-action
Disables the termination action for this VM if allowed OR sets
termination action to the default value. Depending on a VM's
availability settings, a termination action is either required or not
allowed. This flag is required when you are updating a VM such that
it's previously specified termination action is no longer allowed. If
you use this flag when a VM requires a termination action, it's
termination action is just set to the default value (stop).
--instance-termination-action=INSTANCE_TERMINATION_ACTION
Specifies the termination action that will be taken upon VM
preemption. INSTANCE_TERMINATION_ACTION must be one of:
DELETE
Permanently delete the VM.
STOP
Default. Stop the VM without preserving memory. The VM can be
restarted later.
Sole Tenancy.
At most one of these can be specified:

39
gcloud/compute/instances/update
View file

@ -7,7 +7,10 @@ SYNOPSIS
[--[no-]shielded-integrity-monitoring]
[--shielded-learn-integrity-policy] [--[no-]shielded-secure-boot]
[--[no-]shielded-vtpm] [--update-labels=[KEY=VALUE,...]] [--zone=ZONE]
[--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...]
[--clear-labels | --remove-labels=[KEY,...]]
[--clear-node-affinities | --node=NODE
| --node-affinity-file=NODE_AFFINITY_FILE | --node-group=NODE_GROUP]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute instances update updates labels and requested CPU Platform
@ -158,6 +161,40 @@ FLAGS
silently ignored. If --update-labels is also specified then
--update-labels is applied first.
Sole Tenancy.
At most one of these can be specified:
--clear-node-affinities
Removes the node affinities field from the instance. If specified,
the instance node settings will be cleared. The instance will not be
scheduled onto a sole-tenant node.
--node=NODE
The name of the node to schedule this instance on.
--node-affinity-file=NODE_AFFINITY_FILE
The JSON/YAML file containing the configuration of desired nodes onto
which this instance could be scheduled. These rules filter the nodes
according to their node affinity labels. A node's affinity labels
come from the node template of the group the node is in.
The file should contain a list of a JSON/YAML objects with the
following fields:
key
Corresponds to the node affinity label keys of the Node resource.
operator
Specifies the node selection type. Must be one of: IN: Requires
Compute Engine to seek for matched nodes. NOT_IN: Requires
Compute Engine to avoid certain nodes.
values
Optional. A list of values which correspond to the node affinity
label values of the Node resource.
--node-group=NODE_GROUP
The name of the node group to schedule this instance on.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

5
gcloud/compute/machine-images/import
View file

@ -157,8 +157,9 @@ OPTIONAL FLAGS
ubuntu-1604, ubuntu-1804, ubuntu-2004, windows-10-x64-byol,
windows-10-x86-byol, windows-2008r2, windows-2008r2-byol, windows-2012,
windows-2012-byol, windows-2012r2, windows-2012r2-byol, windows-2016,
windows-2016-byol, windows-2019, windows-2019-byol, windows-7-x64-byol,
windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol.
windows-2016-byol, windows-2019, windows-2019-byol, windows-2022,
windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol,
windows-8-x64-byol, windows-8-x86-byol.
--restart-on-failure
The VMs created from the imported machine image are restarted if they

16
gcloud/compute/networks/peerings/create
View file

@ -7,7 +7,8 @@ SYNOPSIS
--peer-network=PEER_NETWORK [--async] [--auto-create-routes]
[--export-custom-routes] [--export-subnet-routes-with-public-ip]
[--import-custom-routes] [--import-subnet-routes-with-public-ip]
[--peer-project=PEER_PROJECT] [GCLOUD_WIDE_FLAG ...]
[--peer-project=PEER_PROJECT] [--stack-type=STACK_TYPE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud compute networks peerings create is used to create peerings between
@ -73,6 +74,19 @@ OPTIONAL FLAGS
The name of the project for the peer network. If not specified,
defaults to current project.
--stack-type=STACK_TYPE
Stack type of the peering. If not specified, defaults to IPV4_ONLY.
STACK_TYPE must be one of:
IPV4_ONLY
Only IPv4 traffic and routes will be exchanged across this peering.
IPV4_IPV6
IPv4 traffic and routes will be exchanged across this peering.
IPv6 traffic and routes will be exchanged if the matching peering
configuration also has stack_type set to IPV4_IPV6.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,

15
gcloud/compute/networks/peerings/update
View file

@ -6,7 +6,7 @@ SYNOPSIS
gcloud compute networks peerings update NAME --network=NETWORK
[--export-custom-routes] [--export-subnet-routes-with-public-ip]
[--import-custom-routes] [--import-subnet-routes-with-public-ip]
[GCLOUD_WIDE_FLAG ...]
[--stack-type=STACK_TYPE] [GCLOUD_WIDE_FLAG ...]
EXAMPLES
To update the peering named peering-name to both export and import custom
@ -50,6 +50,19 @@ OPTIONAL FLAGS
public IP ranges from peer network. Use
--no-import-subnet-routes-with-public-ip to disable it.
--stack-type=STACK_TYPE
Stack type of the peering. If not specified, defaults to IPV4_ONLY.
STACK_TYPE must be one of:
IPV4_ONLY
Only IPv4 traffic and routes will be exchanged across this peering.
IPV4_IPV6
IPv4 traffic and routes will be exchanged across this peering.
IPv6 traffic and routes will be exchanged if the matching peering
configuration also has stack_type set to IPV4_IPV6.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,