mirror of
https://github.com/imjasonh/gcloud-help
synced 2026-07-18 14:56:05 +00:00
gcloud: Wed Sep 13 10:32:10 UTC 2023
This commit is contained in:
parent
6c8d2eb024
commit
39a8a4f491
111 changed files with 1798 additions and 302 deletions
|
|
@ -6,13 +6,21 @@ SYNOPSIS
|
|||
gcloud edge-cloud container clusters create (CLUSTER : --location=LOCATION)
|
||||
[--admin-users=ADMIN_USERS] [--async]
|
||||
[--cluster-ipv4-cidr=CLUSTER_IPV4_CIDR; default="10.0.0.0/17"]
|
||||
[--control-plane-machine-filter=CONTROL_PLANE_MACHINE_FILTER]
|
||||
[--control-plane-node-count=CONTROL_PLANE_NODE_COUNT]
|
||||
[--control-plane-node-location=CONTROL_PLANE_NODE_LOCATION]
|
||||
[--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY]
|
||||
[--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE]
|
||||
[--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]]
|
||||
[--fleet-project=FLEET_PROJECT] [--labels=[KEY=VALUE,...]]
|
||||
[--lro-timeout=LRO_TIMEOUT]
|
||||
[--maintenance-window-end=MAINTENANCE_WINDOW_END]
|
||||
[--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE]
|
||||
[--maintenance-window-start=MAINTENANCE_WINDOW_START]
|
||||
[--release-channel=RELEASE_CHANNEL;
|
||||
default="RELEASE_CHANNEL_UNSPECIFIED"]
|
||||
[--services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12"]
|
||||
[--system-addons-config=SYSTEM_ADDONS_CONFIG] [--version=VERSION]
|
||||
[GCLOUD_WIDE_FLAG ...]
|
||||
|
||||
DESCRIPTION
|
||||
|
|
@ -70,9 +78,43 @@ FLAGS
|
|||
All pods in the cluster are assigned an RFC1918 IPv4 address from this
|
||||
block. This field cannot be changed after creation.
|
||||
|
||||
--control-plane-machine-filter=CONTROL_PLANE_MACHINE_FILTER
|
||||
Only machines matching this filter will be allowed to host local
|
||||
control plane nodes. The filtering language accepts strings like
|
||||
"name=<name>", and is documented here: AIP-160
|
||||
(https://google.aip.dev/160).
|
||||
|
||||
--control-plane-node-count=CONTROL_PLANE_NODE_COUNT
|
||||
The number of local control plane nodes in a cluster. Use one to create
|
||||
a single-node control plane or use three to create a high availability
|
||||
control plane. Any other numbers of nodes will not be accepted.
|
||||
|
||||
--control-plane-node-location=CONTROL_PLANE_NODE_LOCATION
|
||||
Google Edge Cloud zone where the local control plane nodes will be
|
||||
created.
|
||||
|
||||
--control-plane-shared-deployment-policy=CONTROL_PLANE_SHARED_DEPLOYMENT_POLICY
|
||||
Policy configuration about how user application is deployed for local
|
||||
control plane cluster. It supports two values, ALLOWED and DISALLOWED.
|
||||
ALLOWED means that user application can be deployed on control plane
|
||||
nodes. DISALLOWED means that user application can not be deployed on
|
||||
control plane nodes. Instead, it can only be deployed on worker nodes.
|
||||
By default, this value is DISALLOWED. The input is case insensitive.
|
||||
|
||||
--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE
|
||||
The default maximum number of pods per node.
|
||||
|
||||
--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]
|
||||
IPv4 address pools that are used for data plane load balancing of local
|
||||
control plane clusters. Existing pools cannot be updated after cluster
|
||||
creation; only adding new pools is allowed. Each address pool must be
|
||||
specified as one of the following two types of values: 1. A IPv4
|
||||
address range, for example, "10.0.0.1-10.0.0.10". A range that contains
|
||||
a single IP (e.g. "10.0.0.1-10.0.0.1") is allowed. 2. A IPv4 CIDR
|
||||
block, for example, "10.0.0.1/24" Use comma when specifying multiple
|
||||
address pools, for example: --external-lb-ipv4-address-pools
|
||||
10.0.0.1-10.0.0.10,10.0.0.1/24
|
||||
|
||||
--fleet-project=FLEET_PROJECT
|
||||
Name of the Fleet host project where the cluster is registered.
|
||||
|
||||
|
|
@ -102,10 +144,31 @@ FLAGS
|
|||
(https://www.ietf.org/rfc/rfc3339.txt) format. E.g.
|
||||
"2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00"
|
||||
|
||||
--release-channel=RELEASE_CHANNEL; default="RELEASE_CHANNEL_UNSPECIFIED"
|
||||
Release channel a cluster is subscribed to. It supports two values,
|
||||
NONE and REGULAR. NONE is used to opt out of any release channel.
|
||||
Clusters subscribed to the REGULAR channel will be automatically
|
||||
upgraded to versions that are considered GA quality, and cannot be
|
||||
manually upgraded. Additionally, if the REGULAR channel is used, a
|
||||
specific target version cannot be set with the 'version' flag. If left
|
||||
unspecified, the release channel will default to REGULAR.
|
||||
|
||||
--services-ipv4-cidr=SERVICES_IPV4_CIDR; default="10.96.0.0/12"
|
||||
All services in the cluster are assigned an RFC1918 IPv4 address from
|
||||
this block. This field cannot be changed after creation.
|
||||
|
||||
--system-addons-config=SYSTEM_ADDONS_CONFIG
|
||||
If specified as a YAML/JSON file, customized configuration in this file
|
||||
will be applied to the system add-ons.
|
||||
|
||||
For example,
|
||||
|
||||
{ "systemAddonsConfig": { "ingress": { "disabled": true, "ipv4_vip":
|
||||
"10.0.0.1" } } }
|
||||
|
||||
--version=VERSION
|
||||
Target cluster version. For example: "1.5.0".
|
||||
|
||||
GCLOUD WIDE FLAGS
|
||||
These flags are available to all commands: --access-token-file, --account,
|
||||
--billing-project, --configuration, --flags-file, --flatten, --format,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue