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

gcloud: Wed Apr 17 09:40:58 UTC 2024

Browse source
This commit is contained in:
Automated 2024-04-17 09:40:58 +00:00
parent 7e2535c53d
commit 3740758467
178 changed files with 2958 additions and 1351 deletions
Download patch file Download diff file Expand all files Collapse all files

63
gcloud/alpha/edge-cloud/container/clusters/create
View file

@ -13,6 +13,7 @@ SYNOPSIS
[--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-address-pools=EXTERNAL_LB_ADDRESS_POOLS]
[--external-lb-ipv4-address-pools=[EXTERNAL_LB_IPV4_ADDRESS,...]]
[--external-lb-ipv6-address-pools=[EXTERNAL_LB_IPV6_ADDRESS,...]]
[--fleet-project=FLEET_PROJECT] [--labels=[KEY=VALUE,...]]
@ -120,6 +121,68 @@ FLAGS
--default-max-pods-per-node=DEFAULT_MAX_PODS_PER_NODE
The default maximum number of pods per node.
--external-lb-address-pools=EXTERNAL_LB_ADDRESS_POOLS
Path to a YAML/JSON file containing external load balancer pool
configuration. External load balancer pools are used for data plane
load balancing of local control plane clusters, with custom config such
as address pool name. Either --external-lb-ipv4-address-pools or
--external-lb-address-pools should be specified. Existing pools cannot
be updated after cluster creation; only adding new pools is allowed
currently.
For example,
{
"externalLoadBalancerAddressPools": [
{
"addressPool": "MyLoadBalancerPool",
"ipv4Range": ["10.200.0.200-10.200.0.204","10.200.0.300/30"],
"avoidBuggyIps": "false",
"manualAssign": "true"
}
]
}
address_pool
Optional. A name that identifies an address pool. If a name is not
specified, an auto-generated one will be used.
ipv4_range
Mandatory. One or more ipv4 address range, each 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"
ipv6_range
Optional. One or more ipv6 address range, each must be specified as
one of the following two types of values:
1. A IPv6 address range, for example, "2001:db8::1-2001:db8::a". A range that contains a single IP (e.g. "2001:db8::1-2001:db8::1") is allowed.
2. A IPv6 CIDR block, for example, "2001:db8::/120"
avoid_buggy_ips
Optional. If true, the pool omits IP addresses ending in .0 and
.255. Some network hardware drops traffic to these special
addresses. Its default value is false.
manual_assign
Optional. If true, addresses in this pool are not automatically
assigned to Kubernetes Services. If true, an IP address in this
pool is used only when it is specified explicitly by a service. Its
default value is false.
--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

11
gcloud/alpha/edge-cloud/container/clusters/list
View file

@ -17,17 +17,16 @@ EXAMPLES
--location=us-central1
FLAGS
Location resource - Parent Edge Container location to list all contained
Edge Container clusters. This represents a Cloud resource. (NOTE) Some
attributes are not given arguments in this group but can be set in other
ways.
Location resource - Edge Container location to list. This represents a
Cloud 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 --location on the command line with a fully
specified name;
◆ set the property edge_container/location with a fully specified name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
◆ provide the argument --project on the command line;
◆ set the property core/project.
--location=LOCATION
ID of the location or fully qualified identifier for the location.

30
gcloud/alpha/edge-cloud/container/clusters/update
View file

@ -7,9 +7,7 @@ SYNOPSIS
(CLUSTER : --location=LOCATION) [--async]
[--release-channel=RELEASE_CHANNEL]
[--clear-maintenance-window
| --maintenance-window-end=MAINTENANCE_WINDOW_END
--maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE
--maintenance-window-start=MAINTENANCE_WINDOW_START]
| --remove-maintenance-exclusion-window=REMOVE_MAINTENANCE_EXCLUSION_WINDOW | --add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END --add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME --add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START | --maintenance-window-end=MAINTENANCE_WINDOW_END --maintenance-window-recurrence=MAINTENANCE_WINDOW_RECURRENCE --maintenance-window-start=MAINTENANCE_WINDOW_START]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
@ -71,7 +69,31 @@ FLAGS
At most one of these can be specified:
--clear-maintenance-window
If set, removes the maintenance window setting from the cluster.
If set, removes the maintenance window setting from the cluster. If
any exclusion windows exist, they must be removed beforehand as a
maintenance policy cannot exist without a maintenance window.
--remove-maintenance-exclusion-window=REMOVE_MAINTENANCE_EXCLUSION_WINDOW
Name of the maintenance exclusion to remove.
Add a maintenance exclusion window (all flags must be specified to add a
valid maintenance exclusion window). There can be a maximum of 3
exclusion windows set at a given time. A maintenance exclusion window
cannot be added in the absence of a maintenance window.
--add-maintenance-exclusion-end=ADD_MAINTENANCE_EXCLUSION_END
End time of the maintenance exclusion window in the RFC 3339
(https://www.ietf.org/rfc/rfc3339.txt) format. E.g.
"2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00".
--add-maintenance-exclusion-name=ADD_MAINTENANCE_EXCLUSION_NAME
Unique name (per cluster) of the maintenance exclusion window that
can be used to remove it.
--add-maintenance-exclusion-start=ADD_MAINTENANCE_EXCLUSION_START
Start time of the maintenance exclusion window (can occur in the
past) in the RFC 3339 (https://www.ietf.org/rfc/rfc3339.txt)
format. E.g. "2021-01-01T00:00:00Z" or "2021-01-01T00:00:00-05:00".
Updates cluster maintenance window setting (more than one flags can be
specified from this group)