diff --git a/gcloud/_version b/gcloud/_version index 08803fbab..003a7d7db 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 442.0.0 -alpha 2023.08.04 -beta 2023.08.04 +Google Cloud SDK 443.0.0 +alpha 2023.08.11 +beta 2023.08.11 bq 2.0.96 bundled-python3-unix 3.9.16 -core 2023.08.04 +core 2023.08.11 gcloud-crc32c 1.0.0 gsutil 5.25 diff --git a/gcloud/alloydb/instances/create b/gcloud/alloydb/instances/create index 7f6f2cd7c..6dc2967a1 100644 --- a/gcloud/alloydb/instances/create +++ b/gcloud/alloydb/instances/create @@ -40,7 +40,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: diff --git a/gcloud/alloydb/instances/update b/gcloud/alloydb/instances/update index 09aaabe32..541b3d187 100644 --- a/gcloud/alloydb/instances/update +++ b/gcloud/alloydb/instances/update @@ -52,7 +52,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an diff --git a/gcloud/alpha/ai/model-monitoring-jobs/create b/gcloud/alpha/ai/model-monitoring-jobs/create index 0894142cf..2fddb0c4c 100644 --- a/gcloud/alpha/ai/model-monitoring-jobs/create +++ b/gcloud/alpha/ai/model-monitoring-jobs/create @@ -10,6 +10,7 @@ SYNOPSIS [--[no-]anomaly-cloud-logging] [--labels=[KEY=VALUE,...]] [--log-ttl=LOG_TTL] [--monitoring-frequency=MONITORING_FREQUENCY; default=24] + [--notification-channels=[NOTIFICATION_CHANNELS,...]] [--predict-instance-schema=PREDICT_INSTANCE_SCHEMA] [--region=REGION] [--sample-predict-request=SAMPLE_PREDICT_REQUEST] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -119,6 +120,10 @@ OPTIONAL FLAGS --monitoring-frequency=MONITORING_FREQUENCY; default=24 Monitoring frequency, unit is 1 hour. + --notification-channels=[NOTIFICATION_CHANNELS,...] + Comma-separated notification channel list. e.g. + --notification-channels=projects/fake-project/notificationChannels/123,projects/fake-project/notificationChannels/456 + --predict-instance-schema=PREDICT_INSTANCE_SCHEMA YAML schema file uri(Google Cloud Storage) describing the format of a single instance, which are given to format this Endpoint's prediction. diff --git a/gcloud/alpha/ai/model-monitoring-jobs/update b/gcloud/alpha/ai/model-monitoring-jobs/update index 85d7a51ab..09fff9f90 100644 --- a/gcloud/alpha/ai/model-monitoring-jobs/update +++ b/gcloud/alpha/ai/model-monitoring-jobs/update @@ -9,6 +9,7 @@ SYNOPSIS [--[no-]anomaly-cloud-logging] [--display-name=DISPLAY_NAME] [--emails=[EMAILS,...]] [--log-ttl=LOG_TTL] [--monitoring-frequency=MONITORING_FREQUENCY] + [--notification-channels=[NOTIFICATION_CHANNELS,...]] [--prediction-sampling-rate=PREDICTION_SAMPLING_RATE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] @@ -85,6 +86,10 @@ FLAGS --monitoring-frequency=MONITORING_FREQUENCY Monitoring frequency, unit is 1 hour. + --notification-channels=[NOTIFICATION_CHANNELS,...] + Comma-separated notification channel list. e.g. + --notification-channels=projects/fake-project/notificationChannels/123,projects/fake-project/notificationChannels/456 + --prediction-sampling-rate=PREDICTION_SAMPLING_RATE Prediction sampling rate. diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create index 56f0d91ba..97df9d160 100644 --- a/gcloud/alpha/alloydb/clusters/create +++ b/gcloud/alpha/alloydb/clusters/create @@ -5,7 +5,7 @@ NAME SYNOPSIS gcloud alpha alloydb clusters create CLUSTER --password=PASSWORD --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] - [--async] [--network=NETWORK] + [--async] [--database-version=DATABASE_VERSION] [--network=NETWORK] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -54,6 +54,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --database-version=DATABASE_VERSION + Database version of the cluster. DATABASE_VERSION must be one of: + POSTGRES_14, POSTGRES_15. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/alpha/alloydb/instances/create b/gcloud/alpha/alloydb/instances/create index 4948a546e..3fb18d3f7 100644 --- a/gcloud/alpha/alloydb/instances/create +++ b/gcloud/alpha/alloydb/instances/create @@ -41,7 +41,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: diff --git a/gcloud/alpha/alloydb/instances/update b/gcloud/alpha/alloydb/instances/update index 8e5d11353..8b3c9134e 100644 --- a/gcloud/alpha/alloydb/instances/update +++ b/gcloud/alpha/alloydb/instances/update @@ -56,7 +56,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an diff --git a/gcloud/alpha/asset/analyze-org-policies b/gcloud/alpha/asset/analyze-org-policies index 465fd5193..2ff23c684 100644 --- a/gcloud/alpha/asset/analyze-org-policies +++ b/gcloud/alpha/asset/analyze-org-policies @@ -11,7 +11,7 @@ DESCRIPTION (ALPHA) Analyze organization policies under a scope. EXAMPLES - To list 10 org policies of a constraint in an organization, run: + To list 10 organization policies of a constraint in an organization, run: $ gcloud alpha asset analyze-org-policies \ --scope=organizations/YOUR_ORG_ID \ @@ -23,16 +23,15 @@ REQUIRED FLAGS response only contains analyzed organization policies for the provided constraint. - Examples: + Example: - ◆ ``organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} + ◆ organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} for a user-defined custom constraint. --scope=SCOPE - Scope can only be an organization for now. The analysis is limited to - the Cloud org policies within this scope. The caller must be granted - the cloudasset.assets.searchAllResources permission on the desired - scope. + Scope can only be an organization. The analysis is limited to the Cloud + organization policies within this scope. The caller must be granted the + cloudasset.assets.searchAllResources permission on the desired scope. The allowed values are: diff --git a/gcloud/alpha/asset/analyze-org-policy-governed-containers b/gcloud/alpha/asset/analyze-org-policy-governed-containers index 9dad3ecc3..f282282eb 100644 --- a/gcloud/alpha/asset/analyze-org-policy-governed-containers +++ b/gcloud/alpha/asset/analyze-org-policy-governed-containers @@ -24,16 +24,16 @@ REQUIRED FLAGS response only contains analyzed organization policies for the provided constraint. - Examples: + Example: - ◆ ``organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} + ◆ organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} for a user-defined custom constraint. --scope=SCOPE - Scope can only be an organization for now. The analysis is limited to - the Cloud org policies and containers within this scope. The caller - must be granted the cloudasset.assets.searchAllResources permission on - the desired scope. + Scope can only be an organization. The analysis is limited to the Cloud + organization policies and containers within this scope. The caller must + be granted the cloudasset.assets.searchAllResources permission on the + desired scope. The allowed values are: diff --git a/gcloud/alpha/assured/workloads/enable-resource-monitoring b/gcloud/alpha/assured/workloads/enable-resource-monitoring new file mode 100644 index 000000000..b29e0ba96 --- /dev/null +++ b/gcloud/alpha/assured/workloads/enable-resource-monitoring @@ -0,0 +1,68 @@ +NAME + gcloud alpha assured workloads enable-resource-monitoring - enables + Resource Monitoring for an Assured Workloads environment + +SYNOPSIS + gcloud alpha assured workloads enable-resource-monitoring + (WORKLOAD : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enable resource violation monitoring for a workload. + +EXAMPLES + To enable resource violation monitoring for a workload in the us-central1 + region, belonging to an organization with ID 123, with workload ID 456, + run: + + $ gcloud alpha assured workloads enable-resource-monitoring \ + organizations/123/locations/us-central1/workloads/456 + +POSITIONAL ARGUMENTS + Workload resource - The Assured Workloads environment resource to + enable-resource-monitoring. The arguments in this group can be used to + specify the attributes of this resource. + + This must be specified. + + WORKLOAD + ID of the workload or fully qualified identifier for the workload. + + To set the workload attribute: + ▸ provide the argument workload on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the workload. + + To set the location attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The parent organization for the workload. + + To set the organization attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + +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 + 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: + + $ gcloud beta assured workloads enable-resource-monitoring + diff --git a/gcloud/alpha/assured/workloads/help b/gcloud/alpha/assured/workloads/help index 554e60084..eb23ad7de 100644 --- a/gcloud/alpha/assured/workloads/help +++ b/gcloud/alpha/assured/workloads/help @@ -31,6 +31,10 @@ COMMANDS describe (ALPHA) Describe Assured Workloads environment. + enable-resource-monitoring + (ALPHA) Enables Resource Monitoring for an Assured Workloads + environment. + list (ALPHA) List all Assured Workloads environments that belong to a given parent organization. diff --git a/gcloud/alpha/bigtable/backups/copy b/gcloud/alpha/bigtable/backups/copy index df4c589e0..d1c3bd67a 100644 --- a/gcloud/alpha/bigtable/backups/copy +++ b/gcloud/alpha/bigtable/backups/copy @@ -15,7 +15,7 @@ SYNOPSIS [--async] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) This command copies a Cloud Bigtable backup to a new backup. + (ALPHA) This command creates a copy of a Cloud Bigtable backup. EXAMPLES To copy a backup within the same project, run: @@ -26,7 +26,7 @@ EXAMPLES --destination-instance=DESTINATION_INSTANCE \ --destination-cluster=DESTINATION_CLUSTER \ --destination-backup=DESTINATION_BACKUP \ - --expiration-date=2022-08-01T10:49:41Z + --expiration-date=2023-09-01T10:49:41Z To copy a backup to a different project, run: @@ -93,13 +93,13 @@ REQUIRED FLAGS --expiration-date=EXPIRATION_DATE Expiration time of the backup, must be at least 6 hours and at most - 30 days from the time the request is received. See $ gcloud topic - datetimes for information on date/time formats. + 30 days from the time the source backup is created. See $ gcloud + topic datetimes for information on date/time formats. --retention-period=RETENTION_PERIOD Retention period of the backup relative from now, must be at least 6 - hours and at most 30 days. See $ gcloud topic datetimes for - information on duration formats. + hours and at most 30 days from the time the source backup is created. + See $ gcloud topic datetimes for information on duration formats. Backup resource - The source backup to copy from. The arguments in this group can be used to specify the attributes of this resource. @@ -160,5 +160,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. + access allowlist. These variants are also available: + + $ gcloud bigtable backups copy + + $ gcloud beta bigtable backups copy diff --git a/gcloud/alpha/compute/forwarding-rules/create b/gcloud/alpha/compute/forwarding-rules/create index 0530712f3..7e8b53ac4 100644 --- a/gcloud/alpha/compute/forwarding-rules/create +++ b/gcloud/alpha/compute/forwarding-rules/create @@ -16,6 +16,8 @@ SYNOPSIS | --target-vpn-gateway=TARGET_VPN_GATEWAY) [--address=ADDRESS] [--allow-global-access] [--allow-psc-global-access] [--description=DESCRIPTION] [--disable-automate-dns-zone] + [--ip-collection=IP_COLLECTION] + [--ip-collection-region=IP_COLLECTION_REGION] [--ip-protocol=IP_PROTOCOL] [--ip-version=IP_VERSION] [--is-mirroring-collector] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK] @@ -215,6 +217,15 @@ OPTIONAL FLAGS (--target-service-attachment=SERVICE_ATTACHMENT) or Google APIs bundle (--target-google-apis-bundle=API_BUNDLE) + --ip-collection=IP_COLLECTION + Resource reference to a PublicDelegatedPrefix. The PDP must be a + sub-PDP in EXTERNAL_IPV6_FORWARDING_RULE_CREATION mode. + + --ip-collection-region=IP_COLLECTION_REGION + Region of the public delegated prefix to operate on. If not specified, + the region is set to the region of the forwarding rule. Overrides the + default compute/region property value for this command invocation. + --ip-protocol=IP_PROTOCOL IP protocol that the rule will serve. The default is TCP. diff --git a/gcloud/alpha/compute/future-reservations/create b/gcloud/alpha/compute/future-reservations/create index 59851e529..8612ca3fc 100644 --- a/gcloud/alpha/compute/future-reservations/create +++ b/gcloud/alpha/compute/future-reservations/create @@ -4,7 +4,7 @@ NAME SYNOPSIS gcloud alpha compute future-reservations create FUTURE_RESERVATION - --auto-delete-auto-created-reservations --total-count=TOTAL_COUNT + --[no-]auto-delete-auto-created-reservations --total-count=TOTAL_COUNT (--source-instance-template=SOURCE_INSTANCE_TEMPLATE | [--machine-type=MACHINE_TYPE : --accelerator=[count=COUNT],[type=TYPE] @@ -49,9 +49,11 @@ POSITIONAL ARGUMENTS Name of the future reservation to create. REQUIRED FLAGS - --auto-delete-auto-created-reservations + --[no-]auto-delete-auto-created-reservations If specified, the auto-created reservations for a future reservation are deleted at the end time (default) or at a specified delete time. + Use --auto-delete-auto-created-reservations to enable and + --no-auto-delete-auto-created-reservations to disable. --total-count=TOTAL_COUNT The total number of instances for which capacity assurance is requested diff --git a/gcloud/alpha/compute/future-reservations/update b/gcloud/alpha/compute/future-reservations/update index e86bebcd3..f297b6fdc 100644 --- a/gcloud/alpha/compute/future-reservations/update +++ b/gcloud/alpha/compute/future-reservations/update @@ -4,9 +4,9 @@ NAME SYNOPSIS gcloud alpha compute future-reservations update FUTURE_RESERVATION - [--auto-delete-auto-created-reservations] [--description=DESCRIPTION] - [--planning-status=PLANNING_STATUS] [--total-count=TOTAL_COUNT] - [--zone=ZONE] + [--[no-]auto-delete-auto-created-reservations] + [--description=DESCRIPTION] [--planning-status=PLANNING_STATUS] + [--total-count=TOTAL_COUNT] [--zone=ZONE] [--auto-created-reservations-delete-time=AUTO_CREATED_RESERVATIONS_DELETE_TIME | --auto-created-reservations-duration=AUTO_CREATED_RESERVATIONS_DURATION] [--clear-name-prefix | --name-prefix=NAME_PREFIX] [--clear-share-settings @@ -37,9 +37,11 @@ POSITIONAL ARGUMENTS Name of the future reservation to update. FLAGS - --auto-delete-auto-created-reservations + --[no-]auto-delete-auto-created-reservations If specified, the auto-created reservations for a future reservation are deleted at the end time (default) or at a specified delete time. + Use --auto-delete-auto-created-reservations to enable and + --no-auto-delete-auto-created-reservations to disable. --description=DESCRIPTION An optional description of the reservation to create. diff --git a/gcloud/alpha/compute/project-info/update b/gcloud/alpha/compute/project-info/update index bd8bec2ec..b2e5ba3a2 100644 --- a/gcloud/alpha/compute/project-info/update +++ b/gcloud/alpha/compute/project-info/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud alpha compute project-info update - [--default-network-tier=DEFAULT_NETWORK_TIER] [GCLOUD_WIDE_FLAG ...] + [--default-network-tier=DEFAULT_NETWORK_TIER] + [--managed-protection-tier=MANAGED_PROTECTION_TIER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute project-info update is used to update a @@ -15,6 +17,10 @@ FLAGS The default network tier to assign to the project. DEFAULT_NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. + --managed-protection-tier=MANAGED_PROTECTION_TIER + The maanged protection tier to assign to the project. + MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_MONTHLY. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/alpha/compute/target-http-proxies/create b/gcloud/alpha/compute/target-http-proxies/create index 9e2659a44..9dfe22b3d 100644 --- a/gcloud/alpha/compute/target-http-proxies/create +++ b/gcloud/alpha/compute/target-http-proxies/create @@ -54,7 +54,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external Application load balancer, the minimum allowed + For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. --proxy-bind diff --git a/gcloud/alpha/compute/target-http-proxies/update b/gcloud/alpha/compute/target-http-proxies/update index 96aa31f0e..9f50aa0e8 100644 --- a/gcloud/alpha/compute/target-http-proxies/update +++ b/gcloud/alpha/compute/target-http-proxies/update @@ -52,7 +52,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external Application load balancer, the minimum + seconds. For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/alpha/compute/target-https-proxies/create b/gcloud/alpha/compute/target-https-proxies/create index e25906de8..2c265ec25 100644 --- a/gcloud/alpha/compute/target-https-proxies/create +++ b/gcloud/alpha/compute/target-https-proxies/create @@ -83,7 +83,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external Application load balancer, the minimum allowed + For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. --proxy-bind @@ -130,8 +130,8 @@ OPTIONAL FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the HTTPS proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target HTTPS proxy. + and load balancers that are using the HTTPS proxy. The SSL policy must + exist and cannot be deleted while referenced by a target HTTPS proxy. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-https-proxies/update b/gcloud/alpha/compute/target-https-proxies/update index 533528e44..bd916f6bf 100644 --- a/gcloud/alpha/compute/target-https-proxies/update +++ b/gcloud/alpha/compute/target-https-proxies/update @@ -172,7 +172,7 @@ FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external Application load balancer, the minimum + seconds. For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. @@ -211,8 +211,9 @@ FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the HTTPS proxy load balancer. The SSL policy must exist and - cannot be deleted while referenced by a target HTTPS proxy. + and load balancers that are using the HTTPS proxy. The SSL policy + must exist and cannot be deleted while referenced by a target HTTPS + proxy. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-ssl-proxies/create b/gcloud/alpha/compute/target-ssl-proxies/create index 1e1da3348..b19a14107 100644 --- a/gcloud/alpha/compute/target-ssl-proxies/create +++ b/gcloud/alpha/compute/target-ssl-proxies/create @@ -76,8 +76,8 @@ OPTIONAL FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the SSL proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target SSL proxy. + and load balancers that are using the SSL proxy. The SSL policy must + exist and cannot be deleted while referenced by a target SSL proxy. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-ssl-proxies/help b/gcloud/alpha/compute/target-ssl-proxies/help index 74779b40e..b5a2a965d 100644 --- a/gcloud/alpha/compute/target-ssl-proxies/help +++ b/gcloud/alpha/compute/target-ssl-proxies/help @@ -7,11 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List, create, and delete target SSL target proxies for SSL Proxy - Load Balancing. + (ALPHA) List, create, and delete target SSL target proxies for proxy + Network Load Balancers. - For more information about target SSL proxies, see the SSL proxy load - balancer documentation (https://cloud.google.com/load-balancing/docs/ssl/). + For more information about target SSL proxies, see the proxy Network Load + Balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). See also: Target SSL proxies API (https://cloud.google.com/compute/docs/reference/rest/v1/targetSslProxies). diff --git a/gcloud/alpha/compute/target-ssl-proxies/update b/gcloud/alpha/compute/target-ssl-proxies/update index bc358e74f..bfec7e180 100644 --- a/gcloud/alpha/compute/target-ssl-proxies/update +++ b/gcloud/alpha/compute/target-ssl-proxies/update @@ -47,8 +47,8 @@ FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the SSL proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target SSL proxy. + and load balancers that are using the SSL proxy. The SSL policy must + exist and cannot be deleted while referenced by a target SSL proxy. At most one of these can be specified: diff --git a/gcloud/alpha/compute/target-tcp-proxies/help b/gcloud/alpha/compute/target-tcp-proxies/help index a524f1e50..1b82b487d 100644 --- a/gcloud/alpha/compute/target-tcp-proxies/help +++ b/gcloud/alpha/compute/target-tcp-proxies/help @@ -7,11 +7,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List, create, and delete target TCP proxies for TCP Proxy Load - Balancing. + (ALPHA) List, create, and delete target TCP proxies for proxy Network Load + Balancers. - For more information about target TCP proxies, see the TCP proxy load - balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). + For more information about target TCP proxies, see the proxy Network Load + Balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). See also: Target TCP proxies API (https://cloud.google.com/compute/docs/reference/rest/v1/targetTcpProxies). diff --git a/gcloud/alpha/compute/tpus/queued-resources/help b/gcloud/alpha/compute/tpus/queued-resources/help index d74f73932..6ccbc071d 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/help +++ b/gcloud/alpha/compute/tpus/queued-resources/help @@ -31,6 +31,12 @@ COMMANDS reset (ALPHA) Reset a Queued Resource. + scp + (ALPHA) Copy files to and from a Cloud TPU Queued Resource via SCP. + + ssh + (ALPHA) SSH into a Cloud TPU Queued Resource's node(s). + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/compute/tpus/queued-resources/scp b/gcloud/alpha/compute/tpus/queued-resources/scp new file mode 100644 index 000000000..4d4c03382 --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/scp @@ -0,0 +1,201 @@ +NAME + gcloud alpha compute tpus queued-resources scp - copy files to and from a + Cloud TPU Queued Resource via SCP + +SYNOPSIS + gcloud alpha compute tpus queued-resources scp [[USER@]INSTANCE:]SRC + [[[USER@]INSTANCE:]SRC ...] [[USER@]INSTANCE:]DEST + [--batch-size=BATCH_SIZE; default="all"] [--compress] [--dry-run] + [--force-key-file-overwrite] [--node=NODE; default="0"] [--plain] + [--recurse] [--scp-flag=SCP_FLAG] [--ssh-key-file=SSH_KEY_FILE] + [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] + [--worker=WORKER; default="0"] [--zone=ZONE] + [--internal-ip | --tunnel-through-iap] + [--ssh-key-expiration=SSH_KEY_EXPIRATION + | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Copy files to and from a Cloud TPU Queued Resource via SCP. + +EXAMPLES + To copy a file (for example, a text file in the local home directory) to a + Cloud Queued Resource, run: + + $ gcloud alpha compute tpus queued-resources scp ~/my-file my-qr: + + To copy a file into all nodes and workers in a Cloud TPU Queued Resource, + run: + + $ gcloud alpha compute tpus queued-resources scp ~/my-file my-qr: \ + --worker=all --node=all + + To copy a file into all workers in the first node of a Cloud TPU Queued + Resource, run: + + $ gcloud alpha compute tpus queued-resources scp ~/my-file my-qr: \ + --worker=all + + To copy a file from a Cloud TPU Queued Resource to the home directory of + the local computer, run: + + $ gcloud alpha compute tpus queued-resources scp my-qr:~/my-file ~/ + + To copy all files in a folder to a Cloud TPU Queued Resource, run: + + $ gcloud alpha compute tpus queued-resources scp ~/my-folder/ \ + my-qr: --recurse + +POSITIONAL ARGUMENTS + [[USER@]INSTANCE:]SRC [[[USER@]INSTANCE:]SRC ...] + Specifies the files to copy. + + [[USER@]INSTANCE:]DEST + Specifies a destination for the source files. + +FLAGS + --batch-size=BATCH_SIZE; default="all" + Batch size for simultaneous command execution. When using a + comma-separated list (e.g. '1,4,6') or a range (e.g. '1-3') or ``all`` + keyword in --worker flag, it executes the command concurrently in + groups of the batch size. This flag takes a value greater than 0 to + specify the batch size to control the concurrent connections that can + be established with the TPU workers, or the special keyword ``all`` to + allow the concurrent command executions on all the specified workers in + --worker flag. Maximum value of this flag should not be more than the + number of specified workers, otherwise the value will be treated as + ``--batch-size=all``. + + --compress + Enable compression. + + --dry-run + Print the equivalent scp/ssh command that would be run to stdout, + instead of executing it. + + --force-key-file-overwrite + If enabled, the gcloud command-line tool will regenerate and overwrite + the files associated with a broken SSH key without asking for + confirmation in both interactive and non-interactive environments. + + If disabled, the files associated with a broken SSH key will not be + regenerated and will fail in both interactive and non-interactive + environments. + + --node=NODE; default="0" + TPU node(s) to connect to. The supported value is a single 0-based + index of the node(s) in the case of a TPU Pod. It additionally supports + a comma-separated list (e.g. '1,4,6'), range (e.g. '1-3'), or special + keyword ``all" to run the command concurrently on each of the specified + node(s). + + Note that when targeting multiple nodes, you should run 'ssh-add' with + your private key prior to executing the gcloud command. Default: + 'ssh-add ~/.ssh/google_compute_engine'. + + --plain + Suppress the automatic addition of ssh(1)/scp(1) flags. This flag is + useful if you want to take care of authentication yourself or use + specific ssh/scp features. + + --recurse + Upload directories recursively. + + --scp-flag=SCP_FLAG + Additional flags to be passed to scp(1). This flag may be repeated. + + --ssh-key-file=SSH_KEY_FILE + The path to the SSH key file. By default, this is + ~/.ssh/google_compute_engine. + + --strict-host-key-checking=STRICT_HOST_KEY_CHECKING + Override the default behavior of StrictHostKeyChecking for the + connection. By default, StrictHostKeyChecking is set to 'no' the first + time you connect to an instance, and will be set to 'yes' for all + subsequent connections. STRICT_HOST_KEY_CHECKING must be one of: yes, + no, ask. + + --worker=WORKER; default="0" + TPU worker to connect to. The supported value is a single 0-based index + of the worker in the case of a TPU Pod. When also using the --command + flag, it additionally supports a comma-separated list (e.g. '1,4,6'), + range (e.g. '1-3'), or special keyword ``all" to run the command + concurrently on each of the specified workers. + + Note that when targeting multiple workers, you should run 'ssh-add' + with your private key prior to executing the gcloud command. Default: + 'ssh-add ~/.ssh/google_compute_engine'. + + --zone=ZONE + Zone of the tpu to scp. If not specified and the compute/zone property + isn't set, you might be prompted to select a zone (interactive mode + only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + + At most one of these can be specified: + + --internal-ip + Connect to TPU VMs using their internal IP addresses rather than + their external IP addresses. Use this to connect from a Google + Compute Engine VM to a TPU VM on the same VPC network, or between two + peered VPC networks. + + --tunnel-through-iap + Tunnel the SSH connection through Cloud Identity-Aware Proxy for TCP + forwarding. + + This flag must be specified to attempt to connect via IAP tunneling. + If it is not set, and connection to a Cloud TPU VM without external + IP address is attempted from outside the network, then the command + will fail. + + To use IAP tunneling, there must be firewall access to the SSH port + for the IAP TCP IP address range for the network the TPU is created + in. See the user guide + (https://cloud.google.com/iap/docs/using-tcp-forwarding) for more + details. + + To learn more, see the IAP for TCP forwarding documentation + (https://cloud.google.com/iap/docs/tcp-forwarding-overview). + + At most one of these can be specified: + + --ssh-key-expiration=SSH_KEY_EXPIRATION + The time when the ssh key will be valid until, such as + "2017-08-29T18:52:51.142Z." This is only valid if the instance is not + using OS Login. See $ gcloud topic datetimes for information on time + formats. + + --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER + The maximum length of time an SSH key is valid for once created and + installed, e.g. 2m for 2 minutes. See $ gcloud topic datetimes for + information on duration formats. + +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 + 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. + diff --git a/gcloud/alpha/compute/tpus/queued-resources/ssh b/gcloud/alpha/compute/tpus/queued-resources/ssh new file mode 100644 index 000000000..4a4659667 --- /dev/null +++ b/gcloud/alpha/compute/tpus/queued-resources/ssh @@ -0,0 +1,238 @@ +NAME + gcloud alpha compute tpus queued-resources ssh - SSH into a Cloud TPU + Queued Resource's node(s) + +SYNOPSIS + gcloud alpha compute tpus queued-resources ssh [USER@]QR + [--batch-size=BATCH_SIZE; default="all"] [--dry-run] + [--force-key-file-overwrite] [--node=NODE; default="0"] [--plain] + [--ssh-flag=SSH_FLAG] [--ssh-key-file=SSH_KEY_FILE] + [--strict-host-key-checking=STRICT_HOST_KEY_CHECKING] + [--worker=WORKER; default="0"] [--zone=ZONE] + [--command=COMMAND : --output-directory=OUTPUT_DIRECTORY] + [--internal-ip | --tunnel-through-iap] + [--ssh-key-expiration=SSH_KEY_EXPIRATION + | --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER] [GCLOUD_WIDE_FLAG ...] + [-- SSH_ARGS ...] + +DESCRIPTION + (ALPHA) Send SSH commands to a Cloud TPU Queued Resource. + +EXAMPLES + To run an SSH command in a Cloud TPU Queued Resource's first node and first + worker (for example, to print the time since last boot), run: + + $ gcloud alpha compute tpus queued-resources ssh my-qr \ + --command="last boot" + + To run the same command in all nodes and workers in a Cloud TPU Queued + Resource simultaneously, run: + + $ gcloud alpha compute tpus queued-resources ssh my-qr \ + --command="last boot" --worker=all --node=all + + To run the same command in all nodes and workers in a Cloud TPU Queued + Resource but batching the request in groups of 4, run: + + $ gcloud alpha compute tpus queued-resources ssh my-qr \ + --command="last boot" --worker=all --node=all --batch-size=4 + +POSITIONAL ARGUMENTS + [USER@]QR + Specifies the Cloud TPU Queued Resource to send SSH command to. + + USER specifies the username with which to SSH. If omitted, the user + login name is used. + + QR specifies the name of the Cloud TPU Queued Resource to send SSH + command to. + + [-- SSH_ARGS ...] + Flags and positionals passed to the underlying ssh implementation. + + The '--' argument must be specified between gcloud specific args on the + left and SSH_ARGS on the right. Example: + + $ gcloud alpha compute tpus queued-resources ssh example-instance \ + --zone=us-central1-a -- -vvv -L 80:%TPU%:80 + +FLAGS + --batch-size=BATCH_SIZE; default="all" + Batch size for simultaneous command execution. When using a + comma-separated list (e.g. '1,4,6') or a range (e.g. '1-3') or ``all`` + keyword in --worker flag, it executes the command concurrently in + groups of the batch size. This flag takes a value greater than 0 to + specify the batch size to control the concurrent connections that can + be established with the TPU workers, or the special keyword ``all`` to + allow the concurrent command executions on all the specified workers in + --worker flag. Maximum value of this flag should not be more than the + number of specified workers, otherwise the value will be treated as + ``--batch-size=all``. + + --dry-run + Print the equivalent scp/ssh command that would be run to stdout, + instead of executing it. + + --force-key-file-overwrite + If enabled, the gcloud command-line tool will regenerate and overwrite + the files associated with a broken SSH key without asking for + confirmation in both interactive and non-interactive environments. + + If disabled, the files associated with a broken SSH key will not be + regenerated and will fail in both interactive and non-interactive + environments. + + --node=NODE; default="0" + TPU node(s) to connect to. The supported value is a single 0-based + index of the node(s) in the case of a TPU Pod. When also using the + --command flag, it additionally supports a comma-separated list (e.g. + '1,4,6'), range (e.g. '1-3'), or special keyword ``all" to run the + command concurrently on each of the specified node(s). + + Note that when targeting multiple nodes, you should run 'ssh-add' with + your private key prior to executing the gcloud command. Default: + 'ssh-add ~/.ssh/google_compute_engine'. + + --plain + Suppress the automatic addition of ssh(1)/scp(1) flags. This flag is + useful if you want to take care of authentication yourself or use + specific ssh/scp features. + + --ssh-flag=SSH_FLAG + Additional flags to be passed to ssh(1). It is recommended that flags + be passed using an assignment operator and quotes. Example: + + $ gcloud alpha compute tpus queued-resources ssh example-instance \ + --zone=us-central1-a --ssh-flag="-vvv" \ + --ssh-flag="-L 80:localhost:80" + + This flag will replace occurences of %USER% and %TPU% with their + dereferenced values. For example, passing ``80:%TPU%:80`` into the flag + is equivalent to passing 80:162.222.181.197:80 to ssh(1) if the + external IP address of 'example-instance' is 162.222.181.197. + + If connecting to the instance's external IP, then %TPU% is replaced + with that, otherwise it is replaced with the internal IP. + + --ssh-key-file=SSH_KEY_FILE + The path to the SSH key file. By default, this is + ~/.ssh/google_compute_engine. + + --strict-host-key-checking=STRICT_HOST_KEY_CHECKING + Override the default behavior of StrictHostKeyChecking for the + connection. By default, StrictHostKeyChecking is set to 'no' the first + time you connect to an instance, and will be set to 'yes' for all + subsequent connections. STRICT_HOST_KEY_CHECKING must be one of: yes, + no, ask. + + --worker=WORKER; default="0" + TPU worker to connect to. The supported value is a single 0-based index + of the worker in the case of a TPU Pod. When also using the --command + flag, it additionally supports a comma-separated list (e.g. '1,4,6'), + range (e.g. '1-3'), or special keyword ``all" to run the command + concurrently on each of the specified workers. + + Note that when targeting multiple workers, you should run 'ssh-add' + with your private key prior to executing the gcloud command. Default: + 'ssh-add ~/.ssh/google_compute_engine'. + + --zone=ZONE + Zone of the tpu to ssh. If not specified and the compute/zone property + isn't set, you might be prompted to select a zone (interactive mode + only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + + These arguments are used to run commands using SSH. + + --command=COMMAND + Command to run on the Cloud TPU VM. + + Runs the command on the target Cloud TPU Queued Resource's nodes and + then exits. + + Note: in the case of a TPU Pod, it will only run the command in the + workers specified with the --worker flag (defaults to worker all if + not set). + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --output-directory=OUTPUT_DIRECTORY + Path to the directory to output the logs of the commands. + + The path can be relative or absolute. The directory must already + exist. + + If not specified, standard output will be used. + + The logs will be written in files named {WORKER_ID}.log. For example: + "2.log". + + At most one of these can be specified: + + --internal-ip + Connect to TPU VMs using their internal IP addresses rather than + their external IP addresses. Use this to connect from a Google + Compute Engine VM to a TPU VM on the same VPC network, or between two + peered VPC networks. + + --tunnel-through-iap + Tunnel the SSH connection through Cloud Identity-Aware Proxy for TCP + forwarding. + + This flag must be specified to attempt to connect via IAP tunneling. + If it is not set, and connection to a Cloud TPU VM without external + IP address is attempted from outside the network, then the command + will fail. + + To use IAP tunneling, there must be firewall access to the SSH port + for the IAP TCP IP address range for the network the TPU is created + in. See the user guide + (https://cloud.google.com/iap/docs/using-tcp-forwarding) for more + details. + + To learn more, see the IAP for TCP forwarding documentation + (https://cloud.google.com/iap/docs/tcp-forwarding-overview). + + At most one of these can be specified: + + --ssh-key-expiration=SSH_KEY_EXPIRATION + The time when the ssh key will be valid until, such as + "2017-08-29T18:52:51.142Z." This is only valid if the instance is not + using OS Login. See $ gcloud topic datetimes for information on time + formats. + + --ssh-key-expire-after=SSH_KEY_EXPIRE_AFTER + The maximum length of time an SSH key is valid for once created and + installed, e.g. 2m for 2 minutes. See $ gcloud topic datetimes for + information on duration formats. + +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 + 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. + diff --git a/gcloud/alpha/compute/tpus/tpu-vm/create b/gcloud/alpha/compute/tpus/tpu-vm/create index 98d95ee3e..2f82c5cd9 100644 --- a/gcloud/alpha/compute/tpus/tpu-vm/create +++ b/gcloud/alpha/compute/tpus/tpu-vm/create @@ -3,9 +3,9 @@ NAME SYNOPSIS gcloud alpha compute tpus tpu-vm create (TPU : --zone=ZONE) - --version=VERSION [--async] [--data-disk=DATA_DISK] - [--description=DESCRIPTION] [--internal-ips] [--labels=[LABELS,...]] - [--metadata=[METADATA,...]] + --version=VERSION [--async] [--boot-disk=[BOOT_DISK,...]] + [--data-disk=DATA_DISK] [--description=DESCRIPTION] [--internal-ips] + [--labels=[LABELS,...]] [--metadata=[METADATA,...]] [--metadata-from-file=[METADATA_FROM_FILE,...]] [--network=NETWORK; default="default"] [--preemptible] [--range=RANGE] [--reserved] [--scopes=[SCOPES,...]] @@ -82,6 +82,24 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --boot-disk=[BOOT_DISK,...] + Specifies if the boot disk should be created in confidential-compute + mode. + + $ gcloud alpha compute tpus tpu-vm create \ + --boot-disk confidential-compute=True,kms-key= + + The following keys are allowed: + + confidential-compute + Create the boot disk in confidential compute mode, CMEK layer is + required and only applicable to HyperDisk series. + + kms-key + Specifies fully qualified Cloud KMS cryptokey name which will be + used to protect the disk. KMS cryptokey name format: + projects//locations//keyRings//cryptoKeys/ + --data-disk=DATA_DISK Additional data disks for the TPU VM. diff --git a/gcloud/alpha/config/get b/gcloud/alpha/config/get index 29d6ebd0e..b65dd69e0 100644 --- a/gcloud/alpha/config/get +++ b/gcloud/alpha/config/get @@ -414,6 +414,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 3c5ab1375..05cd0d215 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -446,6 +446,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 1c277f946..652d602c1 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -458,6 +458,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 3ff3c6f8a..3d10805df 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -461,6 +461,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index db8079087..bf8371b32 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -422,6 +422,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/alpha/container/bare-metal/clusters/create b/gcloud/alpha/container/bare-metal/clusters/create index 48309a4e6..ffe8d3087 100644 --- a/gcloud/alpha/container/bare-metal/clusters/create +++ b/gcloud/alpha/container/bare-metal/clusters/create @@ -42,7 +42,8 @@ SYNOPSIS [--description=DESCRIPTION] [--enable-application-logs] [--login-user=LOGIN_USER] [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, - ...]] [--validate-only] + ...]] [--upgrade-control-plane=UPGRADE_CONTROL_PLANE] + [--validate-only] [--container-runtime=CONTAINER_RUNTIME --max-pods-per-node=MAX_PODS_PER_NODE] [[(--island-mode-pod-address-cidr-blocks=POD_ADDRESS,[POD_ADDRESS,...] @@ -438,6 +439,24 @@ OPTIONAL FLAGS --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] IPv4 addresses to be placed into maintenance mode. + Upgrade policy for the cluster. + + --upgrade-control-plane=UPGRADE_CONTROL_PLANE + If not specified, worker node pools are upgraded with the control + plane. + + Examples: + + To upgrade control plane only and keep node pools version unchanged, + + $ gcloud alpha container bare-metal clusters create \ + --upgrade-control-plane=True + + To upgrade both control plane and node pools, + + $ gcloud alpha container bare-metal clusters create \ + --upgrade-control-plane=False + --validate-only If set, only validate the request, but do not actually perform the operation. diff --git a/gcloud/alpha/container/bare-metal/clusters/update b/gcloud/alpha/container/bare-metal/clusters/update index c4773360c..8f9c9841a 100644 --- a/gcloud/alpha/container/bare-metal/clusters/update +++ b/gcloud/alpha/container/bare-metal/clusters/update @@ -8,7 +8,8 @@ SYNOPSIS [--allow-missing] [--async] [--description=DESCRIPTION] [--enable-application-logs] [--login-user=LOGIN_USER] [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, - ...]] [--validate-only] [--version=VERSION] + ...]] [--upgrade-control-plane=UPGRADE_CONTROL_PLANE] + [--validate-only] [--version=VERSION] [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...] | --remove-annotations=[KEY1,KEY2,...]] [--api-server-args=[KEY=VALUE,...] @@ -119,6 +120,24 @@ FLAGS --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] IPv4 addresses to be placed into maintenance mode. + Upgrade policy for the cluster. + + --upgrade-control-plane=UPGRADE_CONTROL_PLANE + If not specified, worker node pools are upgraded with the control + plane. + + Examples: + + To upgrade control plane only and keep node pools version unchanged, + + $ gcloud alpha container bare-metal clusters update \ + --upgrade-control-plane=True + + To upgrade both control plane and node pools, + + $ gcloud alpha container bare-metal clusters update \ + --upgrade-control-plane=False + --validate-only If set, only validate the request, but do not actually perform the operation. diff --git a/gcloud/alpha/container/binauthz/policy/create b/gcloud/alpha/container/binauthz/policy/create new file mode 100644 index 000000000..294ab2bf3 --- /dev/null +++ b/gcloud/alpha/container/binauthz/policy/create @@ -0,0 +1,79 @@ +NAME + gcloud alpha container binauthz policy create - create a Binary + Authorization platform policy + +SYNOPSIS + gcloud alpha container binauthz policy create + (POLICY_RESOURCE_NAME : --platform=PLATFORM) --policy-file=POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create a policy for GKE in the current project: + + $ gcloud alpha container binauthz policy create my-policy \ + --platform=gke --policy-file=my_policy.yaml + + To create a policy for GKE in a specific project: + + $ gcloud alpha container binauthz policy create my-policy \ + --platform=gke --project=my-project-id \ + --policy-file=my_policy.yaml + + or + + $ gcloud alpha container binauthz policy create \ + /projects/my-project-id/platforms/gke/policies/my-policy \ + --policy-file=my_policy.yaml + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to create. The arguments + in this group can be used to specify the attributes of this 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +REQUIRED FLAGS + --policy-file=POLICY_FILE + The JSON or YAML file containing the new policy. + +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 + 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: + + $ gcloud beta container binauthz policy create + diff --git a/gcloud/alpha/container/binauthz/policy/delete b/gcloud/alpha/container/binauthz/policy/delete new file mode 100644 index 000000000..9b1ae2ba5 --- /dev/null +++ b/gcloud/alpha/container/binauthz/policy/delete @@ -0,0 +1,67 @@ +NAME + gcloud alpha container binauthz policy delete - delete a Binary + Authorization platform policy + +SYNOPSIS + gcloud alpha container binauthz policy delete + (POLICY_RESOURCE_NAME : --platform=PLATFORM) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a policy using its resource name: + + $ gcloud alpha container binauthz policy delete \ + projects/my_proj/platforms/gke/policies/policy1 + + To delete the same policy using flags: + + $ gcloud alpha container binauthz policy delete policy1 \ + --platform=gke --project=my_proj + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to delete. The arguments + in this group can be used to specify the attributes of this 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +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 + 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: + + $ gcloud beta container binauthz policy delete + diff --git a/gcloud/alpha/container/binauthz/policy/describe b/gcloud/alpha/container/binauthz/policy/describe new file mode 100644 index 000000000..e8a3f11e2 --- /dev/null +++ b/gcloud/alpha/container/binauthz/policy/describe @@ -0,0 +1,67 @@ +NAME + gcloud alpha container binauthz policy describe - describe a Binary + Authorization platform policy + +SYNOPSIS + gcloud alpha container binauthz policy describe + (POLICY_RESOURCE_NAME : --platform=PLATFORM) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe an existing policy using its resource name: + + $ gcloud alpha container binauthz policy describe \ + projects/my_proj/platforms/gke/policies/policy1 + + To describe the same policy using flags: + + $ gcloud alpha container binauthz policy describe policy1 \ + --platform=gke --project=my_proj + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to describe. The + arguments in this group can be used to specify the attributes of this + 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +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 + 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: + + $ gcloud beta container binauthz policy describe + diff --git a/gcloud/alpha/container/binauthz/policy/help b/gcloud/alpha/container/binauthz/policy/help index 18fd3ded2..d34b4ac77 100644 --- a/gcloud/alpha/container/binauthz/policy/help +++ b/gcloud/alpha/container/binauthz/policy/help @@ -19,6 +19,15 @@ COMMANDS add-iam-policy-binding (ALPHA) Add IAM policy binding to a Binary Authorization policy. + create + (ALPHA) Create a Binary Authorization platform policy. + + delete + (ALPHA) Delete a Binary Authorization platform policy. + + describe + (ALPHA) Describe a Binary Authorization platform policy. + export (ALPHA) Export the Binary Authorization policy for the current project. @@ -31,12 +40,18 @@ COMMANDS import (ALPHA) Import a Binary Authorization policy to the current project. + list + (ALPHA) List Binary Authorization platform policies. + remove-iam-policy-binding (ALPHA) Remove IAM policy binding of a Binary Authorization policy. set-iam-policy (ALPHA) Set the IAM policy for a Binary Authorization policy. + update + (ALPHA) Update a Binary Authorization platform policy. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/container/binauthz/policy/list b/gcloud/alpha/container/binauthz/policy/list new file mode 100644 index 000000000..28c3b19d4 --- /dev/null +++ b/gcloud/alpha/container/binauthz/policy/list @@ -0,0 +1,91 @@ +NAME + gcloud alpha container binauthz policy list - list Binary Authorization + platform policies + +SYNOPSIS + gcloud alpha container binauthz policy list PLATFORM_RESOURCE_NAME + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list the policies for GKE in the current project: + + $ gcloud alpha container binauthz policy list gke + + To list the policies for GKE in a specific project: + + $ gcloud alpha container binauthz policy list gke \ + --project=my-project-id + + or + + $ gcloud alpha container binauthz policy list \ + projects/my-project-id/gke + +POSITIONAL ARGUMENTS + Platform resource - The platform whose policies 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 platform_resource_name on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + PLATFORM_RESOURCE_NAME + ID of the platform or fully qualified identifier for the platform. + + To set the platform attribute: + ▸ provide the argument platform_resource_name on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 + 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: + + $ gcloud beta container binauthz policy list + diff --git a/gcloud/alpha/container/binauthz/policy/update b/gcloud/alpha/container/binauthz/policy/update new file mode 100644 index 000000000..9abce890a --- /dev/null +++ b/gcloud/alpha/container/binauthz/policy/update @@ -0,0 +1,73 @@ +NAME + gcloud alpha container binauthz policy update - update a Binary + Authorization platform policy + +SYNOPSIS + gcloud alpha container binauthz policy update + (POLICY_RESOURCE_NAME : --platform=PLATFORM) --policy-file=POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To update an existing policy using its resource name: + + $ gcloud alpha container binauthz policy update \ + projects/my_proj/platforms/gke/policies/policy1 \ + --policy-file=policy1.json + + To update the same policy using flags: + + $ gcloud alpha container binauthz policy update policy1 \ + --platform=gke --project=my_proj --policy-file=policy1.json + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to update. The arguments + in this group can be used to specify the attributes of this 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +REQUIRED FLAGS + --policy-file=POLICY_FILE + The JSON or YAML file containing the new policy. + +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 + 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: + + $ gcloud beta container binauthz policy update + diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index a627edd23..b24b335e7 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -872,7 +872,7 @@ FLAGS 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]. + [TIER_UNSPECIFIED,TIER_1]. See https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration @@ -1140,6 +1140,9 @@ FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -1170,6 +1173,19 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. diff --git a/gcloud/alpha/container/clusters/update b/gcloud/alpha/container/clusters/update index 79dce57be..84e0c3173 100644 --- a/gcloud/alpha/container/clusters/update +++ b/gcloud/alpha/container/clusters/update @@ -426,7 +426,7 @@ REQUIRED FLAGS 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]. + [TIER_UNSPECIFIED,TIER_1]. See https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration diff --git a/gcloud/alpha/container/fleet/memberships/bindings/create b/gcloud/alpha/container/fleet/memberships/bindings/create index f37efd663..a04c41426 100644 --- a/gcloud/alpha/container/fleet/memberships/bindings/create +++ b/gcloud/alpha/container/fleet/memberships/bindings/create @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud alpha container fleet memberships bindings create - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -73,32 +72,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Membership Binding is created for all the Scopes in the Fleet for - given Membership. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --labels=[KEY=VALUE,...] diff --git a/gcloud/alpha/container/fleet/memberships/bindings/update b/gcloud/alpha/container/fleet/memberships/bindings/update index 626ba324d..bf8f52824 100644 --- a/gcloud/alpha/container/fleet/memberships/bindings/update +++ b/gcloud/alpha/container/fleet/memberships/bindings/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha container fleet memberships bindings update - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -74,32 +74,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Bindings for all the membership related scopes in the fleet would be - updated. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --update-labels=[KEY=VALUE,...] diff --git a/gcloud/alpha/container/hub/memberships/bindings/create b/gcloud/alpha/container/hub/memberships/bindings/create index e310af684..754177485 100644 --- a/gcloud/alpha/container/hub/memberships/bindings/create +++ b/gcloud/alpha/container/hub/memberships/bindings/create @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud alpha container hub memberships bindings create - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) This command can fail for the following reasons: @@ -73,32 +72,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Membership Binding is created for all the Scopes in the Fleet for - given Membership. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --labels=[KEY=VALUE,...] diff --git a/gcloud/alpha/container/hub/memberships/bindings/update b/gcloud/alpha/container/hub/memberships/bindings/update index 280a4be9f..76367d8f7 100644 --- a/gcloud/alpha/container/hub/memberships/bindings/update +++ b/gcloud/alpha/container/hub/memberships/bindings/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha container hub memberships bindings update - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -74,32 +74,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Bindings for all the membership related scopes in the fleet would be - updated. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --update-labels=[KEY=VALUE,...] diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index e7ce337ae..9bc986b0a 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -46,7 +46,7 @@ SYNOPSIS batch-soak-duration=BATCH_SOAK_DURATION,...]] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] - [--windows-os-version=WINDOWS_OS_VERSION] + [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] [--workload-metadata=WORKLOAD_METADATA] [--create-pod-ipv4-range=[KEY=VALUE,...] | --pod-ipv4-range=NAME] [--enable-autoscaling --location-policy=LOCATION_POLICY @@ -609,6 +609,9 @@ FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -639,6 +642,19 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. @@ -659,6 +675,12 @@ FLAGS The number of visible threads per physical core for each node. To disable simultaneous multithreading (SMT) set this to 1. + --tpu-topology=TPU_TOPOLOGY + The desired physical topology for the PodSlice. + + $ gcloud alpha container node-pools create node-pool-1 \ + --cluster=example-cluster --tpu-topology + --windows-os-version=WINDOWS_OS_VERSION Specifies the Windows Server Image to use when creating a Windows node pool. Valid variants can be "ltsc2019", "ltsc2022". It means using diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 502024c49..6753a767d 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -12,18 +12,18 @@ SYNOPSIS | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION - | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning - --enable-autoscaling --location-policy=LOCATION_POLICY - --max-nodes=MAX_NODES --min-nodes=MIN_NODES - --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES - | --enable-autorepair --enable-autoupgrade - | --enable-blue-green-upgrade --enable-surge-upgrade - --max-surge-upgrade=MAX_SURGE_UPGRADE + | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade + --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE --node-pool-soak-duration=NODE_POOL_SOAK_DURATION --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, - batch-soak-duration=BATCH_SOAK_DURATION,...]) [--async] + batch-soak-duration=BATCH_SOAK_DURATION,...] + | --enable-autoprovisioning --enable-autoscaling + --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES + | --enable-autorepair --enable-autoupgrade) [--async] [--cluster=CLUSTER] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -157,6 +157,9 @@ REQUIRED FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -190,6 +193,19 @@ REQUIRED FLAGS tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. @@ -250,6 +266,70 @@ REQUIRED FLAGS security improvements. This feature is scheduled to be deprecated in the future and later removed. + Upgrade settings + + --enable-blue-green-upgrade + Changes node pool upgrade strategy to blue-green upgrade. + + --enable-surge-upgrade + Changes node pool upgrade strategy to surge upgrade. + + --max-surge-upgrade=MAX_SURGE_UPGRADE + Number of extra (surge) nodes to be created on each upgrade of the + node pool. + + Specifies the number of extra (surge) nodes to be created during + this node pool's upgrades. For example, running the following + command will result in creating an extra node each time the node + pool is upgraded: + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster --max-surge-upgrade=1 \ + --max-unavailable-upgrade=0 + + Must be used in conjunction with '--max-unavailable-upgrade'. + + --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE + Number of nodes that can be unavailable at the same time on each + upgrade of the node pool. + + Specifies the number of nodes that can be unavailable at the same + time during this node pool's upgrades. For example, assume the node + pool has 5 nodes, running the following command will result in + having 3 nodes being upgraded in parallel (1 + 2), but keeping + always at least 3 (5 - 2) available each time the node pool is + upgraded: + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster --max-surge-upgrade=1 \ + --max-unavailable-upgrade=2 + + Must be used in conjunction with '--max-surge-upgrade'. + + --node-pool-soak-duration=NODE_POOL_SOAK_DURATION + Time in seconds to be spent waiting during blue-green upgrade + before deleting the blue pool and completing the upgrade. + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster --node-pool-soak-duration=600s + + --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...] + Standard rollout policy options for blue-green upgrade. + + Batch sizes are specified by one of, batch-node-count or + batch-percent. The duration between batches is specified by + batch-soak-duration. + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --standard-rollout-policy=batch-node-count=3,\ + batch-soak-duration=60s + + $ gcloud alpha container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --standard-rollout-policy=batch-percent=0.3,\ + batch-soak-duration=60s + Cluster autoscaling --enable-autoprovisioning @@ -328,70 +408,6 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades for more info. - Upgrade settings - - --enable-blue-green-upgrade - Changes node pool upgrade strategy to blue-green upgrade. - - --enable-surge-upgrade - Changes node pool upgrade strategy to surge upgrade. - - --max-surge-upgrade=MAX_SURGE_UPGRADE - Number of extra (surge) nodes to be created on each upgrade of the - node pool. - - Specifies the number of extra (surge) nodes to be created during - this node pool's upgrades. For example, running the following - command will result in creating an extra node each time the node - pool is upgraded: - - $ gcloud alpha container node-pools update node-pool-1 \ - --cluster=example-cluster --max-surge-upgrade=1 \ - --max-unavailable-upgrade=0 - - Must be used in conjunction with '--max-unavailable-upgrade'. - - --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE - Number of nodes that can be unavailable at the same time on each - upgrade of the node pool. - - Specifies the number of nodes that can be unavailable at the same - time during this node pool's upgrades. For example, assume the node - pool has 5 nodes, running the following command will result in - having 3 nodes being upgraded in parallel (1 + 2), but keeping - always at least 3 (5 - 2) available each time the node pool is - upgraded: - - $ gcloud alpha container node-pools update node-pool-1 \ - --cluster=example-cluster --max-surge-upgrade=1 \ - --max-unavailable-upgrade=2 - - Must be used in conjunction with '--max-surge-upgrade'. - - --node-pool-soak-duration=NODE_POOL_SOAK_DURATION - Time in seconds to be spent waiting during blue-green upgrade - before deleting the blue pool and completing the upgrade. - - $ gcloud alpha container node-pools update node-pool-1 \ - --cluster=example-cluster --node-pool-soak-duration=600s - - --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...] - Standard rollout policy options for blue-green upgrade. - - Batch sizes are specified by one of, batch-node-count or - batch-percent. The duration between batches is specified by - batch-soak-duration. - - $ gcloud alpha container node-pools update node-pool-1 \ - --cluster=example-cluster \ - --standard-rollout-policy=batch-node-count=3,\ - batch-soak-duration=60s - - $ gcloud alpha container node-pools update node-pool-1 \ - --cluster=example-cluster \ - --standard-rollout-policy=batch-percent=0.3,\ - batch-soak-duration=60s - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/alpha/container/vmware/admin-clusters/help b/gcloud/alpha/container/vmware/admin-clusters/help index cc0a498ad..8f75f839f 100644 --- a/gcloud/alpha/container/vmware/admin-clusters/help +++ b/gcloud/alpha/container/vmware/admin-clusters/help @@ -25,6 +25,9 @@ COMMANDS list (ALPHA) List Anthos on VMware admin clusters. + unenroll + (ALPHA) Unenroll an Anthos on VMware admin cluster. + update (ALPHA) Update an Anthos on VMware admin cluster. diff --git a/gcloud/alpha/container/vmware/admin-clusters/unenroll b/gcloud/alpha/container/vmware/admin-clusters/unenroll new file mode 100644 index 000000000..a7b73bb3b --- /dev/null +++ b/gcloud/alpha/container/vmware/admin-clusters/unenroll @@ -0,0 +1,81 @@ +NAME + gcloud alpha container vmware admin-clusters unenroll - unenroll an Anthos + on VMware admin cluster + +SYNOPSIS + gcloud alpha container vmware admin-clusters unenroll + (ADMIN_CLUSTER : --location=LOCATION) [--allow-missing] [--async] + [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Unenroll an Anthos on VMware admin cluster. + +EXAMPLES + To unenroll an admin cluster named my-cluster managed in location us-west1, + run: + + $ gcloud alpha container vmware admin-clusters unenroll my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster to unenroll The arguments in this + group can be used to specify the attributes of this 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 admin_cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + ADMIN_CLUSTER + ID of the admin_cluster or fully qualified identifier for the + admin_cluster. + + To set the admin_cluster attribute: + ▸ provide the argument admin_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location for the admin_cluster. + + To set the location attribute: + ▸ provide the argument admin_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +FLAGS + --allow-missing + If set, and the VMware Cluster is not found, the request will succeed + but no action will be taken on the server and return a completed LRO. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + +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 + 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: + + $ gcloud beta container vmware admin-clusters unenroll + diff --git a/gcloud/alpha/deploy/targets/rollback b/gcloud/alpha/deploy/targets/rollback index 193692ffe..914eea888 100644 --- a/gcloud/alpha/deploy/targets/rollback +++ b/gcloud/alpha/deploy/targets/rollback @@ -6,8 +6,9 @@ SYNOPSIS gcloud alpha deploy targets rollback (TARGET : --region=REGION) --delivery-pipeline=DELIVERY_PIPELINE [--annotations=[KEY=VALUE,...]] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [--release=RELEASE] [--rollout-id=ROLLOUT_ID] - [--starting-phase-id=STARTING_PHASE_ID] [GCLOUD_WIDE_FLAG ...] + [--release=RELEASE] [--rollback-of-rollout=ROLLBACK_OF_ROLLOUT] + [--rollout-id=ROLLOUT_ID] [--starting-phase-id=STARTING_PHASE_ID] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) If release is not specified, the command rollbacks the target with @@ -86,6 +87,19 @@ OPTIONAL FLAGS --release=RELEASE Name of the release to rollback to. + --rollback-of-rollout=ROLLBACK_OF_ROLLOUT + If set, this validates whether the rollout name specified by the flag + matches the rollout on the target. + + Examples: + + Validate that test-rollout is the rollout to rollback on the target. + + $ gcloud alpha deploy targets rollback \ + --rollback-of-rollout=projects/test-project/locations/\ + us-central1/deliveryPipelines/test-pipeline/releases/test-release/\ + rollouts/test-rollout + --rollout-id=ROLLOUT_ID ID to assign to the generated rollout for promotion. diff --git a/gcloud/alpha/dns/record-sets/create b/gcloud/alpha/dns/record-sets/create index 9d69eb411..847dd51c7 100644 --- a/gcloud/alpha/dns/record-sets/create +++ b/gcloud/alpha/dns/record-sets/create @@ -130,8 +130,9 @@ REQUIRED FLAGS semicolon-delimited list of the format "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP address or a reference to a forwarding rule of the format - FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full - resource path of the forwarding rule. + "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@{region}", + "FORWARDING_RULE_NAME@global", or the full resource path of the + forwarding rule. Configuration for primary backup routing policy diff --git a/gcloud/alpha/dns/record-sets/update b/gcloud/alpha/dns/record-sets/update index 02d1ed5bf..31bd4184c 100644 --- a/gcloud/alpha/dns/record-sets/update +++ b/gcloud/alpha/dns/record-sets/update @@ -97,8 +97,9 @@ REQUIRED FLAGS semicolon-delimited list of the format "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP address or a reference to a forwarding rule of the format - FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full - resource path of the forwarding rule. + "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@{region}", + "FORWARDING_RULE_NAME@global", or the full resource path of the + forwarding rule. Configuration for primary backup routing policy diff --git a/gcloud/alpha/netapp/active-directories/create b/gcloud/alpha/netapp/active-directories/create index 889d1f7eb..817a61d16 100644 --- a/gcloud/alpha/netapp/active-directories/create +++ b/gcloud/alpha/netapp/active-directories/create @@ -17,11 +17,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Creates an AD (Active Directory) config for Cloud NetApp Volumes + (ALPHA) Creates an AD (Active Directory) config for Cloud NetApp Volumes. EXAMPLES The following command creates an AD named AD_NAME with the required - arguments + arguments: $ gcloud alpha netapp active-directories create AD_NAME \ --location=us-central1 --domain=example-domain.com \ diff --git a/gcloud/alpha/netapp/active-directories/delete b/gcloud/alpha/netapp/active-directories/delete index 16bdf883d..a5e578f3a 100644 --- a/gcloud/alpha/netapp/active-directories/delete +++ b/gcloud/alpha/netapp/active-directories/delete @@ -8,11 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Deletes an AD (Active Directory) config for Cloud NetApp Volumes + (ALPHA) Deletes an AD (Active Directory) config for Cloud NetApp Volumes. EXAMPLES The following command deletes an AD named AD_NAME with the required - arguments + arguments: $ gcloud alpha netapp active-directories delete AD_NAME \ --location=us-central1 diff --git a/gcloud/alpha/netapp/active-directories/describe b/gcloud/alpha/netapp/active-directories/describe index efefed6c9..c19881e35 100644 --- a/gcloud/alpha/netapp/active-directories/describe +++ b/gcloud/alpha/netapp/active-directories/describe @@ -7,11 +7,11 @@ SYNOPSIS (ACTIVE_DIRECTORY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describes an AD (Active Directory) config for Cloud NetApp Volumes + (ALPHA) Describes an AD (Active Directory) config for Cloud NetApp Volumes. EXAMPLES The following command describes an AD named AD_NAME with the required - arguments + arguments: $ gcloud alpha netapp active-directories describe AD_NAME \ --location=us-central1 diff --git a/gcloud/alpha/netapp/active-directories/list b/gcloud/alpha/netapp/active-directories/list index 78789bee4..cef629106 100644 --- a/gcloud/alpha/netapp/active-directories/list +++ b/gcloud/alpha/netapp/active-directories/list @@ -8,10 +8,10 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Lists AD (Active Directory) configs for Cloud NetApp Volumes + (ALPHA) Lists AD (Active Directory) configs for Cloud NetApp Volumes. EXAMPLES - The following command lists AD configs in the given project and location + The following command lists AD configs in the given project and location: $ gcloud alpha netapp active-directories list --location=us-central1 diff --git a/gcloud/alpha/netapp/active-directories/update b/gcloud/alpha/netapp/active-directories/update index 6135b4a85..b8aa22fc5 100644 --- a/gcloud/alpha/netapp/active-directories/update +++ b/gcloud/alpha/netapp/active-directories/update @@ -18,11 +18,11 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Updates AD (Active Directory) configs for Cloud NetApp Volumes + (ALPHA) Updates AD (Active Directory) configs for Cloud NetApp Volumes. EXAMPLES The following command updates an AD config in the given project and - location with specified arguments + location with specified arguments: $ gcloud alpha netapp active-directories update AD_NAME \ --location=us-central1 --domain=new-domain.com --dns=1.1.1.1 \ diff --git a/gcloud/alpha/recommender/recommendations/list b/gcloud/alpha/recommender/recommendations/list index ffb5ac386..14cb73560 100644 --- a/gcloud/alpha/recommender/recommendations/list +++ b/gcloud/alpha/recommender/recommendations/list @@ -48,10 +48,10 @@ REQUIRED FLAGS FLAGS --recommender=RECOMMENDER - Recommender to list recommendations for. If no recommender is - specified, recommendations for all supported recommenders is listed. - Supported recommenders can be found here: - https://cloud.google.com/recommender/docs/recommenders + Recommender to list recommendations for. Supported recommenders can be + found here: https://cloud.google.com/recommender/docs/recommenders. For + alpha and beta users: If no recommender is specified, recommendations + for all supported recommenders are listed. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/redis/clusters/create b/gcloud/alpha/redis/clusters/create new file mode 100644 index 000000000..0ed28591d --- /dev/null +++ b/gcloud/alpha/redis/clusters/create @@ -0,0 +1,134 @@ +NAME + gcloud alpha redis clusters create - create a new Memorystore for Redis + Cluster instance + +SYNOPSIS + gcloud alpha redis clusters create (CLUSTER : --region=REGION) + --network=NETWORK --shard-count=SHARD_COUNT [--async] + [--auth-mode=AUTH_MODE] [--replica-count=REPLICA_COUNT] + [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Create a new Memorystore for Redis Cluster instance, and uses + Private Service Connect service connectivity automation to automate + connectivity for instances. + + This command can fail for the following reasons: + ▪ A cluster with the same name already exists. + ▪ The active account does not have permission to create clusters. + ▪ Some required APIs not enabled yet. + ▪ No connection policy defined yet on the network and in the region a + cluster will be created. + ▪ Miss the steps for creating and configuring a service account (to + grant permissions) in both host project and service project, if a + shared VPC network is used. + + Refer to + https://cloud.google.com/memorystore/docs/cluster/networking#prerequisites_required_before_creating_a_cluster + for prerequisites. + +EXAMPLES + To create a cluster with name my-redis-cluster in region us-central1 with 3 + shards and with a discovery endpoint created on network "default", run: + + $ gcloud alpha redis clusters create my-redis-cluster \ + --region=us-central1 --shard-count=3 \ + --network=projects/NETWORK_PROJECT_ID/global/networks/default + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to create. Your cluster ID must be 1 to 63 characters and use only + lowercase letters, numbers, or hyphens. It must start with a lowercase + letter and end with a lowercase letter or number. The arguments in this + group can be used to specify the attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --network=NETWORK + The network used to create your instance. It must use the format: + projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID + used here must match the network ID used by the service connection + policy. Otherwise, the create operation fails + + --shard-count=SHARD_COUNT + The shard count of the cluster. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auth-mode=AUTH_MODE + Available authorization mode of a Redis cluster. AUTH_MODE must be one + of: + + disabled + Authorization is disabled for the cluster. + + iam-auth + IAM basic authorization is enabled for the cluster. + + --replica-count=REPLICA_COUNT + The replica count of each shard. + + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE + Transit encryption mode used for the Redis cluster. If not provided, + encryption is disabled for the cluster. TRANSIT_ENCRYPTION_MODE must be + one of: + + disabled + In-transit encryption is disabled for the cluster. + + server-authentication + The cluster uses server managed encryption for in-transit + encryption. + +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. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +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: + + $ gcloud beta redis clusters create + diff --git a/gcloud/alpha/redis/clusters/delete b/gcloud/alpha/redis/clusters/delete new file mode 100644 index 000000000..c985e6a66 --- /dev/null +++ b/gcloud/alpha/redis/clusters/delete @@ -0,0 +1,80 @@ +NAME + gcloud alpha redis clusters delete - delete a Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud alpha redis clusters delete (CLUSTER : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Delete a Memorystore for Redis Cluster instance. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To delete a cluster with the name my-redis-cluster in your default region, + run: + + $ gcloud alpha redis clusters delete my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to delete. The arguments in this group can be used to specify the + attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +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: + + $ gcloud beta redis clusters delete + diff --git a/gcloud/alpha/redis/clusters/describe b/gcloud/alpha/redis/clusters/describe new file mode 100644 index 000000000..4d2c4638c --- /dev/null +++ b/gcloud/alpha/redis/clusters/describe @@ -0,0 +1,77 @@ +NAME + gcloud alpha redis clusters describe - show metadata for a Memorystore for + Redis Cluster instance + +SYNOPSIS + gcloud alpha redis clusters describe (CLUSTER : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Show metadata for a Memorystore for Redis Cluster instance. + + Displays all metadata associated with a cluster given a valid cluster name. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To display the metadata for a cluster with the name my-redis-cluster in the + default region, run: + + $ gcloud alpha redis clusters describe my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to describe. The arguments in this group can be used to specify the + attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +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. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +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: + + $ gcloud beta redis clusters describe + diff --git a/gcloud/alpha/redis/clusters/get-cluster-certificate-authority b/gcloud/alpha/redis/clusters/get-cluster-certificate-authority new file mode 100644 index 000000000..dce902fe5 --- /dev/null +++ b/gcloud/alpha/redis/clusters/get-cluster-certificate-authority @@ -0,0 +1,78 @@ +NAME + gcloud alpha redis clusters get-cluster-certificate-authority - get the + certificate authority information for a Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud alpha redis clusters get-cluster-certificate-authority + (CLUSTER : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Get the certificate authority information for a Memorystore for + Redis Cluster instance. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To get the metadata for a cluster with the name my-redie-cluster in the + default region, run: + + $ gcloud alpha redis clusters get-cluster-certificate-authority \ + my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster. The + arguments in this group can be used to specify the attributes of this + 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +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. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +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: + + $ gcloud beta redis clusters get-cluster-certificate-authority + diff --git a/gcloud/alpha/redis/clusters/help b/gcloud/alpha/redis/clusters/help new file mode 100644 index 000000000..46ac2ad6e --- /dev/null +++ b/gcloud/alpha/redis/clusters/help @@ -0,0 +1,45 @@ +NAME + gcloud alpha redis clusters - manage Memorystore for Redis Cluster + instances + +SYNOPSIS + gcloud alpha redis clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (ALPHA) Create a new Memorystore for Redis Cluster instance. + + delete + (ALPHA) Delete a Memorystore for Redis Cluster instance. + + describe + (ALPHA) Show metadata for a Memorystore for Redis Cluster instance. + + get-cluster-certificate-authority + (ALPHA) Get the certificate authority information for a Memorystore for + Redis Cluster instance. + + list + (ALPHA) List Memorystore for Redis Cluster instances. + + update + (ALPHA) Update Memorystore Cluster for Redis instance. + +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: + + $ gcloud beta redis clusters + diff --git a/gcloud/alpha/redis/clusters/list b/gcloud/alpha/redis/clusters/list new file mode 100644 index 000000000..b43fe3540 --- /dev/null +++ b/gcloud/alpha/redis/clusters/list @@ -0,0 +1,90 @@ +NAME + gcloud alpha redis clusters list - list Memorystore for Redis Cluster + instances + +SYNOPSIS + gcloud alpha redis clusters list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List all clusters under the specified project and region. + + To specify the maximum number of clusters to list, use the --limit flag. + +EXAMPLES + To list up to five clusters, run: + + $ gcloud alpha redis clusters list --limit=5 + +FLAGS + Region resource - The region of the clusters to display. 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 --region on the command line with a fully + specified name; + ◆ set the property redis/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +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: + + $ gcloud beta redis clusters list + diff --git a/gcloud/alpha/redis/clusters/update b/gcloud/alpha/redis/clusters/update new file mode 100644 index 000000000..f7b200020 --- /dev/null +++ b/gcloud/alpha/redis/clusters/update @@ -0,0 +1,88 @@ +NAME + gcloud alpha redis clusters update - update Memorystore Cluster for Redis + instance + +SYNOPSIS + gcloud alpha redis clusters update (CLUSTER : --region=REGION) [--async] + [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the metadata and/or configuration parameters of a Redis + cluster. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to update the given + cluster. + +EXAMPLES + To update a Redis cluster with 5 shard and 2 replica, run: + + $ gcloud alpha redis clusters update my-redis-cluster \ + --shard-count=5 --replica-count=2 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --replica-count=REPLICA_COUNT + The replica count of each shard. + + --shard-count=SHARD_COUNT + The shard count of the cluster. + +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. + +API REFERENCE + This command uses the redis/v1alpha1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +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: + + $ gcloud beta redis clusters update + diff --git a/gcloud/alpha/redis/help b/gcloud/alpha/redis/help index e42eeb75a..9c0aefcfd 100644 --- a/gcloud/alpha/redis/help +++ b/gcloud/alpha/redis/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + clusters + (ALPHA) Manage Memorystore for Redis Cluster instances. + instances (ALPHA) Manage Cloud Memorystore Redis instances. diff --git a/gcloud/alpha/sql/instances/create b/gcloud/alpha/sql/instances/create index 8e43bca46..c252edc47 100644 --- a/gcloud/alpha/sql/instances/create +++ b/gcloud/alpha/sql/instances/create @@ -384,9 +384,8 @@ FLAGS --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default - value is 7 for Enterprise edition instances. For Enterprise_Plus - Postgres and MySQL instances, default values are 15 and 8 respectively. - Applicable only if --no-backups is not specified. + value is 7 for Enterprise edition instances. For Enterprise_Plus, + default value is 15. Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between 1 @@ -394,9 +393,7 @@ FLAGS logs are stored on disk, storage size for transaction logs could increase when the number of days for log retention increases. For Enterprise, default and max retention values are 7 and 7 respectively. - For MySQL Enterprise_Plus, default and max retention values are 7 and - 7. For Postgres Enterprise_Plus, default and max retention values are - 14 and 35. + For Enterprise_Plus, default and max retention values are 14 and 35. --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/alpha/sql/instances/patch b/gcloud/alpha/sql/instances/patch index 67c68c0ea..cfcf9f4a4 100644 --- a/gcloud/alpha/sql/instances/patch +++ b/gcloud/alpha/sql/instances/patch @@ -481,8 +481,8 @@ FLAGS --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default value is 7 for Enterprise edition instances. For - Enterprise_Plus Postgres and MySQL instances, default values are 15 - and 8 respectively. Applicable only if --no-backups is not specified. + Enterprise_Plus, default value is 15. Applicable only if --no-backups + is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between @@ -490,9 +490,8 @@ FLAGS enabled. If logs are stored on disk, storage size for transaction logs could increase when the number of days for log retention increases. For Enterprise, default and max retention values are 7 and - 7 respectively. For MySQL Enterprise_Plus, default and max retention - values are 7 and 7. For Postgres Enterprise_Plus, default and max - retention values are 14 and 35. + 7 respectively. For Enterprise_Plus, default and max retention values + are 14 and 35. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/artifacts/repositories/create b/gcloud/artifacts/repositories/create index 4c9a41ad4..2e4e67307 100644 --- a/gcloud/artifacts/repositories/create +++ b/gcloud/artifacts/repositories/create @@ -7,10 +7,14 @@ SYNOPSIS --repository-format=REPOSITORY_FORMAT [--allow-snapshot-overwrites] [--async] [--description=DESCRIPTION] [--immutable-tags] [--kms-key=KMS_KEY] [--labels=[KEY=VALUE,...]] - [--mode=MODE; default="NONE"] [--remote-docker-repo=REMOTE_DOCKER_REPO] + [--mode=MODE; default="NONE"] [--remote-apt-repo=REMOTE_APT_REPO] + [--remote-apt-repo-path=REMOTE_APT_REPO_PATH] + [--remote-docker-repo=REMOTE_DOCKER_REPO] [--remote-mvn-repo=REMOTE_MVN_REPO] [--remote-npm-repo=REMOTE_NPM_REPO] [--remote-python-repo=REMOTE_PYTHON_REPO] [--remote-repo-config-desc=REMOTE_REPO_CONFIG_DESC] + [--remote-yum-repo=REMOTE_YUM_REPO] + [--remote-yum-repo-path=REMOTE_YUM_REPO_PATH] [--upstream-policy-file=FILE] [--version-policy=VERSION_POLICY] [--allow-sbom-generation | --disable-sbom-generation] [GCLOUD_WIDE_FLAG ...] @@ -135,6 +139,13 @@ OPTIONAL FLAGS virtual-repository Virtual repository mode - aggregates data from several upstreams. + --remote-apt-repo=REMOTE_APT_REPO + (Apt only) Repository base for apt remote repository. REMOTE_APT_REPO + must be one of: [debian, ubuntu]. + + --remote-apt-repo-path=REMOTE_APT_REPO_PATH + (Apt only) Remaining URL path to apt remote repository. + --remote-docker-repo=REMOTE_DOCKER_REPO (Docker only) Repo upstream for docker remote repository. REMOTE_DOCKER_REPO must be one of: [docker-hub]. @@ -154,6 +165,14 @@ OPTIONAL FLAGS --remote-repo-config-desc=REMOTE_REPO_CONFIG_DESC The description for the remote repository config. + --remote-yum-repo=REMOTE_YUM_REPO + (Yum only) Repository base for yum remote repository. REMOTE_YUM_REPO + must be one of: [centos, centos-debug, centos-stream, centos-vault, + epel, rocky]. + + --remote-yum-repo-path=REMOTE_YUM_REPO_PATH + (Yum only) Remaining URL path to yum remote repository. + --upstream-policy-file=FILE (Virtual Repositories only) is the upstreams for the Virtual Repository. Example of the file contents: [ { "id": "test1", diff --git a/gcloud/artifacts/sbom/export b/gcloud/artifacts/sbom/export index ef25466f9..dc39a13a6 100644 --- a/gcloud/artifacts/sbom/export +++ b/gcloud/artifacts/sbom/export @@ -1,11 +1,11 @@ NAME - gcloud artifacts sbom export - export SBOM files + gcloud artifacts sbom export - export SBOM files to Google Cloud Storage SYNOPSIS gcloud artifacts sbom export --uri=URI [GCLOUD_WIDE_FLAG ...] DESCRIPTION - Export SBOM files. + Export SBOM files to Google Cloud Storage. EXAMPLES To export an SBOM file for the Artifact Registry image with URI diff --git a/gcloud/artifacts/sbom/help b/gcloud/artifacts/sbom/help index e928076b1..d29820177 100644 --- a/gcloud/artifacts/sbom/help +++ b/gcloud/artifacts/sbom/help @@ -16,7 +16,7 @@ COMMANDS COMMAND is one of the following: export - Export SBOM files. + Export SBOM files to Google Cloud Storage. list List SBOM file references. diff --git a/gcloud/beta/ai/model-monitoring-jobs/create b/gcloud/beta/ai/model-monitoring-jobs/create index 88ae9bd91..58d64f24c 100644 --- a/gcloud/beta/ai/model-monitoring-jobs/create +++ b/gcloud/beta/ai/model-monitoring-jobs/create @@ -10,6 +10,7 @@ SYNOPSIS [--[no-]anomaly-cloud-logging] [--labels=[KEY=VALUE,...]] [--log-ttl=LOG_TTL] [--monitoring-frequency=MONITORING_FREQUENCY; default=24] + [--notification-channels=[NOTIFICATION_CHANNELS,...]] [--predict-instance-schema=PREDICT_INSTANCE_SCHEMA] [--region=REGION] [--sample-predict-request=SAMPLE_PREDICT_REQUEST] [--kms-key=KMS_KEY : --kms-keyring=KMS_KEYRING @@ -119,6 +120,10 @@ OPTIONAL FLAGS --monitoring-frequency=MONITORING_FREQUENCY; default=24 Monitoring frequency, unit is 1 hour. + --notification-channels=[NOTIFICATION_CHANNELS,...] + Comma-separated notification channel list. e.g. + --notification-channels=projects/fake-project/notificationChannels/123,projects/fake-project/notificationChannels/456 + --predict-instance-schema=PREDICT_INSTANCE_SCHEMA YAML schema file uri(Google Cloud Storage) describing the format of a single instance, which are given to format this Endpoint's prediction. diff --git a/gcloud/beta/ai/model-monitoring-jobs/update b/gcloud/beta/ai/model-monitoring-jobs/update index 2c37b34a2..4ba7252ae 100644 --- a/gcloud/beta/ai/model-monitoring-jobs/update +++ b/gcloud/beta/ai/model-monitoring-jobs/update @@ -9,6 +9,7 @@ SYNOPSIS [--[no-]anomaly-cloud-logging] [--display-name=DISPLAY_NAME] [--emails=[EMAILS,...]] [--log-ttl=LOG_TTL] [--monitoring-frequency=MONITORING_FREQUENCY] + [--notification-channels=[NOTIFICATION_CHANNELS,...]] [--prediction-sampling-rate=PREDICTION_SAMPLING_RATE] [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] @@ -85,6 +86,10 @@ FLAGS --monitoring-frequency=MONITORING_FREQUENCY Monitoring frequency, unit is 1 hour. + --notification-channels=[NOTIFICATION_CHANNELS,...] + Comma-separated notification channel list. e.g. + --notification-channels=projects/fake-project/notificationChannels/123,projects/fake-project/notificationChannels/456 + --prediction-sampling-rate=PREDICTION_SAMPLING_RATE Prediction sampling rate. diff --git a/gcloud/beta/alloydb/clusters/create b/gcloud/beta/alloydb/clusters/create index 287dae411..bf608bba0 100644 --- a/gcloud/beta/alloydb/clusters/create +++ b/gcloud/beta/alloydb/clusters/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud beta alloydb clusters create CLUSTER --password=PASSWORD - --region=REGION [--async] [--network=NETWORK] + --region=REGION [--async] [--database-version=DATABASE_VERSION] + [--network=NETWORK] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -45,6 +46,10 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --database-version=DATABASE_VERSION + Database version of the cluster. DATABASE_VERSION must be one of: + POSTGRES_14, POSTGRES_15. + --network=NETWORK Network in the current project that the instance will be part of. To specify using a network with a shared VPC, use the full URL of the diff --git a/gcloud/beta/alloydb/instances/create b/gcloud/beta/alloydb/instances/create index d79abe9ba..c1a954a71 100644 --- a/gcloud/beta/alloydb/instances/create +++ b/gcloud/beta/alloydb/instances/create @@ -41,7 +41,7 @@ REQUIRED FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. --instance-type=INSTANCE_TYPE Specifies instance type. INSTANCE_TYPE must be one of: diff --git a/gcloud/beta/alloydb/instances/update b/gcloud/beta/alloydb/instances/update index cd9ccaf9b..63bdac366 100644 --- a/gcloud/beta/alloydb/instances/update +++ b/gcloud/beta/alloydb/instances/update @@ -53,7 +53,7 @@ OPTIONAL FLAGS Whole number value indicating how many vCPUs the machine should contain. Each vCPU count corresponds to a N2 high-mem machine: (https://cloud.google.com/compute/docs/general-purpose-machines#n2_machines). - CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64. + CPU_COUNT must be one of: 2, 4, 8, 16, 32, 64, 96. --database-flags=FLAG=VALUE,[FLAG=VALUE,...] Comma-separated list of database flags to set on the instance. Use an diff --git a/gcloud/beta/asset/analyze-org-policies b/gcloud/beta/asset/analyze-org-policies index dc5d660c8..c4615ad1a 100644 --- a/gcloud/beta/asset/analyze-org-policies +++ b/gcloud/beta/asset/analyze-org-policies @@ -11,7 +11,7 @@ DESCRIPTION (BETA) Analyze organization policies under a scope. EXAMPLES - To list 10 org policies of a constraint in an organization, run: + To list 10 organization policies of a constraint in an organization, run: $ gcloud beta asset analyze-org-policies \ --scope=organizations/YOUR_ORG_ID \ @@ -23,16 +23,15 @@ REQUIRED FLAGS response only contains analyzed organization policies for the provided constraint. - Examples: + Example: - ◆ ``organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} + ◆ organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} for a user-defined custom constraint. --scope=SCOPE - Scope can only be an organization for now. The analysis is limited to - the Cloud org policies within this scope. The caller must be granted - the cloudasset.assets.searchAllResources permission on the desired - scope. + Scope can only be an organization. The analysis is limited to the Cloud + organization policies within this scope. The caller must be granted the + cloudasset.assets.searchAllResources permission on the desired scope. The allowed values are: diff --git a/gcloud/beta/asset/analyze-org-policy-governed-assets b/gcloud/beta/asset/analyze-org-policy-governed-assets index 809b92708..f66778be0 100644 --- a/gcloud/beta/asset/analyze-org-policy-governed-assets +++ b/gcloud/beta/asset/analyze-org-policy-governed-assets @@ -26,14 +26,14 @@ REQUIRED FLAGS Examples: - ◆ ``organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} + ◆ organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} for a user-defined custom constraint. - ◆ ``organizations/{ORGANIZATION_NUMBER}/constraints/{CANNED_CONSTRAINT_NAME} + ◆ organizations/{ORGANIZATION_NUMBER}/constraints/{CANNED_CONSTRAINT_NAME} for a gcp-service-defined canned constraint. --scope=SCOPE - Scope can only be an organization for now. The analysis is limited to - the Cloud org policies and assets within this scope. The caller must be + Scope can only be an organization. The analysis is limited to the Cloud + organization policies and assets within this scope. The caller must be granted the cloudasset.assets.searchAllResources and cloudasset.assets.searchAllIamPolicies permission on the desired scope. diff --git a/gcloud/beta/asset/analyze-org-policy-governed-containers b/gcloud/beta/asset/analyze-org-policy-governed-containers index ac67c0680..7059eb813 100644 --- a/gcloud/beta/asset/analyze-org-policy-governed-containers +++ b/gcloud/beta/asset/analyze-org-policy-governed-containers @@ -24,16 +24,16 @@ REQUIRED FLAGS response only contains analyzed organization policies for the provided constraint. - Examples: + Example: - ◆ ``organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} + ◆ organizations/{ORGANIZATION_NUMBER}/customConstraints/{CUSTOM_CONSTRAINT_NAME} for a user-defined custom constraint. --scope=SCOPE - Scope can only be an organization for now. The analysis is limited to - the Cloud org policies and containers within this scope. The caller - must be granted the cloudasset.assets.searchAllResources permission on - the desired scope. + Scope can only be an organization. The analysis is limited to the Cloud + organization policies and containers within this scope. The caller must + be granted the cloudasset.assets.searchAllResources permission on the + desired scope. The allowed values are: diff --git a/gcloud/beta/assured/workloads/enable-resource-monitoring b/gcloud/beta/assured/workloads/enable-resource-monitoring new file mode 100644 index 000000000..2fceed384 --- /dev/null +++ b/gcloud/beta/assured/workloads/enable-resource-monitoring @@ -0,0 +1,66 @@ +NAME + gcloud beta assured workloads enable-resource-monitoring - enables Resource + Monitoring for an Assured Workloads environment + +SYNOPSIS + gcloud beta assured workloads enable-resource-monitoring + (WORKLOAD : --location=LOCATION --organization=ORGANIZATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enable resource violation monitoring for a workload. + +EXAMPLES + To enable resource violation monitoring for a workload in the us-central1 + region, belonging to an organization with ID 123, with workload ID 456, + run: + + $ gcloud beta assured workloads enable-resource-monitoring \ + organizations/123/locations/us-central1/workloads/456 + +POSITIONAL ARGUMENTS + Workload resource - The Assured Workloads environment resource to + enable-resource-monitoring. The arguments in this group can be used to + specify the attributes of this resource. + + This must be specified. + + WORKLOAD + ID of the workload or fully qualified identifier for the workload. + + To set the workload attribute: + ▸ provide the argument workload on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + The location for the workload. + + To set the location attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --location on the command line. + + --organization=ORGANIZATION + The parent organization for the workload. + + To set the organization attribute: + ▸ provide the argument workload on the command line with a fully + specified name; + ▸ provide the argument --organization on the command line. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha assured workloads enable-resource-monitoring + diff --git a/gcloud/beta/assured/workloads/help b/gcloud/beta/assured/workloads/help index 6be9c9490..e1b86163d 100644 --- a/gcloud/beta/assured/workloads/help +++ b/gcloud/beta/assured/workloads/help @@ -31,6 +31,10 @@ COMMANDS describe (BETA) Describe Assured Workloads environment. + enable-resource-monitoring + (BETA) Enables Resource Monitoring for an Assured Workloads + environment. + list (BETA) List all Assured Workloads environments that belong to a given parent organization. diff --git a/gcloud/beta/bigtable/backups/copy b/gcloud/beta/bigtable/backups/copy new file mode 100644 index 000000000..c8b2d8972 --- /dev/null +++ b/gcloud/beta/bigtable/backups/copy @@ -0,0 +1,166 @@ +NAME + gcloud beta bigtable backups copy - copy a Cloud Bigtable backup to a new + backup + +SYNOPSIS + gcloud beta bigtable backups copy + (--destination-backup=DESTINATION_BACKUP + : --destination-cluster=DESTINATION_CLUSTER + --destination-instance=DESTINATION_INSTANCE + --destination-project=DESTINATION_PROJECT) + (--expiration-date=EXPIRATION_DATE + | --retention-period=RETENTION_PERIOD) + (--source-backup=SOURCE_BACKUP : --source-cluster=SOURCE_CLUSTER + --source-instance=SOURCE_INSTANCE --source-project=SOURCE_PROJECT) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command creates a copy of a Cloud Bigtable backup. + +EXAMPLES + To copy a backup within the same project, run: + + $ gcloud beta bigtable backups copy \ + --source-instance=SOURCE_INSTANCE \ + --source-cluster=SOURCE_CLUSTER --source-backup=SOURCE_BACKUP \ + --destination-instance=DESTINATION_INSTANCE \ + --destination-cluster=DESTINATION_CLUSTER \ + --destination-backup=DESTINATION_BACKUP \ + --expiration-date=2023-09-01T10:49:41Z + + To copy a backup to a different project, run: + + $ gcloud beta bigtable backups copy \ + --source-backup=projects/SOURCE_PROJECT/instances/\ + SOURCE_INSTANCE/clusters/SOURCE_CLUSTER/backups/SOURCE_BACKUP \ + --destination-backup=projects/DESTINATION_PROJECT/instances/\ + DESTINATION_INSTANCE/clusters/DESTINATION_CLUSTER/backups/\ + DESTINATION_BACKUP --expiration-date=2022-08-01T10:49:41Z + + To set retention period and run asyncronously, run: + + $ gcloud beta bigtable backups copy \ + --source-backup=projects/SOURCE_PROJECT/instances/\ + SOURCE_INSTANCE/clusters/SOURCE_CLUSTER/backups/SOURCE_BACKUP \ + --destination-backup=projects/DESTINATION_PROJECT/instances/\ + DESTINATION_INSTANCE/clusters/DESTINATION_CLUSTER/backups/\ + DESTINATION_BACKUP --retention-period=2w --async + +REQUIRED FLAGS + Backup resource - The destination backup to copy to. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + --destination-backup=DESTINATION_BACKUP + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument --destination-backup on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --destination-cluster=DESTINATION_CLUSTER + Cloud Bigtable cluster for the backup. + + To set the cluster attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-cluster on the command line. + + --destination-instance=DESTINATION_INSTANCE + Cloud Bigtable instance for the backup. + + To set the instance attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-instance on the command line; + ▸ provide the argument --source-instance on the command line. + + --destination-project=DESTINATION_PROJECT + Project ID of the Google Cloud project for the backup. + + To set the project attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-project on the command line; + ▸ provide the argument --source-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + Exactly one of these must be specified: + + --expiration-date=EXPIRATION_DATE + Expiration time of the backup, must be at least 6 hours and at most + 30 days from the time the source backup is created. See $ gcloud + topic datetimes for information on date/time formats. + + --retention-period=RETENTION_PERIOD + Retention period of the backup relative from now, must be at least 6 + hours and at most 30 days from the time the source backup is created. + See $ gcloud topic datetimes for information on duration formats. + + Backup resource - The source backup to copy from. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + --source-backup=SOURCE_BACKUP + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument --source-backup on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --source-cluster=SOURCE_CLUSTER + Cloud Bigtable cluster for the backup. + + To set the cluster attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-cluster on the command line. + + --source-instance=SOURCE_INSTANCE + Cloud Bigtable instance for the backup. + + To set the instance attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-instance on the command line; + ▸ provide the argument --destination-instance on the command line. + + --source-project=SOURCE_PROJECT + Project ID of the Google Cloud project for the backup. + + To set the project attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-project on the command line; + ▸ provide the argument --destination-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud bigtable backups copy + + $ gcloud alpha bigtable backups copy + diff --git a/gcloud/beta/bigtable/backups/help b/gcloud/beta/bigtable/backups/help index 4a66325d7..1dde654e7 100644 --- a/gcloud/beta/bigtable/backups/help +++ b/gcloud/beta/bigtable/backups/help @@ -18,6 +18,9 @@ COMMANDS add-iam-policy-binding (BETA) Add an IAM policy binding to a Cloud Bigtable Backup. + copy + (BETA) Copy a Cloud Bigtable backup to a new backup. + create (BETA) Creates a backup of a Cloud Bigtable table. diff --git a/gcloud/beta/compute/project-info/update b/gcloud/beta/compute/project-info/update index 2aac1ed1d..7f6d39db0 100644 --- a/gcloud/beta/compute/project-info/update +++ b/gcloud/beta/compute/project-info/update @@ -4,7 +4,9 @@ NAME SYNOPSIS gcloud beta compute project-info update - [--default-network-tier=DEFAULT_NETWORK_TIER] [GCLOUD_WIDE_FLAG ...] + [--default-network-tier=DEFAULT_NETWORK_TIER] + [--managed-protection-tier=MANAGED_PROTECTION_TIER] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) gcloud beta compute project-info update is used to update a Compute @@ -15,6 +17,10 @@ FLAGS The default network tier to assign to the project. DEFAULT_NETWORK_TIER must be one of: PREMIUM, STANDARD, FIXED_STANDARD. + --managed-protection-tier=MANAGED_PROTECTION_TIER + The maanged protection tier to assign to the project. + MANAGED_PROTECTION_TIER must be one of: CA_STANDARD, CAMP_PLUS_MONTHLY. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, diff --git a/gcloud/beta/compute/target-http-proxies/create b/gcloud/beta/compute/target-http-proxies/create index 420658d28..91f48539b 100644 --- a/gcloud/beta/compute/target-http-proxies/create +++ b/gcloud/beta/compute/target-http-proxies/create @@ -53,7 +53,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external Application load balancer, the minimum allowed + For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-http-proxies/update b/gcloud/beta/compute/target-http-proxies/update index 192e7cb98..9963f60b1 100644 --- a/gcloud/beta/compute/target-http-proxies/update +++ b/gcloud/beta/compute/target-http-proxies/update @@ -50,7 +50,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external Application load balancer, the minimum + seconds. For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/beta/compute/target-https-proxies/create b/gcloud/beta/compute/target-https-proxies/create index b309f625b..bbc92bea7 100644 --- a/gcloud/beta/compute/target-https-proxies/create +++ b/gcloud/beta/compute/target-https-proxies/create @@ -83,7 +83,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external Application load balancer, the minimum allowed + For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. --quic-override=QUIC_OVERRIDE; default="NONE" @@ -102,8 +102,8 @@ OPTIONAL FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the HTTPS proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target HTTPS proxy. + and load balancers that are using the HTTPS proxy. The SSL policy must + exist and cannot be deleted while referenced by a target HTTPS proxy. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-https-proxies/update b/gcloud/beta/compute/target-https-proxies/update index d7d1d71e0..5919c5700 100644 --- a/gcloud/beta/compute/target-https-proxies/update +++ b/gcloud/beta/compute/target-https-proxies/update @@ -171,7 +171,7 @@ FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external Application load balancer, the minimum + seconds. For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. @@ -183,8 +183,9 @@ FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the HTTPS proxy load balancer. The SSL policy must exist and - cannot be deleted while referenced by a target HTTPS proxy. + and load balancers that are using the HTTPS proxy. The SSL policy + must exist and cannot be deleted while referenced by a target HTTPS + proxy. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-ssl-proxies/create b/gcloud/beta/compute/target-ssl-proxies/create index cc9e56e96..7c233b7e7 100644 --- a/gcloud/beta/compute/target-ssl-proxies/create +++ b/gcloud/beta/compute/target-ssl-proxies/create @@ -76,8 +76,8 @@ OPTIONAL FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the SSL proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target SSL proxy. + and load balancers that are using the SSL proxy. The SSL policy must + exist and cannot be deleted while referenced by a target SSL proxy. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-ssl-proxies/help b/gcloud/beta/compute/target-ssl-proxies/help index f866bb384..505b21af9 100644 --- a/gcloud/beta/compute/target-ssl-proxies/help +++ b/gcloud/beta/compute/target-ssl-proxies/help @@ -6,11 +6,11 @@ SYNOPSIS gcloud beta compute target-ssl-proxies COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List, create, and delete target SSL target proxies for SSL Proxy - Load Balancing. + (BETA) List, create, and delete target SSL target proxies for proxy Network + Load Balancers. - For more information about target SSL proxies, see the SSL proxy load - balancer documentation (https://cloud.google.com/load-balancing/docs/ssl/). + For more information about target SSL proxies, see the proxy Network Load + Balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). See also: Target SSL proxies API (https://cloud.google.com/compute/docs/reference/rest/v1/targetSslProxies). diff --git a/gcloud/beta/compute/target-ssl-proxies/update b/gcloud/beta/compute/target-ssl-proxies/update index bc6b68c2c..da5bf010f 100644 --- a/gcloud/beta/compute/target-ssl-proxies/update +++ b/gcloud/beta/compute/target-ssl-proxies/update @@ -47,8 +47,8 @@ FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the SSL proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target SSL proxy. + and load balancers that are using the SSL proxy. The SSL policy must + exist and cannot be deleted while referenced by a target SSL proxy. At most one of these can be specified: diff --git a/gcloud/beta/compute/target-tcp-proxies/help b/gcloud/beta/compute/target-tcp-proxies/help index 369eb31f9..0cdf88e42 100644 --- a/gcloud/beta/compute/target-tcp-proxies/help +++ b/gcloud/beta/compute/target-tcp-proxies/help @@ -6,11 +6,11 @@ SYNOPSIS gcloud beta compute target-tcp-proxies COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) List, create, and delete target TCP proxies for TCP Proxy Load - Balancing. + (BETA) List, create, and delete target TCP proxies for proxy Network Load + Balancers. - For more information about target TCP proxies, see the TCP proxy load - balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). + For more information about target TCP proxies, see the proxy Network Load + Balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). See also: Target TCP proxies API (https://cloud.google.com/compute/docs/reference/rest/v1/targetTcpProxies). diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index 7422b037d..778569dee 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -414,6 +414,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 70187c4fb..6d80452b5 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -446,6 +446,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 0aaf77d35..00a062bf6 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -458,6 +458,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 6024ec430..725e4243d 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -461,6 +461,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 25ba70747..cece31ec3 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -422,6 +422,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/beta/container/binauthz/policy/create b/gcloud/beta/container/binauthz/policy/create new file mode 100644 index 000000000..fb4d24c43 --- /dev/null +++ b/gcloud/beta/container/binauthz/policy/create @@ -0,0 +1,77 @@ +NAME + gcloud beta container binauthz policy create - create a Binary + Authorization platform policy + +SYNOPSIS + gcloud beta container binauthz policy create + (POLICY_RESOURCE_NAME : --platform=PLATFORM) --policy-file=POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To create a policy for GKE in the current project: + + $ gcloud beta container binauthz policy create my-policy \ + --platform=gke --policy-file=my_policy.yaml + + To create a policy for GKE in a specific project: + + $ gcloud beta container binauthz policy create my-policy \ + --platform=gke --project=my-project-id \ + --policy-file=my_policy.yaml + + or + + $ gcloud beta container binauthz policy create \ + /projects/my-project-id/platforms/gke/policies/my-policy \ + --policy-file=my_policy.yaml + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to create. The arguments + in this group can be used to specify the attributes of this 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +REQUIRED FLAGS + --policy-file=POLICY_FILE + The JSON or YAML file containing the new policy. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container binauthz policy create + diff --git a/gcloud/beta/container/binauthz/policy/delete b/gcloud/beta/container/binauthz/policy/delete new file mode 100644 index 000000000..a2cf49f2b --- /dev/null +++ b/gcloud/beta/container/binauthz/policy/delete @@ -0,0 +1,65 @@ +NAME + gcloud beta container binauthz policy delete - delete a Binary + Authorization platform policy + +SYNOPSIS + gcloud beta container binauthz policy delete + (POLICY_RESOURCE_NAME : --platform=PLATFORM) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To delete a policy using its resource name: + + $ gcloud beta container binauthz policy delete \ + projects/my_proj/platforms/gke/policies/policy1 + + To delete the same policy using flags: + + $ gcloud beta container binauthz policy delete policy1 \ + --platform=gke --project=my_proj + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to delete. The arguments + in this group can be used to specify the attributes of this 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container binauthz policy delete + diff --git a/gcloud/beta/container/binauthz/policy/describe b/gcloud/beta/container/binauthz/policy/describe new file mode 100644 index 000000000..fb932e290 --- /dev/null +++ b/gcloud/beta/container/binauthz/policy/describe @@ -0,0 +1,65 @@ +NAME + gcloud beta container binauthz policy describe - describe a Binary + Authorization platform policy + +SYNOPSIS + gcloud beta container binauthz policy describe + (POLICY_RESOURCE_NAME : --platform=PLATFORM) [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To describe an existing policy using its resource name: + + $ gcloud beta container binauthz policy describe \ + projects/my_proj/platforms/gke/policies/policy1 + + To describe the same policy using flags: + + $ gcloud beta container binauthz policy describe policy1 \ + --platform=gke --project=my_proj + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to describe. The + arguments in this group can be used to specify the attributes of this + 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container binauthz policy describe + diff --git a/gcloud/beta/container/binauthz/policy/help b/gcloud/beta/container/binauthz/policy/help index 96994527f..c454c3602 100644 --- a/gcloud/beta/container/binauthz/policy/help +++ b/gcloud/beta/container/binauthz/policy/help @@ -19,6 +19,15 @@ COMMANDS add-iam-policy-binding (BETA) Add IAM policy binding to a Binary Authorization policy. + create + (BETA) Create a Binary Authorization platform policy. + + delete + (BETA) Delete a Binary Authorization platform policy. + + describe + (BETA) Describe a Binary Authorization platform policy. + export (BETA) Export the Binary Authorization policy for the current project. @@ -28,12 +37,18 @@ COMMANDS import (BETA) Import a Binary Authorization policy to the current project. + list + (BETA) List Binary Authorization platform policies. + remove-iam-policy-binding (BETA) Remove IAM policy binding of a Binary Authorization policy. set-iam-policy (BETA) Set the IAM policy for a Binary Authorization policy. + update + (BETA) Update a Binary Authorization platform policy. + NOTES This command is currently in beta and might change without notice. These variants are also available: diff --git a/gcloud/beta/container/binauthz/policy/list b/gcloud/beta/container/binauthz/policy/list new file mode 100644 index 000000000..0977c6138 --- /dev/null +++ b/gcloud/beta/container/binauthz/policy/list @@ -0,0 +1,89 @@ +NAME + gcloud beta container binauthz policy list - list Binary Authorization + platform policies + +SYNOPSIS + gcloud beta container binauthz policy list PLATFORM_RESOURCE_NAME + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To list the policies for GKE in the current project: + + $ gcloud beta container binauthz policy list gke + + To list the policies for GKE in a specific project: + + $ gcloud beta container binauthz policy list gke \ + --project=my-project-id + + or + + $ gcloud beta container binauthz policy list \ + projects/my-project-id/gke + +POSITIONAL ARGUMENTS + Platform resource - The platform whose policies 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 platform_resource_name on the command line with + a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + PLATFORM_RESOURCE_NAME + ID of the platform or fully qualified identifier for the platform. + + To set the platform attribute: + ▸ provide the argument platform_resource_name on the command line. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container binauthz policy list + diff --git a/gcloud/beta/container/binauthz/policy/update b/gcloud/beta/container/binauthz/policy/update new file mode 100644 index 000000000..f146831f4 --- /dev/null +++ b/gcloud/beta/container/binauthz/policy/update @@ -0,0 +1,71 @@ +NAME + gcloud beta container binauthz policy update - update a Binary + Authorization platform policy + +SYNOPSIS + gcloud beta container binauthz policy update + (POLICY_RESOURCE_NAME : --platform=PLATFORM) --policy-file=POLICY_FILE + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To update an existing policy using its resource name: + + $ gcloud beta container binauthz policy update \ + projects/my_proj/platforms/gke/policies/policy1 \ + --policy-file=policy1.json + + To update the same policy using flags: + + $ gcloud beta container binauthz policy update policy1 \ + --platform=gke --project=my_proj --policy-file=policy1.json + +POSITIONAL ARGUMENTS + Policy resource - The resource name of the policy to update. The arguments + in this group can be used to specify the attributes of this 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 policy_resource_name on the command line with a + fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + POLICY_RESOURCE_NAME + ID of the policy or fully qualified identifier for the policy. + + To set the policy attribute: + ▸ provide the argument policy_resource_name on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --platform=PLATFORM + The platform that the policy belongs to. PLATFORM must be one of the + following: cloudRun, gke. + + To set the platform attribute: + ▸ provide the argument policy_resource_name on the command line + with a fully specified name; + ▸ provide the argument --platform on the command line. + +REQUIRED FLAGS + --policy-file=POLICY_FILE + The JSON or YAML file containing the new policy. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container binauthz policy update + diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 73217e5db..e9a0c9208 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -854,7 +854,7 @@ FLAGS 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]. + [TIER_UNSPECIFIED,TIER_1]. See https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration @@ -1107,6 +1107,9 @@ FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -1137,6 +1140,19 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. diff --git a/gcloud/beta/container/clusters/update b/gcloud/beta/container/clusters/update index 1f9699249..1a0edeeaa 100644 --- a/gcloud/beta/container/clusters/update +++ b/gcloud/beta/container/clusters/update @@ -425,7 +425,7 @@ REQUIRED FLAGS 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]. + [TIER_UNSPECIFIED,TIER_1]. See https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration diff --git a/gcloud/beta/container/fleet/memberships/bindings/create b/gcloud/beta/container/fleet/memberships/bindings/create index c38c2b0ce..85b340f2e 100644 --- a/gcloud/beta/container/fleet/memberships/bindings/create +++ b/gcloud/beta/container/fleet/memberships/bindings/create @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud beta container fleet memberships bindings create - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -73,32 +72,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Membership Binding is created for all the Scopes in the Fleet for - given Membership. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --labels=[KEY=VALUE,...] diff --git a/gcloud/beta/container/fleet/memberships/bindings/update b/gcloud/beta/container/fleet/memberships/bindings/update index b560e9ad1..af2707828 100644 --- a/gcloud/beta/container/fleet/memberships/bindings/update +++ b/gcloud/beta/container/fleet/memberships/bindings/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud beta container fleet memberships bindings update - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -74,32 +74,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Bindings for all the membership related scopes in the fleet would be - updated. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --update-labels=[KEY=VALUE,...] diff --git a/gcloud/beta/container/hub/memberships/bindings/create b/gcloud/beta/container/hub/memberships/bindings/create index e9a99390d..ced68fa7d 100644 --- a/gcloud/beta/container/hub/memberships/bindings/create +++ b/gcloud/beta/container/hub/memberships/bindings/create @@ -4,9 +4,8 @@ NAME SYNOPSIS gcloud beta container hub memberships bindings create - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -73,32 +72,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Membership Binding is created for all the Scopes in the Fleet for - given Membership. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --labels=[KEY=VALUE,...] diff --git a/gcloud/beta/container/hub/memberships/bindings/update b/gcloud/beta/container/hub/memberships/bindings/update index 6a6272b90..919b8513c 100644 --- a/gcloud/beta/container/hub/memberships/bindings/update +++ b/gcloud/beta/container/hub/memberships/bindings/update @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud beta container hub memberships bindings update - (BINDING : --location=LOCATION --membership=MEMBERSHIP) - (--fleet=FLEET | --scope=SCOPE) [--update-labels=[KEY=VALUE,...]] + (BINDING : --location=LOCATION --membership=MEMBERSHIP) --scope=SCOPE + [--update-labels=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -74,32 +74,11 @@ POSITIONAL ARGUMENTS ▸ provide the argument --membership on the command line. REQUIRED FLAGS - Exactly one of these must be specified: + --scope=SCOPE + ID of the scope or fully qualified identifier for the scope. - --fleet=FLEET - Bindings for all the membership related scopes in the fleet would be - updated. - - Scope resource - The group of arguments defining the Fleet Scope. 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 --scope on the command line with a fully - specified name; - ▸ provide the argument --project on the command line; - ▸ set the property core/project. - - To set the location attribute: - ▸ provide the argument --scope on the command line with a fully - specified name; - ▸ global is the only supported location. - - --scope=SCOPE - ID of the scope or fully qualified identifier for the scope. - - To set the scope attribute: - ▫ provide the argument --scope on the command line. + To set the scope attribute: + ◆ provide the argument --scope on the command line. OPTIONAL FLAGS --update-labels=[KEY=VALUE,...] diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index 9de1a6f2e..9d6786e87 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -45,7 +45,7 @@ SYNOPSIS batch-soak-duration=BATCH_SOAK_DURATION,...]] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] - [--windows-os-version=WINDOWS_OS_VERSION] + [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] [--workload-metadata=WORKLOAD_METADATA] [--create-pod-ipv4-range=[KEY=VALUE,...] | --pod-ipv4-range=NAME] [--enable-autoscaling --location-policy=LOCATION_POLICY @@ -591,6 +591,9 @@ FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -621,6 +624,19 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. @@ -641,6 +657,12 @@ FLAGS The number of visible threads per physical core for each node. To disable simultaneous multithreading (SMT) set this to 1. + --tpu-topology=TPU_TOPOLOGY + The desired physical topology for the PodSlice. + + $ gcloud beta container node-pools create node-pool-1 \ + --cluster=example-cluster --tpu-topology + --windows-os-version=WINDOWS_OS_VERSION Specifies the Windows Server Image to use when creating a Windows node pool. Valid variants can be "ltsc2019", "ltsc2022". It means using diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 25acb6923..abef3c0da 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -12,18 +12,18 @@ SYNOPSIS | --node-taints=[NODE_TAINT,...] | --system-config-from-file=SYSTEM_CONFIG_FROM_FILE | --tags=[TAG,...] | --windows-os-version=WINDOWS_OS_VERSION - | --workload-metadata=WORKLOAD_METADATA | --enable-autoprovisioning - --enable-autoscaling --location-policy=LOCATION_POLICY - --max-nodes=MAX_NODES --min-nodes=MIN_NODES - --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES - | --enable-autorepair --enable-autoupgrade - | --enable-blue-green-upgrade --enable-surge-upgrade - --max-surge-upgrade=MAX_SURGE_UPGRADE + | --workload-metadata=WORKLOAD_METADATA | --enable-blue-green-upgrade + --enable-surge-upgrade --max-surge-upgrade=MAX_SURGE_UPGRADE --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE --node-pool-soak-duration=NODE_POOL_SOAK_DURATION --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT, batch-percent=BATCH_NODE_PERCENTAGE, - batch-soak-duration=BATCH_SOAK_DURATION,...]) [--async] + batch-soak-duration=BATCH_SOAK_DURATION,...] + | --enable-autoprovisioning --enable-autoscaling + --location-policy=LOCATION_POLICY --max-nodes=MAX_NODES + --min-nodes=MIN_NODES + --total-max-nodes=TOTAL_MAX_NODES --total-min-nodes=TOTAL_MIN_NODES + | --enable-autorepair --enable-autoupgrade) [--async] [--cluster=CLUSTER] [--location=LOCATION | --region=REGION | --zone=ZONE, -z ZONE] [GCLOUD_WIDE_FLAG ...] @@ -157,6 +157,9 @@ REQUIRED FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -190,6 +193,19 @@ REQUIRED FLAGS tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. @@ -250,6 +266,70 @@ REQUIRED FLAGS security improvements. This feature is scheduled to be deprecated in the future and later removed. + Upgrade settings + + --enable-blue-green-upgrade + Changes node pool upgrade strategy to blue-green upgrade. + + --enable-surge-upgrade + Changes node pool upgrade strategy to surge upgrade. + + --max-surge-upgrade=MAX_SURGE_UPGRADE + Number of extra (surge) nodes to be created on each upgrade of the + node pool. + + Specifies the number of extra (surge) nodes to be created during + this node pool's upgrades. For example, running the following + command will result in creating an extra node each time the node + pool is upgraded: + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster --max-surge-upgrade=1 \ + --max-unavailable-upgrade=0 + + Must be used in conjunction with '--max-unavailable-upgrade'. + + --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE + Number of nodes that can be unavailable at the same time on each + upgrade of the node pool. + + Specifies the number of nodes that can be unavailable at the same + time during this node pool's upgrades. For example, assume the node + pool has 5 nodes, running the following command will result in + having 3 nodes being upgraded in parallel (1 + 2), but keeping + always at least 3 (5 - 2) available each time the node pool is + upgraded: + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster --max-surge-upgrade=1 \ + --max-unavailable-upgrade=2 + + Must be used in conjunction with '--max-surge-upgrade'. + + --node-pool-soak-duration=NODE_POOL_SOAK_DURATION + Time in seconds to be spent waiting during blue-green upgrade + before deleting the blue pool and completing the upgrade. + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster --node-pool-soak-duration=600s + + --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...] + Standard rollout policy options for blue-green upgrade. + + Batch sizes are specified by one of, batch-node-count or + batch-percent. The duration between batches is specified by + batch-soak-duration. + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --standard-rollout-policy=batch-node-count=3,\ + batch-soak-duration=60s + + $ gcloud beta container node-pools update node-pool-1 \ + --cluster=example-cluster \ + --standard-rollout-policy=batch-percent=0.3,\ + batch-soak-duration=60s + Cluster autoscaling --enable-autoprovisioning @@ -328,70 +408,6 @@ REQUIRED FLAGS https://cloud.google.com/kubernetes-engine/docs/node-auto-upgrades for more info. - Upgrade settings - - --enable-blue-green-upgrade - Changes node pool upgrade strategy to blue-green upgrade. - - --enable-surge-upgrade - Changes node pool upgrade strategy to surge upgrade. - - --max-surge-upgrade=MAX_SURGE_UPGRADE - Number of extra (surge) nodes to be created on each upgrade of the - node pool. - - Specifies the number of extra (surge) nodes to be created during - this node pool's upgrades. For example, running the following - command will result in creating an extra node each time the node - pool is upgraded: - - $ gcloud beta container node-pools update node-pool-1 \ - --cluster=example-cluster --max-surge-upgrade=1 \ - --max-unavailable-upgrade=0 - - Must be used in conjunction with '--max-unavailable-upgrade'. - - --max-unavailable-upgrade=MAX_UNAVAILABLE_UPGRADE - Number of nodes that can be unavailable at the same time on each - upgrade of the node pool. - - Specifies the number of nodes that can be unavailable at the same - time during this node pool's upgrades. For example, assume the node - pool has 5 nodes, running the following command will result in - having 3 nodes being upgraded in parallel (1 + 2), but keeping - always at least 3 (5 - 2) available each time the node pool is - upgraded: - - $ gcloud beta container node-pools update node-pool-1 \ - --cluster=example-cluster --max-surge-upgrade=1 \ - --max-unavailable-upgrade=2 - - Must be used in conjunction with '--max-surge-upgrade'. - - --node-pool-soak-duration=NODE_POOL_SOAK_DURATION - Time in seconds to be spent waiting during blue-green upgrade - before deleting the blue pool and completing the upgrade. - - $ gcloud beta container node-pools update node-pool-1 \ - --cluster=example-cluster --node-pool-soak-duration=600s - - --standard-rollout-policy=[batch-node-count=BATCH_NODE_COUNT,batch-percent=BATCH_NODE_PERCENTAGE,batch-soak-duration=BATCH_SOAK_DURATION,...] - Standard rollout policy options for blue-green upgrade. - - Batch sizes are specified by one of, batch-node-count or - batch-percent. The duration between batches is specified by - batch-soak-duration. - - $ gcloud beta container node-pools update node-pool-1 \ - --cluster=example-cluster \ - --standard-rollout-policy=batch-node-count=3,\ - batch-soak-duration=60s - - $ gcloud beta container node-pools update node-pool-1 \ - --cluster=example-cluster \ - --standard-rollout-policy=batch-percent=0.3,\ - batch-soak-duration=60s - OPTIONAL FLAGS --async Return immediately, without waiting for the operation in progress to diff --git a/gcloud/beta/container/vmware/admin-clusters/help b/gcloud/beta/container/vmware/admin-clusters/help index f0474f7e8..b5420a4fc 100644 --- a/gcloud/beta/container/vmware/admin-clusters/help +++ b/gcloud/beta/container/vmware/admin-clusters/help @@ -25,6 +25,9 @@ COMMANDS list (BETA) List Anthos on VMware admin clusters. + unenroll + (BETA) Unenroll an Anthos on VMware admin cluster. + update (BETA) Update an Anthos on VMware admin cluster. diff --git a/gcloud/beta/container/vmware/admin-clusters/unenroll b/gcloud/beta/container/vmware/admin-clusters/unenroll new file mode 100644 index 000000000..7497d0698 --- /dev/null +++ b/gcloud/beta/container/vmware/admin-clusters/unenroll @@ -0,0 +1,79 @@ +NAME + gcloud beta container vmware admin-clusters unenroll - unenroll an Anthos + on VMware admin cluster + +SYNOPSIS + gcloud beta container vmware admin-clusters unenroll + (ADMIN_CLUSTER : --location=LOCATION) [--allow-missing] [--async] + [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Unenroll an Anthos on VMware admin cluster. + +EXAMPLES + To unenroll an admin cluster named my-cluster managed in location us-west1, + run: + + $ gcloud beta container vmware admin-clusters unenroll my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster to unenroll The arguments in this + group can be used to specify the attributes of this 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 admin_cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + ADMIN_CLUSTER + ID of the admin_cluster or fully qualified identifier for the + admin_cluster. + + To set the admin_cluster attribute: + ▸ provide the argument admin_cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --location=LOCATION + Google Cloud location for the admin_cluster. + + To set the location attribute: + ▸ provide the argument admin_cluster on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +FLAGS + --allow-missing + If set, and the VMware Cluster is not found, the request will succeed + but no action will be taken on the server and return a completed LRO. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + +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 + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware admin-clusters unenroll + diff --git a/gcloud/beta/dataflow/jobs/update-options b/gcloud/beta/dataflow/jobs/update-options index c21a71e9b..8b226a7e8 100644 --- a/gcloud/beta/dataflow/jobs/update-options +++ b/gcloud/beta/dataflow/jobs/update-options @@ -59,5 +59,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. NOTES - This command is currently in beta and might change without notice. + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud dataflow jobs update-options diff --git a/gcloud/beta/dns/record-sets/create b/gcloud/beta/dns/record-sets/create index cdc7f967f..bf15845fd 100644 --- a/gcloud/beta/dns/record-sets/create +++ b/gcloud/beta/dns/record-sets/create @@ -129,8 +129,9 @@ REQUIRED FLAGS semicolon-delimited list of the format "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP address or a reference to a forwarding rule of the format - FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full - resource path of the forwarding rule. + "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@{region}", + "FORWARDING_RULE_NAME@global", or the full resource path of the + forwarding rule. Configuration for primary backup routing policy diff --git a/gcloud/beta/dns/record-sets/update b/gcloud/beta/dns/record-sets/update index 816e70366..e27df0127 100644 --- a/gcloud/beta/dns/record-sets/update +++ b/gcloud/beta/dns/record-sets/update @@ -96,8 +96,9 @@ REQUIRED FLAGS semicolon-delimited list of the format "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP address or a reference to a forwarding rule of the format - FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full - resource path of the forwarding rule. + "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@{region}", + "FORWARDING_RULE_NAME@global", or the full resource path of the + forwarding rule. Configuration for primary backup routing policy diff --git a/gcloud/beta/netapp/active-directories/create b/gcloud/beta/netapp/active-directories/create index 12db43f4a..a308b16a3 100644 --- a/gcloud/beta/netapp/active-directories/create +++ b/gcloud/beta/netapp/active-directories/create @@ -17,11 +17,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Creates an AD (Active Directory) config for Cloud NetApp Volumes + (BETA) Creates an AD (Active Directory) config for Cloud NetApp Volumes. EXAMPLES The following command creates an AD named AD_NAME with the required - arguments + arguments: $ gcloud beta netapp active-directories create AD_NAME \ --location=us-central1 --domain=example-domain.com \ diff --git a/gcloud/beta/netapp/active-directories/delete b/gcloud/beta/netapp/active-directories/delete index b3e361cd8..667f697c5 100644 --- a/gcloud/beta/netapp/active-directories/delete +++ b/gcloud/beta/netapp/active-directories/delete @@ -8,11 +8,11 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Deletes an AD (Active Directory) config for Cloud NetApp Volumes + (BETA) Deletes an AD (Active Directory) config for Cloud NetApp Volumes. EXAMPLES The following command deletes an AD named AD_NAME with the required - arguments + arguments: $ gcloud beta netapp active-directories delete AD_NAME \ --location=us-central1 diff --git a/gcloud/beta/netapp/active-directories/describe b/gcloud/beta/netapp/active-directories/describe index fe8d5a1e0..531c8456b 100644 --- a/gcloud/beta/netapp/active-directories/describe +++ b/gcloud/beta/netapp/active-directories/describe @@ -7,11 +7,11 @@ SYNOPSIS (ACTIVE_DIRECTORY : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Describes an AD (Active Directory) config for Cloud NetApp Volumes + (BETA) Describes an AD (Active Directory) config for Cloud NetApp Volumes. EXAMPLES The following command describes an AD named AD_NAME with the required - arguments + arguments: $ gcloud beta netapp active-directories describe AD_NAME \ --location=us-central1 diff --git a/gcloud/beta/netapp/active-directories/list b/gcloud/beta/netapp/active-directories/list index af3b9f50c..28d754a69 100644 --- a/gcloud/beta/netapp/active-directories/list +++ b/gcloud/beta/netapp/active-directories/list @@ -8,10 +8,10 @@ SYNOPSIS [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Lists AD (Active Directory) configs for Cloud NetApp Volumes + (BETA) Lists AD (Active Directory) configs for Cloud NetApp Volumes. EXAMPLES - The following command lists AD configs in the given project and location + The following command lists AD configs in the given project and location: $ gcloud beta netapp active-directories list --location=us-central1 diff --git a/gcloud/beta/netapp/active-directories/update b/gcloud/beta/netapp/active-directories/update index 9eb83590f..0d28d5a1c 100644 --- a/gcloud/beta/netapp/active-directories/update +++ b/gcloud/beta/netapp/active-directories/update @@ -18,11 +18,11 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (BETA) Updates AD (Active Directory) configs for Cloud NetApp Volumes + (BETA) Updates AD (Active Directory) configs for Cloud NetApp Volumes. EXAMPLES The following command updates an AD config in the given project and - location with specified arguments + location with specified arguments: $ gcloud beta netapp active-directories update AD_NAME \ --location=us-central1 --domain=new-domain.com --dns=1.1.1.1 \ diff --git a/gcloud/beta/network-management/connectivity-tests/create b/gcloud/beta/network-management/connectivity-tests/create index dcbdc9463..c57c599ad 100644 --- a/gcloud/beta/network-management/connectivity-tests/create +++ b/gcloud/beta/network-management/connectivity-tests/create @@ -76,8 +76,7 @@ REQUIRED FLAGS --destination-ip-address=DESTINATION_IP_ADDRESS The IP address of the destination which can be an external or - internal IP. An IPv6 address is only allowed when the test's - destination is a global load balancer VIP. + internal IP. At least one of these must be specified: @@ -102,8 +101,6 @@ REQUIRED FLAGS --source-ip-address=SOURCE_IP_ADDRESS The IP address of the source which can be an external or internal IP. - An IPv6 address is only allowed when the test's destination is a - global load balancer VIP. OPTIONAL FLAGS --async diff --git a/gcloud/beta/network-management/connectivity-tests/update b/gcloud/beta/network-management/connectivity-tests/update index 8dce29ed7..72d36b292 100644 --- a/gcloud/beta/network-management/connectivity-tests/update +++ b/gcloud/beta/network-management/connectivity-tests/update @@ -151,8 +151,7 @@ FLAGS --destination-ip-address=DESTINATION_IP_ADDRESS The IP address of the destination which can be an external or - internal IP. An IPv6 address is only allowed when the test's - destination is a global load balancer VIP. + internal IP. At most one of these can be specified: @@ -210,8 +209,6 @@ FLAGS --source-ip-address=SOURCE_IP_ADDRESS The IP address of the source which can be an external or internal IP. - An IPv6 address is only allowed when the test's destination is a - global load balancer VIP. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/beta/recommender/recommendations/list b/gcloud/beta/recommender/recommendations/list index 916cb92bc..b86f43873 100644 --- a/gcloud/beta/recommender/recommendations/list +++ b/gcloud/beta/recommender/recommendations/list @@ -48,10 +48,10 @@ REQUIRED FLAGS FLAGS --recommender=RECOMMENDER - Recommender to list recommendations for. If no recommender is - specified, recommendations for all supported recommenders is listed. - Supported recommenders can be found here: - https://cloud.google.com/recommender/docs/recommenders + Recommender to list recommendations for. Supported recommenders can be + found here: https://cloud.google.com/recommender/docs/recommenders. For + alpha and beta users: If no recommender is specified, recommendations + for all supported recommenders are listed. LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/beta/redis/clusters/create b/gcloud/beta/redis/clusters/create new file mode 100644 index 000000000..494a0e79d --- /dev/null +++ b/gcloud/beta/redis/clusters/create @@ -0,0 +1,132 @@ +NAME + gcloud beta redis clusters create - create a new Memorystore for Redis + Cluster instance + +SYNOPSIS + gcloud beta redis clusters create (CLUSTER : --region=REGION) + --network=NETWORK --shard-count=SHARD_COUNT [--async] + [--auth-mode=AUTH_MODE] [--replica-count=REPLICA_COUNT] + [--transit-encryption-mode=TRANSIT_ENCRYPTION_MODE] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a new Memorystore for Redis Cluster instance, and uses + Private Service Connect service connectivity automation to automate + connectivity for instances. + + This command can fail for the following reasons: + ▪ A cluster with the same name already exists. + ▪ The active account does not have permission to create clusters. + ▪ Some required APIs not enabled yet. + ▪ No connection policy defined yet on the network and in the region a + cluster will be created. + ▪ Miss the steps for creating and configuring a service account (to + grant permissions) in both host project and service project, if a + shared VPC network is used. + + Refer to + https://cloud.google.com/memorystore/docs/cluster/networking#prerequisites_required_before_creating_a_cluster + for prerequisites. + +EXAMPLES + To create a cluster with name my-redis-cluster in region us-central1 with 3 + shards and with a discovery endpoint created on network "default", run: + + $ gcloud beta redis clusters create my-redis-cluster \ + --region=us-central1 --shard-count=3 \ + --network=projects/NETWORK_PROJECT_ID/global/networks/default + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to create. Your cluster ID must be 1 to 63 characters and use only + lowercase letters, numbers, or hyphens. It must start with a lowercase + letter and end with a lowercase letter or number. The arguments in this + group can be used to specify the attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +REQUIRED FLAGS + --network=NETWORK + The network used to create your instance. It must use the format: + projects/NETWORK_PROJECT_ID/global/networks/NETWORK_ID. The network ID + used here must match the network ID used by the service connection + policy. Otherwise, the create operation fails + + --shard-count=SHARD_COUNT + The shard count of the cluster. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --auth-mode=AUTH_MODE + Available authorization mode of a Redis cluster. AUTH_MODE must be one + of: + + disabled + Authorization is disabled for the cluster. + + iam-auth + IAM basic authorization is enabled for the cluster. + + --replica-count=REPLICA_COUNT + The replica count of each shard. + + --transit-encryption-mode=TRANSIT_ENCRYPTION_MODE + Transit encryption mode used for the Redis cluster. If not provided, + encryption is disabled for the cluster. TRANSIT_ENCRYPTION_MODE must be + one of: + + disabled + In-transit encryption is disabled for the cluster. + + server-authentication + The cluster uses server managed encryption for in-transit + encryption. + +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. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters create + diff --git a/gcloud/beta/redis/clusters/delete b/gcloud/beta/redis/clusters/delete new file mode 100644 index 000000000..2f8533c13 --- /dev/null +++ b/gcloud/beta/redis/clusters/delete @@ -0,0 +1,78 @@ +NAME + gcloud beta redis clusters delete - delete a Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud beta redis clusters delete (CLUSTER : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a Memorystore for Redis Cluster instance. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To delete a cluster with the name my-redis-cluster in your default region, + run: + + $ gcloud beta redis clusters delete my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to delete. The arguments in this group can be used to specify the + attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters delete + diff --git a/gcloud/beta/redis/clusters/describe b/gcloud/beta/redis/clusters/describe new file mode 100644 index 000000000..46bdfee87 --- /dev/null +++ b/gcloud/beta/redis/clusters/describe @@ -0,0 +1,75 @@ +NAME + gcloud beta redis clusters describe - show metadata for a Memorystore for + Redis Cluster instance + +SYNOPSIS + gcloud beta redis clusters describe (CLUSTER : --region=REGION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Show metadata for a Memorystore for Redis Cluster instance. + + Displays all metadata associated with a cluster given a valid cluster name. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To display the metadata for a cluster with the name my-redis-cluster in the + default region, run: + + $ gcloud beta redis clusters describe my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster you want + to describe. The arguments in this group can be used to specify the + attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +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. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters describe + diff --git a/gcloud/beta/redis/clusters/get-cluster-certificate-authority b/gcloud/beta/redis/clusters/get-cluster-certificate-authority new file mode 100644 index 000000000..10f9dd09e --- /dev/null +++ b/gcloud/beta/redis/clusters/get-cluster-certificate-authority @@ -0,0 +1,76 @@ +NAME + gcloud beta redis clusters get-cluster-certificate-authority - get the + certificate authority information for a Memorystore for Redis Cluster + instance + +SYNOPSIS + gcloud beta redis clusters get-cluster-certificate-authority + (CLUSTER : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Get the certificate authority information for a Memorystore for + Redis Cluster instance. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to access the given + cluster. + +EXAMPLES + To get the metadata for a cluster with the name my-redie-cluster in the + default region, run: + + $ gcloud beta redis clusters get-cluster-certificate-authority \ + my-redis-cluster + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the cluster. The + arguments in this group can be used to specify the attributes of this + 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +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. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters get-cluster-certificate-authority + diff --git a/gcloud/beta/redis/clusters/help b/gcloud/beta/redis/clusters/help new file mode 100644 index 000000000..bd82166b9 --- /dev/null +++ b/gcloud/beta/redis/clusters/help @@ -0,0 +1,42 @@ +NAME + gcloud beta redis clusters - manage Memorystore for Redis Cluster instances + +SYNOPSIS + gcloud beta redis clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Memorystore for Redis Cluster instances. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + (BETA) Create a new Memorystore for Redis Cluster instance. + + delete + (BETA) Delete a Memorystore for Redis Cluster instance. + + describe + (BETA) Show metadata for a Memorystore for Redis Cluster instance. + + get-cluster-certificate-authority + (BETA) Get the certificate authority information for a Memorystore for + Redis Cluster instance. + + list + (BETA) List Memorystore for Redis Cluster instances. + + update + (BETA) Update Memorystore Cluster for Redis instance. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters + diff --git a/gcloud/beta/redis/clusters/list b/gcloud/beta/redis/clusters/list new file mode 100644 index 000000000..953ec3084 --- /dev/null +++ b/gcloud/beta/redis/clusters/list @@ -0,0 +1,88 @@ +NAME + gcloud beta redis clusters list - list Memorystore for Redis Cluster + instances + +SYNOPSIS + gcloud beta redis clusters list [--region=REGION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List all clusters under the specified project and region. + + To specify the maximum number of clusters to list, use the --limit flag. + +EXAMPLES + To list up to five clusters, run: + + $ gcloud beta redis clusters list --limit=5 + +FLAGS + Region resource - The region of the clusters to display. 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 --region on the command line with a fully + specified name; + ◆ set the property redis/region with a fully specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --region=REGION + ID of the region or fully qualified identifier for the region. + + To set the region attribute: + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +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. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters list + diff --git a/gcloud/beta/redis/clusters/update b/gcloud/beta/redis/clusters/update new file mode 100644 index 000000000..89e2e3885 --- /dev/null +++ b/gcloud/beta/redis/clusters/update @@ -0,0 +1,86 @@ +NAME + gcloud beta redis clusters update - update Memorystore Cluster for Redis + instance + +SYNOPSIS + gcloud beta redis clusters update (CLUSTER : --region=REGION) [--async] + [--replica-count=REPLICA_COUNT] [--shard-count=SHARD_COUNT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update the metadata and/or configuration parameters of a Redis + cluster. + + This command can fail for the following reasons: + ▪ The cluster specified does not exist. + ▪ The active account does not have permission to update the given + cluster. + +EXAMPLES + To update a Redis cluster with 5 shard and 2 replica, run: + + $ gcloud beta redis clusters update my-redis-cluster \ + --shard-count=5 --replica-count=2 + +POSITIONAL ARGUMENTS + Cluster resource - Arguments and flags that specify the Memorystore Redis + cluster you want to update. The arguments in this group can be used to + specify the attributes of this 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 cluster on the command line with a fully + specified name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + This must be specified. + + CLUSTER + ID of the cluster or fully qualified identifier for the cluster. + + To set the cluster attribute: + ▸ provide the argument cluster on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The name of the Redis region of the cluster. Overrides the default + redis/region property value for this command invocation. + + To set the region attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --region on the command line; + ▸ set the property redis/region. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --replica-count=REPLICA_COUNT + The replica count of each shard. + + --shard-count=SHARD_COUNT + The shard count of the cluster. + +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. + +API REFERENCE + This command uses the redis/v1beta1 API. The full documentation for this + API can be found at: https://cloud.google.com/memorystore/docs/redis/ + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha redis clusters update + diff --git a/gcloud/beta/redis/help b/gcloud/beta/redis/help index d102aea6b..50034df67 100644 --- a/gcloud/beta/redis/help +++ b/gcloud/beta/redis/help @@ -15,6 +15,9 @@ GCLOUD WIDE FLAGS GROUPS GROUP is one of the following: + clusters + (BETA) Manage Memorystore for Redis Cluster instances. + instances (BETA) Manage Cloud Memorystore Redis instances. diff --git a/gcloud/beta/sql/instances/create b/gcloud/beta/sql/instances/create index da5e6e0bb..1ec1e0d73 100644 --- a/gcloud/beta/sql/instances/create +++ b/gcloud/beta/sql/instances/create @@ -384,9 +384,8 @@ FLAGS --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default - value is 7 for Enterprise edition instances. For Enterprise_Plus - Postgres and MySQL instances, default values are 15 and 8 respectively. - Applicable only if --no-backups is not specified. + value is 7 for Enterprise edition instances. For Enterprise_Plus, + default value is 15. Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between 1 @@ -394,9 +393,7 @@ FLAGS logs are stored on disk, storage size for transaction logs could increase when the number of days for log retention increases. For Enterprise, default and max retention values are 7 and 7 respectively. - For MySQL Enterprise_Plus, default and max retention values are 7 and - 7. For Postgres Enterprise_Plus, default and max retention values are - 14 and 35. + For Enterprise_Plus, default and max retention values are 14 and 35. --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/beta/sql/instances/patch b/gcloud/beta/sql/instances/patch index 6569c3988..1e39b2b0c 100644 --- a/gcloud/beta/sql/instances/patch +++ b/gcloud/beta/sql/instances/patch @@ -481,8 +481,8 @@ FLAGS --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default value is 7 for Enterprise edition instances. For - Enterprise_Plus Postgres and MySQL instances, default values are 15 - and 8 respectively. Applicable only if --no-backups is not specified. + Enterprise_Plus, default value is 15. Applicable only if --no-backups + is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between @@ -490,9 +490,8 @@ FLAGS enabled. If logs are stored on disk, storage size for transaction logs could increase when the number of days for log retention increases. For Enterprise, default and max retention values are 7 and - 7 respectively. For MySQL Enterprise_Plus, default and max retention - values are 7 and 7. For Postgres Enterprise_Plus, default and max - retention values are 14 and 35. + 7 respectively. For Enterprise_Plus, default and max retention values + are 14 and 35. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/bigtable/backups/copy b/gcloud/bigtable/backups/copy new file mode 100644 index 000000000..83282c1e0 --- /dev/null +++ b/gcloud/bigtable/backups/copy @@ -0,0 +1,163 @@ +NAME + gcloud bigtable backups copy - copy a Cloud Bigtable backup to a new backup + +SYNOPSIS + gcloud bigtable backups copy + (--destination-backup=DESTINATION_BACKUP + : --destination-cluster=DESTINATION_CLUSTER + --destination-instance=DESTINATION_INSTANCE + --destination-project=DESTINATION_PROJECT) + (--expiration-date=EXPIRATION_DATE + | --retention-period=RETENTION_PERIOD) + (--source-backup=SOURCE_BACKUP : --source-cluster=SOURCE_CLUSTER + --source-instance=SOURCE_INSTANCE --source-project=SOURCE_PROJECT) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command creates a copy of a Cloud Bigtable backup. + +EXAMPLES + To copy a backup within the same project, run: + + $ gcloud bigtable backups copy --source-instance=SOURCE_INSTANCE \ + --source-cluster=SOURCE_CLUSTER --source-backup=SOURCE_BACKUP \ + --destination-instance=DESTINATION_INSTANCE \ + --destination-cluster=DESTINATION_CLUSTER \ + --destination-backup=DESTINATION_BACKUP \ + --expiration-date=2023-09-01T10:49:41Z + + To copy a backup to a different project, run: + + $ gcloud bigtable backups copy \ + --source-backup=projects/SOURCE_PROJECT/instances/\ + SOURCE_INSTANCE/clusters/SOURCE_CLUSTER/backups/SOURCE_BACKUP \ + --destination-backup=projects/DESTINATION_PROJECT/instances/\ + DESTINATION_INSTANCE/clusters/DESTINATION_CLUSTER/backups/\ + DESTINATION_BACKUP --expiration-date=2022-08-01T10:49:41Z + + To set retention period and run asyncronously, run: + + $ gcloud bigtable backups copy \ + --source-backup=projects/SOURCE_PROJECT/instances/\ + SOURCE_INSTANCE/clusters/SOURCE_CLUSTER/backups/SOURCE_BACKUP \ + --destination-backup=projects/DESTINATION_PROJECT/instances/\ + DESTINATION_INSTANCE/clusters/DESTINATION_CLUSTER/backups/\ + DESTINATION_BACKUP --retention-period=2w --async + +REQUIRED FLAGS + Backup resource - The destination backup to copy to. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + --destination-backup=DESTINATION_BACKUP + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument --destination-backup on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --destination-cluster=DESTINATION_CLUSTER + Cloud Bigtable cluster for the backup. + + To set the cluster attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-cluster on the command line. + + --destination-instance=DESTINATION_INSTANCE + Cloud Bigtable instance for the backup. + + To set the instance attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-instance on the command line; + ▸ provide the argument --source-instance on the command line. + + --destination-project=DESTINATION_PROJECT + Project ID of the Google Cloud project for the backup. + + To set the project attribute: + ▸ provide the argument --destination-backup on the command line + with a fully specified name; + ▸ provide the argument --destination-project on the command line; + ▸ provide the argument --source-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + + Exactly one of these must be specified: + + --expiration-date=EXPIRATION_DATE + Expiration time of the backup, must be at least 6 hours and at most + 30 days from the time the source backup is created. See $ gcloud + topic datetimes for information on date/time formats. + + --retention-period=RETENTION_PERIOD + Retention period of the backup relative from now, must be at least 6 + hours and at most 30 days from the time the source backup is created. + See $ gcloud topic datetimes for information on duration formats. + + Backup resource - The source backup to copy from. The arguments in this + group can be used to specify the attributes of this resource. + + This must be specified. + + --source-backup=SOURCE_BACKUP + ID of the backup or fully qualified identifier for the backup. + + To set the backup attribute: + ▸ provide the argument --source-backup on the command line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --source-cluster=SOURCE_CLUSTER + Cloud Bigtable cluster for the backup. + + To set the cluster attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-cluster on the command line. + + --source-instance=SOURCE_INSTANCE + Cloud Bigtable instance for the backup. + + To set the instance attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-instance on the command line; + ▸ provide the argument --destination-instance on the command line. + + --source-project=SOURCE_PROJECT + Project ID of the Google Cloud project for the backup. + + To set the project attribute: + ▸ provide the argument --source-backup on the command line with a + fully specified name; + ▸ provide the argument --source-project on the command line; + ▸ provide the argument --destination-project on the command line; + ▸ provide the argument --project on the command line; + ▸ set the property core/project. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + +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 bigtable backups copy + + $ gcloud beta bigtable backups copy + diff --git a/gcloud/bigtable/backups/help b/gcloud/bigtable/backups/help index c4283868d..eafd894da 100644 --- a/gcloud/bigtable/backups/help +++ b/gcloud/bigtable/backups/help @@ -18,6 +18,9 @@ COMMANDS add-iam-policy-binding Add an IAM policy binding to a Cloud Bigtable Backup. + copy + Copy a Cloud Bigtable backup to a new backup. + create Creates a backup of a Cloud Bigtable table. diff --git a/gcloud/compute/target-http-proxies/create b/gcloud/compute/target-http-proxies/create index 33edce3ef..5341a4032 100644 --- a/gcloud/compute/target-http-proxies/create +++ b/gcloud/compute/target-http-proxies/create @@ -53,7 +53,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external Application load balancer, the minimum allowed + For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. At most one of these can be specified: diff --git a/gcloud/compute/target-http-proxies/update b/gcloud/compute/target-http-proxies/update index 7cb7e2ef9..489bcaefa 100644 --- a/gcloud/compute/target-http-proxies/update +++ b/gcloud/compute/target-http-proxies/update @@ -50,7 +50,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external Application load balancer, the minimum + seconds. For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. diff --git a/gcloud/compute/target-https-proxies/create b/gcloud/compute/target-https-proxies/create index dd50aed21..dd40a46b4 100644 --- a/gcloud/compute/target-https-proxies/create +++ b/gcloud/compute/target-https-proxies/create @@ -81,7 +81,7 @@ OPTIONAL FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 seconds. - For global external Application load balancer, the minimum allowed + For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. --quic-override=QUIC_OVERRIDE; default="NONE" @@ -100,8 +100,8 @@ OPTIONAL FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the HTTPS proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target HTTPS proxy. + and load balancers that are using the HTTPS proxy. The SSL policy must + exist and cannot be deleted while referenced by a target HTTPS proxy. At most one of these can be specified: diff --git a/gcloud/compute/target-https-proxies/update b/gcloud/compute/target-https-proxies/update index 22849f9ce..eacf466d3 100644 --- a/gcloud/compute/target-https-proxies/update +++ b/gcloud/compute/target-https-proxies/update @@ -170,7 +170,7 @@ FLAGS Represents the maximum amount of time that a TCP connection can be idle between the (downstream) client and the target HTTP proxy. If an HTTP keepalive timeout is not specified, the default value is 610 - seconds. For global external Application load balancer, the minimum + seconds. For global external Application Load Balancers, the minimum allowed value is 5 seconds and the maximum allowed value is 1200 seconds. @@ -182,8 +182,9 @@ FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the HTTPS proxy load balancer. The SSL policy must exist and - cannot be deleted while referenced by a target HTTPS proxy. + and load balancers that are using the HTTPS proxy. The SSL policy + must exist and cannot be deleted while referenced by a target HTTPS + proxy. At most one of these can be specified: diff --git a/gcloud/compute/target-ssl-proxies/create b/gcloud/compute/target-ssl-proxies/create index e8b865168..47d8a06d6 100644 --- a/gcloud/compute/target-ssl-proxies/create +++ b/gcloud/compute/target-ssl-proxies/create @@ -76,8 +76,8 @@ OPTIONAL FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the SSL proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target SSL proxy. + and load balancers that are using the SSL proxy. The SSL policy must + exist and cannot be deleted while referenced by a target SSL proxy. At most one of these can be specified: diff --git a/gcloud/compute/target-ssl-proxies/help b/gcloud/compute/target-ssl-proxies/help index 014c0ce36..04a05bb56 100644 --- a/gcloud/compute/target-ssl-proxies/help +++ b/gcloud/compute/target-ssl-proxies/help @@ -6,11 +6,11 @@ SYNOPSIS gcloud compute target-ssl-proxies COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List, create, and delete target SSL target proxies for SSL Proxy Load - Balancing. + List, create, and delete target SSL target proxies for proxy Network Load + Balancers. - For more information about target SSL proxies, see the SSL proxy load - balancer documentation (https://cloud.google.com/load-balancing/docs/ssl/). + For more information about target SSL proxies, see the proxy Network Load + Balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). See also: Target SSL proxies API (https://cloud.google.com/compute/docs/reference/rest/v1/targetSslProxies). diff --git a/gcloud/compute/target-ssl-proxies/update b/gcloud/compute/target-ssl-proxies/update index ee0904dbd..1ff48346f 100644 --- a/gcloud/compute/target-ssl-proxies/update +++ b/gcloud/compute/target-ssl-proxies/update @@ -47,8 +47,8 @@ FLAGS --ssl-policy=SSL_POLICY A reference to an SSL policy resource that defines the server-side support for SSL features and affects the connections between clients - and the SSL proxy load balancer. The SSL policy must exist and cannot - be deleted while referenced by a target SSL proxy. + and load balancers that are using the SSL proxy. The SSL policy must + exist and cannot be deleted while referenced by a target SSL proxy. At most one of these can be specified: diff --git a/gcloud/compute/target-tcp-proxies/help b/gcloud/compute/target-tcp-proxies/help index 70f7cd549..9593fe881 100644 --- a/gcloud/compute/target-tcp-proxies/help +++ b/gcloud/compute/target-tcp-proxies/help @@ -6,10 +6,11 @@ SYNOPSIS gcloud compute target-tcp-proxies COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - List, create, and delete target TCP proxies for TCP Proxy Load Balancing. + List, create, and delete target TCP proxies for proxy Network Load + Balancers. - For more information about target TCP proxies, see the TCP proxy load - balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). + For more information about target TCP proxies, see the proxy Network Load + Balancer documentation (https://cloud.google.com/load-balancing/docs/tcp/). See also: Target TCP proxies API (https://cloud.google.com/compute/docs/reference/rest/v1/targetTcpProxies). diff --git a/gcloud/config/get b/gcloud/config/get index f5e542595..8cf049d2a 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -414,6 +414,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/config/help b/gcloud/config/help index 78599b81f..b398240e9 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -446,6 +446,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/config/list b/gcloud/config/list index e2ca2c55a..985116cbb 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -458,6 +458,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/config/set b/gcloud/config/set index 40adac15a..cf73165db 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -461,6 +461,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/config/unset b/gcloud/config/unset index f7075d9cd..0a0d59055 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -422,6 +422,9 @@ AVAILABLE PROPERTIES Overrides API endpoint for gcloud ids command group. Defaults to https://ids.googleapis.com/ + inframanager + Overrides API endpoint for gcloud infra-manager command group. + krmapihosting Overrides API endpoint for gcloud anthos config controller command group. Defaults to https://krmapihosting.googleapis.com/ diff --git a/gcloud/container/aws/node-pools/create b/gcloud/container/aws/node-pools/create index a15744379..90e07adec 100644 --- a/gcloud/container/aws/node-pools/create +++ b/gcloud/container/aws/node-pools/create @@ -10,7 +10,6 @@ SYNOPSIS --max-pods-per-node=MAX_PODS_PER_NODE --node-version=NODE_VERSION --subnet-id=SUBNET_ID (--max-nodes=MAX_NODES --min-nodes=MIN_NODES) [--annotations=ANNOTATION,[ANNOTATION,...]] [--async] - [--instance-type=INSTANCE_TYPE] [--node-labels=NODE_LABEL,[NODE_LABEL,...]] [--node-taints=NODE_TAINT,[NODE_TAINT,...]] [--root-volume-iops=ROOT_VOLUME_IOPS] @@ -23,6 +22,8 @@ SYNOPSIS [--validate-only] [--autoscaling-metrics-granularity=AUTOSCALING_METRICS_GRANULARITY : --autoscaling-metrics=[AUTOSCALING_METRIC,...]] + [--instance-type=INSTANCE_TYPE + | --spot-instance-types=[INSTANCE_TYPE,...]] [--proxy-secret-arn=PROXY_SECRET_ARN --proxy-secret-version-id=PROXY_SECRET_VERSION_ID] [GCLOUD_WIDE_FLAG ...] @@ -118,11 +119,6 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. - Node pool instance configuration - - --instance-type=INSTANCE_TYPE - AWS EC2 instance type for the node pool's nodes. - --node-labels=NODE_LABEL,[NODE_LABEL,...] Labels assigned to nodes of the node pool. @@ -181,6 +177,20 @@ OPTIONAL FLAGS If granularity is specified but not any metrics, all metrics are enabled. + Node pool instance configuration + + At most one of these can be specified: + + --instance-type=INSTANCE_TYPE + AWS EC2 instance type for the node pool's nodes. + + --spot-instance-types=[INSTANCE_TYPE,...] + List of AWS EC2 instance types for creating a spot node pool's nodes. + The specified instance types must have the same number of CPUs and + memory. You can use the Amazon EC2 Instance Selector tool + (https://github.com/aws/amazon-ec2-instance-selector) to choose + instance types with matching CPU and memory configurations. + Proxy config --proxy-secret-arn=PROXY_SECRET_ARN diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 81fa19cb5..17087ada5 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -778,7 +778,7 @@ FLAGS 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]. + [TIER_UNSPECIFIED,TIER_1]. See https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration @@ -1051,6 +1051,9 @@ FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -1081,6 +1084,19 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. diff --git a/gcloud/container/clusters/update b/gcloud/container/clusters/update index 3ae1a6f12..72cbe81be 100644 --- a/gcloud/container/clusters/update +++ b/gcloud/container/clusters/update @@ -361,7 +361,7 @@ REQUIRED FLAGS 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]. + [TIER_UNSPECIFIED,TIER_1]. See https://cloud.google.com/compute/docs/networking/configure-vm-with-high-bandwidth-configuration diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 10fc50e6b..40a4e09bd 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -45,7 +45,7 @@ SYNOPSIS batch-soak-duration=BATCH_SOAK_DURATION,...]] [--system-config-from-file=SYSTEM_CONFIG_FROM_FILE] [--tags=TAG,[TAG,...]] [--threads-per-core=THREADS_PER_CORE] - [--windows-os-version=WINDOWS_OS_VERSION] + [--tpu-topology=TPU_TOPOLOGY] [--windows-os-version=WINDOWS_OS_VERSION] [--workload-metadata=WORKLOAD_METADATA] [--create-pod-ipv4-range=[KEY=VALUE,...] | --pod-ipv4-range=NAME] [--enable-autoscaling --location-policy=LOCATION_POLICY @@ -586,6 +586,9 @@ FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -616,6 +619,19 @@ FLAGS net.ipv4.tcp_wmem Any positive integer tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. @@ -636,6 +652,12 @@ FLAGS The number of visible threads per physical core for each node. To disable simultaneous multithreading (SMT) set this to 1. + --tpu-topology=TPU_TOPOLOGY + The desired physical topology for the PodSlice. + + $ gcloud container node-pools create node-pool-1 \ + --cluster=example-cluster --tpu-topology + --windows-os-version=WINDOWS_OS_VERSION Specifies the Windows Server Image to use when creating a Windows node pool. Valid variants can be "ltsc2019", "ltsc2022". It means using diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 91eeb8360..49cf74641 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -157,6 +157,9 @@ REQUIRED FLAGS sysctl: net.core.somaxconn: '2048' net.ipv4.tcp_rmem: '4096 87380 6291456' + hugepageConfig: + hugepage_size2m: '1024' + hugepage_size1g: '2' List of supported kubelet configs in 'kubeletConfig'. @@ -190,6 +193,19 @@ REQUIRED FLAGS tuple net.ipv4.tcp_tw_reuse Must be {0, 1} + List of supported hugepage size in 'hugepageConfig'. + + KEY VALUE + hugepage_size2m Number of 2M huge pages, any positive integer + hugepage_size1g Number of 1G huge pages, any positive integer + + Allocated hugepage size should not exceed 60% of available memory on + the node. For example, c2d-highcpu-4 has 8GB memory, total allocated + hugepage of 2m and 1g should not exceed 8GB * 0.6 = 4.8GB. + + 1G hugepages are only available in following machine familes: c3, m2, + c2d, c3d, h3, m3, a2, a3, g2. + Note, updating the system configuration of an existing node pool requires recreation of the nodes which which might cause a disruption. diff --git a/gcloud/dataflow/jobs/help b/gcloud/dataflow/jobs/help index 2464e384d..c96adfcbb 100644 --- a/gcloud/dataflow/jobs/help +++ b/gcloud/dataflow/jobs/help @@ -34,6 +34,9 @@ COMMANDS show Shows a short description of the given job. + update-options + Update pipeline options on-the-fly for running Dataflow jobs. + NOTES These variants are also available: diff --git a/gcloud/dataflow/jobs/update-options b/gcloud/dataflow/jobs/update-options new file mode 100644 index 000000000..d119c073b --- /dev/null +++ b/gcloud/dataflow/jobs/update-options @@ -0,0 +1,64 @@ +NAME + gcloud dataflow jobs update-options - update pipeline options on-the-fly + for running Dataflow jobs + +SYNOPSIS + gcloud dataflow jobs update-options JOB_ID + [--max-num-workers=MAX_NUM_WORKERS] [--min-num-workers=MIN_NUM_WORKERS] + [--region=REGION_ID] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command can modify properties of running Dataflow jobs. Currently, + only updating autoscaling settings for Streaming Engine jobs is supported. + + Adjust the autoscaling settings for Streaming Engine Dataflow jobs by + providing at-least one of --min-num-workers or --max-num-workers (or both). + Allow a few minutes for the changes to take effect. + + Note that autoscaling settings can only be modified on-the-fly for + Streaming Engine jobs. Attempts to modify batch job or Streaming Appliance + jobs will fail. + +EXAMPLES + Modify autoscaling settings to scale between 5-10 workers: + + $ gcloud dataflow jobs update-options --min-num-workers=5 \ + --max-num-workers=10 + + Require a job to use at least 2 workers: + + $ gcloud dataflow jobs update-options --min-num-workers=2 + + Require a job to use at most 20 workers: + + $ gcloud dataflow jobs update-options --max-num-workers=20 + +POSITIONAL ARGUMENTS + JOB_ID + Job ID to operate on. + +FLAGS + --max-num-workers=MAX_NUM_WORKERS + Upper-bound for autoscaling, between 1-1000. Only supported for + streaming-engine jobs. + + --min-num-workers=MIN_NUM_WORKERS + Lower-bound for autoscaling, between 1-1000. Only supported for + streaming-engine jobs. + + --region=REGION_ID + Region ID of the job's regional endpoint. Defaults to 'us-central1'. + +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 + This variant is also available: + + $ gcloud beta dataflow jobs update-options + diff --git a/gcloud/dns/record-sets/create b/gcloud/dns/record-sets/create index c89b6a6a0..f83a253a3 100644 --- a/gcloud/dns/record-sets/create +++ b/gcloud/dns/record-sets/create @@ -127,8 +127,9 @@ REQUIRED FLAGS semicolon-delimited list of the format "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP address or a reference to a forwarding rule of the format - FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full - resource path of the forwarding rule. + "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@{region}", + "FORWARDING_RULE_NAME@global", or the full resource path of the + forwarding rule. Configuration for primary backup routing policy diff --git a/gcloud/dns/record-sets/update b/gcloud/dns/record-sets/update index df10023c6..a4538dfd6 100644 --- a/gcloud/dns/record-sets/update +++ b/gcloud/dns/record-sets/update @@ -95,8 +95,9 @@ REQUIRED FLAGS semicolon-delimited list of the format "${region}=${rrdata},${rrdata}". Each rrdata can either be an IP address or a reference to a forwarding rule of the format - FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@region", or the full - resource path of the forwarding rule. + "FORWARDING_RULE_NAME", "FORWARDING_RULE_NAME@{region}", + "FORWARDING_RULE_NAME@global", or the full resource path of the + forwarding rule. Configuration for primary backup routing policy diff --git a/gcloud/network-management/connectivity-tests/create b/gcloud/network-management/connectivity-tests/create index 71887e234..7688b50d8 100644 --- a/gcloud/network-management/connectivity-tests/create +++ b/gcloud/network-management/connectivity-tests/create @@ -76,8 +76,7 @@ REQUIRED FLAGS --destination-ip-address=DESTINATION_IP_ADDRESS The IP address of the destination which can be an external or - internal IP. An IPv6 address is only allowed when the test's - destination is a global load balancer VIP. + internal IP. At least one of these must be specified: @@ -102,8 +101,6 @@ REQUIRED FLAGS --source-ip-address=SOURCE_IP_ADDRESS The IP address of the source which can be an external or internal IP. - An IPv6 address is only allowed when the test's destination is a - global load balancer VIP. OPTIONAL FLAGS --async diff --git a/gcloud/network-management/connectivity-tests/update b/gcloud/network-management/connectivity-tests/update index e92c38927..e6d8d7b05 100644 --- a/gcloud/network-management/connectivity-tests/update +++ b/gcloud/network-management/connectivity-tests/update @@ -151,8 +151,7 @@ FLAGS --destination-ip-address=DESTINATION_IP_ADDRESS The IP address of the destination which can be an external or - internal IP. An IPv6 address is only allowed when the test's - destination is a global load balancer VIP. + internal IP. At most one of these can be specified: @@ -210,8 +209,6 @@ FLAGS --source-ip-address=SOURCE_IP_ADDRESS The IP address of the source which can be an external or internal IP. - An IPv6 address is only allowed when the test's destination is a - global load balancer VIP. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/sql/instances/create b/gcloud/sql/instances/create index cc4b9432f..258b736f3 100644 --- a/gcloud/sql/instances/create +++ b/gcloud/sql/instances/create @@ -362,9 +362,8 @@ FLAGS --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default - value is 7 for Enterprise edition instances. For Enterprise_Plus - Postgres and MySQL instances, default values are 15 and 8 respectively. - Applicable only if --no-backups is not specified. + value is 7 for Enterprise edition instances. For Enterprise_Plus, + default value is 15. Applicable only if --no-backups is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between 1 @@ -372,9 +371,7 @@ FLAGS logs are stored on disk, storage size for transaction logs could increase when the number of days for log retention increases. For Enterprise, default and max retention values are 7 and 7 respectively. - For MySQL Enterprise_Plus, default and max retention values are 7 and - 7. For Postgres Enterprise_Plus, default and max retention values are - 14 and 35. + For Enterprise_Plus, default and max retention values are 14 and 35. --root-password=ROOT_PASSWORD Root Cloud SQL user's password. diff --git a/gcloud/sql/instances/patch b/gcloud/sql/instances/patch index 88acdfcf4..133254f5d 100644 --- a/gcloud/sql/instances/patch +++ b/gcloud/sql/instances/patch @@ -439,8 +439,8 @@ FLAGS --retained-backups-count=RETAINED_BACKUPS_COUNT How many backups to keep. The valid range is between 1 and 365. Default value is 7 for Enterprise edition instances. For - Enterprise_Plus Postgres and MySQL instances, default values are 15 - and 8 respectively. Applicable only if --no-backups is not specified. + Enterprise_Plus, default value is 15. Applicable only if --no-backups + is not specified. --retained-transaction-log-days=RETAINED_TRANSACTION_LOG_DAYS How many days of transaction logs to keep. The valid range is between @@ -448,9 +448,8 @@ FLAGS enabled. If logs are stored on disk, storage size for transaction logs could increase when the number of days for log retention increases. For Enterprise, default and max retention values are 7 and - 7 respectively. For MySQL Enterprise_Plus, default and max retention - values are 7 and 7. For Postgres Enterprise_Plus, default and max - retention values are 14 and 35. + 7 respectively. For Enterprise_Plus, default and max retention values + are 14 and 35. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account,