mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-08 10:35:03 +00:00
gcloud: Wed May 17 10:38:17 UTC 2023
This commit is contained in:
Automated
parent
14441c7ea7
commit
a56fab68e5
151 changed files with 1878 additions and 2972 deletions
|
|
@ -53,7 +53,9 @@ 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. This variant is also available:
|
||||
access allowlist. These variants are also available:
|
||||
|
||||
$ gcloud compute addresses move
|
||||
|
||||
$ gcloud beta compute addresses move
|
||||
|
||||
|
|
|
|||
|
|
@ -350,12 +350,15 @@ FLAGS
|
|||
IPV6_ONLY.
|
||||
|
||||
--load-balancing-scheme=LOAD_BALANCING_SCHEME; default="EXTERNAL"
|
||||
Specifies the load balancer type. Choose EXTERNAL for load balancers
|
||||
that receive traffic from external clients. Choose EXTERNAL_MANAGED for
|
||||
Envoy-based External HTTP(S) Load Balancing. Choose INTERNAL for
|
||||
Internal TCP/UDP Load Balancing. Choose INTERNAL_MANAGED for Internal
|
||||
HTTP(S) Load Balancing. Choose INTERNAL_SELF_MANAGED for Traffic
|
||||
Director. For more information, refer to this guide:
|
||||
Specifies the load balancer type. Choose EXTERNAL for the classic
|
||||
HTTP(S) load balancers, the external TCP/UDP network load balancers,
|
||||
and the external TCP/SSL proxy load balancers. Choose EXTERNAL_MANAGED
|
||||
for the Envoy-based global and regional external HTTP(S) load
|
||||
balancers. Choose INTERNAL for internal TCP/UDP load balancers. Choose
|
||||
INTERNAL_MANAGED for Envoy-based internal load balancers such as the
|
||||
internal HTTP(S) load balancers and the internal TCP proxy load
|
||||
balancers. Choose INTERNAL_SELF_MANAGED for Traffic Director. For more
|
||||
information, refer to this guide:
|
||||
https://cloud.google.com/load-balancing/docs/choosing-load-balancer.
|
||||
LOAD_BALANCING_SCHEME must be one of: INTERNAL, EXTERNAL,
|
||||
INTERNAL_SELF_MANAGED, EXTERNAL_MANAGED, INTERNAL_MANAGED.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ NAME
|
|||
|
||||
SYNOPSIS
|
||||
gcloud alpha compute firewall-rules migrate --source-network=SOURCE_NETWORK
|
||||
(--export-tag-mapping
|
||||
(--bind-tags-to-instances | --export-tag-mapping
|
||||
| --target-firewall-policy=TARGET_FIREWALL_POLICY)
|
||||
[--tag-mapping-file=TAG_MAPPING_FILE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
|
|
@ -27,6 +27,10 @@ REQUIRED FLAGS
|
|||
|
||||
Exactly one of these must be specified:
|
||||
|
||||
--bind-tags-to-instances
|
||||
If set, migration tool will bind secure tags to the instances with
|
||||
the network tags which match secure tags from the tag mapping file.
|
||||
|
||||
--export-tag-mapping
|
||||
If set, migration tool will inspect all VPC Firewalls attached to
|
||||
SOURCE_NETWORK, collect all source and target tags, and store them in
|
||||
|
|
|
|||
|
|
@ -253,17 +253,18 @@ OPTIONAL FLAGS
|
|||
|
||||
--os=OS
|
||||
Specifies the OS of the disk image being imported. OS must be one of:
|
||||
centos-7, debian-10, debian-11, debian-8, debian-9, opensuse-15,
|
||||
rhel-6, rhel-6-byol, rhel-7, rhel-7-byol, rhel-8, rhel-8-byol,
|
||||
rhel-9, rhel-9-byol, rocky-8, rocky-9, sles-12, sles-12-byol,
|
||||
sles-15, sles-15-byol, sles-sap-12, sles-sap-12-byol, sles-sap-15,
|
||||
sles-sap-15-byol, ubuntu-1404, ubuntu-1604, ubuntu-1804, ubuntu-2004,
|
||||
ubuntu-2204, windows-10-x64-byol, windows-10-x86-byol,
|
||||
windows-11-x64-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-2022, windows-2022-byol, windows-7-x64-byol,
|
||||
windows-7-x86-byol, windows-8-x64-byol, windows-8-x86-byol.
|
||||
centos-7, centos-stream-8, centos-stream-9, debian-10, debian-11,
|
||||
debian-8, debian-9, opensuse-15, rhel-6, rhel-6-byol, rhel-7,
|
||||
rhel-7-byol, rhel-8, rhel-8-byol, rhel-9, rhel-9-byol, rocky-8,
|
||||
rocky-9, sles-12, sles-12-byol, sles-15, sles-15-byol, sles-sap-12,
|
||||
sles-sap-12-byol, sles-sap-15, sles-sap-15-byol, ubuntu-1404,
|
||||
ubuntu-1604, ubuntu-1804, ubuntu-2004, ubuntu-2204,
|
||||
windows-10-x64-byol, windows-10-x86-byol, windows-11-x64-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-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,
|
||||
|
|
|
|||
|
|
@ -86,10 +86,15 @@ OPTIONAL FLAGS
|
|||
disable.
|
||||
|
||||
--initial-delay=INITIAL_DELAY
|
||||
Specifies the length of time during which the instance is known to be
|
||||
initializing and should not be autohealed even if unhealthy. This value
|
||||
cannot be greater than 1 hour. See $ gcloud topic datetimes for
|
||||
information on duration formats.
|
||||
Specifies the number of seconds that a new VM takes to initialize and
|
||||
run its startup script. During a VM's initial delay period, the MIG
|
||||
ignores unsuccessful health checks because the VM might be in the
|
||||
startup process. This prevents the MIG from prematurely recreating a
|
||||
VM. If the health check receives a healthy response during the initial
|
||||
delay, it indicates that the startup process is complete and the VM is
|
||||
ready. The value of initial delay must be between 0 and 3600 seconds.
|
||||
The default value is 0. See $ gcloud topic datetimes for information on
|
||||
duration formats.
|
||||
|
||||
--instance-redistribution-type=TYPE
|
||||
Specifies the type of the instance redistribution policy. An instance
|
||||
|
|
|
|||
|
|
@ -32,10 +32,15 @@ POSITIONAL ARGUMENTS
|
|||
|
||||
FLAGS
|
||||
--initial-delay=INITIAL_DELAY
|
||||
Specifies the length of time during which the instance is known to be
|
||||
initializing and should not be autohealed even if unhealthy. This value
|
||||
cannot be greater than 1 hour. See $ gcloud topic datetimes for
|
||||
information on duration formats.
|
||||
Specifies the number of seconds that a new VM takes to initialize and
|
||||
run its startup script. During a VM's initial delay period, the MIG
|
||||
ignores unsuccessful health checks because the VM might be in the
|
||||
startup process. This prevents the MIG from prematurely recreating a
|
||||
VM. If the health check receives a healthy response during the initial
|
||||
delay, it indicates that the startup process is complete and the VM is
|
||||
ready. The value of initial delay must be between 0 and 3600 seconds.
|
||||
The default value is 0. See $ gcloud topic datetimes for information on
|
||||
duration formats.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
|
|
|
|||
|
|
@ -257,10 +257,15 @@ FLAGS
|
|||
Clears all autohealing policy fields for the managed instance group.
|
||||
|
||||
--initial-delay=INITIAL_DELAY
|
||||
Specifies the length of time during which the instance is known to be
|
||||
initializing and should not be autohealed even if unhealthy. This
|
||||
value cannot be greater than 1 hour. See $ gcloud topic datetimes for
|
||||
information on duration formats.
|
||||
Specifies the number of seconds that a new VM takes to initialize and
|
||||
run its startup script. During a VM's initial delay period, the MIG
|
||||
ignores unsuccessful health checks because the VM might be in the
|
||||
startup process. This prevents the MIG from prematurely recreating a
|
||||
VM. If the health check receives a healthy response during the
|
||||
initial delay, it indicates that the startup process is complete and
|
||||
the VM is ready. The value of initial delay must be between 0 and
|
||||
3600 seconds. The default value is 0. See $ gcloud topic datetimes
|
||||
for information on duration formats.
|
||||
|
||||
At most one of these can be specified:
|
||||
|
||||
|
|
|
|||
|
|
@ -37,6 +37,7 @@ SYNOPSIS
|
|||
[--network=NETWORK] [--network-interface=[PROPERTY=VALUE,...]]
|
||||
[--network-performance-configs=[PROPERTY=VALUE,...]]
|
||||
[--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT]
|
||||
[--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT]
|
||||
[--post-key-revocation-action-type=POLICY] [--preemptible]
|
||||
[--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE]
|
||||
[--private-network-ip=PRIVATE_NETWORK_IP]
|
||||
|
|
@ -713,6 +714,17 @@ FLAGS
|
|||
1, 2, 4 or 8. Setting NUMA node count to 0 means using the default
|
||||
setting.
|
||||
|
||||
--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT
|
||||
The set of performance measurement counters to enable for the instance.
|
||||
PERFORMANCE_MONITORING_UNIT must be one of:
|
||||
|
||||
architectural
|
||||
Enable architecturally defined non-LLC events.
|
||||
enhanced
|
||||
Enable most documented core/L2 and LLC events.
|
||||
standard
|
||||
Enable most documented core/L2 events.
|
||||
|
||||
--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:
|
||||
|
|
|
|||
|
|
@ -35,6 +35,7 @@ SYNOPSIS
|
|||
[--network-interface=[PROPERTY=VALUE,...]]
|
||||
[--network-performance-configs=[PROPERTY=VALUE,...]]
|
||||
[--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT]
|
||||
[--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT]
|
||||
[--post-key-revocation-action-type=POLICY] [--preemptible]
|
||||
[--provisioning-model=PROVISIONING_MODEL]
|
||||
[--resource-manager-tags=[KEY=VALUE,...]]
|
||||
|
|
@ -663,6 +664,17 @@ OPTIONAL FLAGS
|
|||
1, 2, 4 or 8. Setting NUMA node count to 0 means using the default
|
||||
setting.
|
||||
|
||||
--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT
|
||||
The set of performance measurement counters to enable for the instance.
|
||||
PERFORMANCE_MONITORING_UNIT must be one of:
|
||||
|
||||
architectural
|
||||
Enable architecturally defined non-LLC events.
|
||||
enhanced
|
||||
Enable most documented core/L2 and LLC events.
|
||||
standard
|
||||
Enable most documented core/L2 events.
|
||||
|
||||
--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:
|
||||
|
|
|
|||
|
|
@ -43,6 +43,7 @@ SYNOPSIS
|
|||
[--network-performance-configs=[PROPERTY=VALUE,...]]
|
||||
[--network-tier=NETWORK_TIER] [--node-project=NODE_PROJECT]
|
||||
[--numa-node-count=NUMA_NODE_COUNT]
|
||||
[--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT]
|
||||
[--post-key-revocation-action-type=POLICY] [--preemptible]
|
||||
[--private-ipv6-google-access-type=PRIVATE_IPV6_GOOGLE_ACCESS_TYPE]
|
||||
[--private-network-ip=PRIVATE_NETWORK_IP]
|
||||
|
|
@ -740,6 +741,17 @@ FLAGS
|
|||
1, 2, 4 or 8. Setting NUMA node count to 0 means using the default
|
||||
setting.
|
||||
|
||||
--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT
|
||||
The set of performance measurement counters to enable for the instance.
|
||||
PERFORMANCE_MONITORING_UNIT must be one of:
|
||||
|
||||
architectural
|
||||
Enable architecturally defined non-LLC events.
|
||||
enhanced
|
||||
Enable most documented core/L2 and LLC events.
|
||||
standard
|
||||
Enable most documented core/L2 events.
|
||||
|
||||
--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:
|
||||
|
|
|
|||
|
|
@ -165,17 +165,18 @@ OPTIONAL FLAGS
|
|||
|
||||
--os=OS
|
||||
Specifies the OS of the image being imported. OS must be one of:
|
||||
centos-7, debian-10, debian-11, debian-8, debian-9, opensuse-15,
|
||||
rhel-6, rhel-6-byol, rhel-7, rhel-7-byol, rhel-8, rhel-8-byol, rhel-9,
|
||||
rhel-9-byol, rocky-8, rocky-9, sles-12, sles-12-byol, sles-15,
|
||||
sles-15-byol, sles-sap-12, sles-sap-12-byol, sles-sap-15,
|
||||
sles-sap-15-byol, ubuntu-1404, ubuntu-1604, ubuntu-1804, ubuntu-2004,
|
||||
ubuntu-2204, windows-10-x64-byol, windows-10-x86-byol,
|
||||
windows-11-x64-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-2022,
|
||||
windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol,
|
||||
windows-8-x64-byol, windows-8-x86-byol.
|
||||
centos-7, centos-stream-8, centos-stream-9, debian-10, debian-11,
|
||||
debian-8, debian-9, opensuse-15, rhel-6, rhel-6-byol, rhel-7,
|
||||
rhel-7-byol, rhel-8, rhel-8-byol, rhel-9, rhel-9-byol, rocky-8,
|
||||
rocky-9, sles-12, sles-12-byol, sles-15, sles-15-byol, sles-sap-12,
|
||||
sles-sap-12-byol, sles-sap-15, sles-sap-15-byol, ubuntu-1404,
|
||||
ubuntu-1604, ubuntu-1804, ubuntu-2004, ubuntu-2204,
|
||||
windows-10-x64-byol, windows-10-x86-byol, windows-11-x64-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-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
|
||||
|
|
|
|||
|
|
@ -158,17 +158,18 @@ OPTIONAL FLAGS
|
|||
|
||||
--os=OS
|
||||
Specifies the OS of the machine image being imported. OS must be one
|
||||
of: centos-7, debian-10, debian-11, debian-8, debian-9, opensuse-15,
|
||||
rhel-6, rhel-6-byol, rhel-7, rhel-7-byol, rhel-8, rhel-8-byol, rhel-9,
|
||||
rhel-9-byol, rocky-8, rocky-9, sles-12, sles-12-byol, sles-15,
|
||||
sles-15-byol, sles-sap-12, sles-sap-12-byol, sles-sap-15,
|
||||
sles-sap-15-byol, ubuntu-1404, ubuntu-1604, ubuntu-1804, ubuntu-2004,
|
||||
ubuntu-2204, windows-10-x64-byol, windows-10-x86-byol,
|
||||
windows-11-x64-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-2022,
|
||||
windows-2022-byol, windows-7-x64-byol, windows-7-x86-byol,
|
||||
windows-8-x64-byol, windows-8-x86-byol.
|
||||
of: centos-7, centos-stream-8, centos-stream-9, debian-10, debian-11,
|
||||
debian-8, debian-9, opensuse-15, rhel-6, rhel-6-byol, rhel-7,
|
||||
rhel-7-byol, rhel-8, rhel-8-byol, rhel-9, rhel-9-byol, rocky-8,
|
||||
rocky-9, sles-12, sles-12-byol, sles-15, sles-15-byol, sles-sap-12,
|
||||
sles-sap-12-byol, sles-sap-15, sles-sap-15-byol, ubuntu-1404,
|
||||
ubuntu-1604, ubuntu-1804, ubuntu-2004, ubuntu-2204,
|
||||
windows-10-x64-byol, windows-10-x86-byol, windows-11-x64-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-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
|
||||
|
|
|
|||
|
|
@ -35,6 +35,7 @@ SYNOPSIS
|
|||
[--network-interface=[PROPERTY=VALUE,...]]
|
||||
[--network-performance-configs=[PROPERTY=VALUE,...]]
|
||||
[--network-tier=NETWORK_TIER] [--numa-node-count=NUMA_NODE_COUNT]
|
||||
[--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT]
|
||||
[--post-key-revocation-action-type=POLICY] [--preemptible]
|
||||
[--provisioning-model=PROVISIONING_MODEL]
|
||||
[--resource-manager-tags=[KEY=VALUE,...]]
|
||||
|
|
@ -636,6 +637,17 @@ OPTIONAL FLAGS
|
|||
1, 2, 4 or 8. Setting NUMA node count to 0 means using the default
|
||||
setting.
|
||||
|
||||
--performance-monitoring-unit=PERFORMANCE_MONITORING_UNIT
|
||||
The set of performance measurement counters to enable for the instance.
|
||||
PERFORMANCE_MONITORING_UNIT must be one of:
|
||||
|
||||
architectural
|
||||
Enable architecturally defined non-LLC events.
|
||||
enhanced
|
||||
Enable most documented core/L2 and LLC events.
|
||||
standard
|
||||
Enable most documented core/L2 events.
|
||||
|
||||
--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:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue