mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Thu Jun 6 09:19:36 UTC 2024
This commit is contained in:
Automated
parent
595ac8640a
commit
40ba53d37f
93 changed files with 3117 additions and 305 deletions
|
|
@ -5,7 +5,9 @@ NAME
|
|||
SYNOPSIS
|
||||
gcloud alpha builds worker-pools create WORKER_POOL --region=REGION
|
||||
[--generation=GENERATION; default=1]
|
||||
[--config-from-file=CONFIG_FROM_FILE | --peered-network=PEERED_NETWORK
|
||||
[--config-from-file=CONFIG_FROM_FILE | --disable-public-ip-address
|
||||
--network-attachment=NETWORK_ATTACHMENT --route-all-traffic
|
||||
| --peered-network=PEERED_NETWORK
|
||||
--peered-network-ip-range=PEERED_NETWORK_IP_RANGE --no-public-egress
|
||||
--worker-disk-size=WORKER_DISK_SIZE
|
||||
--worker-machine-type=WORKER_MACHINE_TYPE] [GCLOUD_WIDE_FLAG ...]
|
||||
|
|
@ -57,32 +59,65 @@ OPTIONAL FLAGS
|
|||
|
||||
Command-line flags to configure the private pool:
|
||||
|
||||
--peered-network=PEERED_NETWORK
|
||||
Existing network to which workers are peered. The network is
|
||||
specified in resource URL format
|
||||
projects/{network_project}/global/networks/{network_name}.
|
||||
At most one of these can be specified:
|
||||
|
||||
If not specified, the workers are not peered to any network.
|
||||
Network configuration for Private Service Connect interface:
|
||||
|
||||
--peered-network-ip-range=PEERED_NETWORK_IP_RANGE
|
||||
An IP range for your peered network. Specify the IP range using
|
||||
Classless Inter-Domain Routing (CIDR) notation with a slash and the
|
||||
subnet prefix size, such as /29.
|
||||
--disable-public-ip-address
|
||||
If set, workers in the worker pool are created without an
|
||||
external IP address.
|
||||
|
||||
Your subnet prefix size must be between 1 and 29. Optional: you can
|
||||
specify an IP address before the subnet prefix value - for example
|
||||
192.168.0.0/24.
|
||||
If the worker pool is within a VPC Service Control perimeter,
|
||||
use this flag.
|
||||
|
||||
If no IP address is specified, your VPC automatically determines
|
||||
the starting IP for the range. If no IP range is specified, Cloud
|
||||
Build uses /24 as the default network IP range.
|
||||
--network-attachment=NETWORK_ATTACHMENT
|
||||
The network attachment that the worker network interface is
|
||||
peered to. The network attachment is specified in resource URL
|
||||
format
|
||||
projects/{project}/regions/{region}/networkAttachments/{name}.
|
||||
The region of network attachment must be the same as the worker
|
||||
pool. See
|
||||
https://cloud.google.com/vpc/docs/about-network-attachments for
|
||||
details.
|
||||
|
||||
--no-public-egress
|
||||
If set, workers in the worker pool are created without an external
|
||||
IP address.
|
||||
--route-all-traffic
|
||||
Route all traffic through PSC interface. Enable this if you
|
||||
want full control of traffic in the private pool. Configure
|
||||
Cloud NAT for the subnet of network attachment if you need to
|
||||
access public Internet.
|
||||
|
||||
If the worker pool is within a VPC Service Control perimeter, use
|
||||
this flag.
|
||||
If unset, Only route private IPs, e.g. 10.0.0.0/8,
|
||||
172.16.0.0/12, and 192.168.0.0/16 through PSC interface.
|
||||
|
||||
Network configuration for Service Networking:
|
||||
|
||||
--peered-network=PEERED_NETWORK
|
||||
Existing network to which workers are peered. The network is
|
||||
specified in resource URL format
|
||||
projects/{network_project}/global/networks/{network_name}.
|
||||
|
||||
If not specified, the workers are not peered to any network.
|
||||
|
||||
--peered-network-ip-range=PEERED_NETWORK_IP_RANGE
|
||||
An IP range for your peered network. Specify the IP range using
|
||||
Classless Inter-Domain Routing (CIDR) notation with a slash and
|
||||
the subnet prefix size, such as /29.
|
||||
|
||||
Your subnet prefix size must be between 1 and 29. Optional: you
|
||||
can specify an IP address before the subnet prefix value - for
|
||||
example 192.168.0.0/24.
|
||||
|
||||
If no IP address is specified, your VPC automatically
|
||||
determines the starting IP for the range. If no IP range is
|
||||
specified, Cloud Build uses /24 as the default network IP
|
||||
range.
|
||||
|
||||
--no-public-egress
|
||||
If set, workers in the worker pool are created without an
|
||||
external IP address.
|
||||
|
||||
If the worker pool is within a VPC Service Control perimeter,
|
||||
use this flag.
|
||||
|
||||
Configuration to be used for creating workers in the worker pool:
|
||||
|
||||
|
|
|
|||
|
|
@ -41,18 +41,20 @@ REQUIRED FLAGS
|
|||
|
||||
Command-line flags to configure the private pool:
|
||||
|
||||
At most one of these can be specified:
|
||||
Network configuration for Service Networking:
|
||||
|
||||
--public-egress
|
||||
If set, workers in the worker pool are created with an external
|
||||
IP address.
|
||||
At most one of these can be specified:
|
||||
|
||||
--no-public-egress
|
||||
If set, workers in the worker pool are created without an
|
||||
external IP address.
|
||||
--public-egress
|
||||
If set, workers in the worker pool are created with an external
|
||||
IP address.
|
||||
|
||||
If the worker pool is within a VPC Service Control perimeter, use
|
||||
this flag.
|
||||
--no-public-egress
|
||||
If set, workers in the worker pool are created without an
|
||||
external IP address.
|
||||
|
||||
If the worker pool is within a VPC Service Control perimeter,
|
||||
use this flag.
|
||||
|
||||
Configuration to be used for creating workers in the worker pool:
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue