diff --git a/gcloud/_version b/gcloud/_version index 02fea18b5..64c7fdb48 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,8 +1,8 @@ -Google Cloud SDK 425.0.0 -alpha 2023.03.31 -beta 2023.03.31 -bq 2.0.89 +Google Cloud SDK 426.0.0 +alpha 2023.04.10 +beta 2023.04.10 +bq 2.0.90 bundled-python3-unix 3.9.16 -core 2023.03.31 +core 2023.04.10 gcloud-crc32c 1.0.0 gsutil 5.21 diff --git a/gcloud/alpha/alloydb/clusters/create b/gcloud/alpha/alloydb/clusters/create index 3f0c1f5ab..a9ba59909 100644 --- a/gcloud/alpha/alloydb/clusters/create +++ b/gcloud/alpha/alloydb/clusters/create @@ -4,7 +4,8 @@ NAME SYNOPSIS gcloud alpha alloydb clusters create CLUSTER --password=PASSWORD - --region=REGION [--async] [--network=NETWORK] + --region=REGION [--allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME] + [--async] [--network=NETWORK] [--continuous-backup-recovery-window-days=RECOVERY_PERIOD --enable-continuous-backup [--continuous-backup-encryption-key=CONTINUOUS_BACKUP_ENCRYPTION_KEY @@ -41,6 +42,14 @@ REQUIRED FLAGS regions at https://cloud.google.com/sql/docs/instance-locations. OPTIONAL FLAGS + --allocated-ip-range-name=ALLOCATED_IP_RANGE_NAME + The name of the allocated IP range for the private IP AlloyDB cluster. + For example: "google-managed-services-default". If set, the instance + IPs for this cluster will be created in the allocated range. The range + name must comply with RFC 1035. Specifically, the name must be 1-63 + characters long and match the regular expression + [a-z]([-a-z0-9][a-z0-9])?. + --async Return immediately, without waiting for the operation in progress to complete. diff --git a/gcloud/alpha/bigtable/app-profiles/update b/gcloud/alpha/bigtable/app-profiles/update index f49abe7d6..0bbe0d17d 100644 --- a/gcloud/alpha/bigtable/app-profiles/update +++ b/gcloud/alpha/bigtable/app-profiles/update @@ -93,6 +93,10 @@ FLAGS --transactional-writes Allow transactional writes with a Single Cluster Routing policy. + If your app profile has single row transactions enabled, you must + specify this flag when updating that app profile. If you do not + specify this flag, then single row transactions are disabled. + 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/builds/deploy/configure/gke b/gcloud/alpha/builds/deploy/configure/gke deleted file mode 100644 index 7f1ceacfa..000000000 --- a/gcloud/alpha/builds/deploy/configure/gke +++ /dev/null @@ -1,186 +0,0 @@ -NAME - gcloud alpha builds deploy configure gke - configure automated build and - deployment to a target Google Kubernetes Engine cluster - -SYNOPSIS - gcloud alpha builds deploy configure gke --cluster=CLUSTER - --location=LOCATION --repo-name=REPO_NAME --repo-type=REPO_TYPE - (--branch-pattern=REGEX | --tag-pattern=REGEX - | [--pull-request-pattern=REGEX --pull-request-preview - : --comment-control --preview-expiry=PREVIEW_EXPIRY; default=3]) - [--app-name=APP_NAME] [--config=CONFIG] [--dockerfile=DOCKERFILE] - [--expose=EXPOSE] [--gcs-config-staging-dir=GCS_CONFIG_STAGING_DIR] - [--namespace=NAMESPACE] [--repo-owner=REPO_OWNER] [--timeout=TIMEOUT] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Configure automated build and deployment from a repository. This - can be triggered by a Git branch or tag push. - -REQUIRED FLAGS - --cluster=CLUSTER - Name of the target cluster to deploy to. - - --location=LOCATION - Region or zone of the target cluster to deploy to. - - --repo-name=REPO_NAME - Name of the repository. - - --repo-type=REPO_TYPE - Type of repository. - - --repo-owner must be provided if one of the following choices is - selected: - - github - A GitHub (Cloud Build GitHub App) repository connected to - Cloud Build triggers. The deployed image will have the format - 'gcr.io/[PROJECT_ID]/github.com/[REPO_OWNER]/[REPO_NAME]:$COMMIT_SHA'. - - bitbucket_mirrored - A Bitbucket repository connected to Cloud Source - Repositories. The deployed image will have the format - 'gcr.io/[PROJECT_ID]/bitbucket.org/[REPO_OWNER]/[REPO_NAME]:$COMMIT_SHA'. - - github_mirrored - A GitHub repository connected to Cloud Source - Repositories. The deployed image will have the format - 'gcr.io/[PROJECT_ID]/github.com/[REPO_OWNER]/[REPO_NAME]:$COMMIT_SHA'. - - --repo-owner must not be provided if the following is selected: - - csr - A repository on Cloud Source Repositories. The deployed image - will have the format 'gcr.io/[PROJECT_ID]/[REPO_NAME]:$COMMIT_SHA'. - - Connect repositories at - https://console.cloud.google.com/cloud-build/triggers/connect. - - REPO_TYPE must be one of: github, bitbucket_mirrored, github_mirrored, - csr. - - Exactly one of these must be specified: - - --branch-pattern=REGEX - A regular expression specifying which Git branches to match. - - This pattern is used as a regex search for any incoming pushes. For - example, --branch-pattern=foo will match "foo", "foobar", and - "barfoo". Events on a branch that does not match will be ignored. - - The syntax of the regular expressions accepted is the syntax accepted - by RE2 and described at https://github.com/google/re2/wiki/Syntax. - - --tag-pattern=REGEX - A regular expression specifying which Git tags to match. - - This pattern is used as a regex search for any incoming pushes. For - example, --tag-pattern=foo will match "foo", "foobar", and "barfoo". - Events on a tag that does not match will be ignored. - - The syntax of the regular expressions accepted is the syntax accepted - by RE2 and described at https://github.com/google/re2/wiki/Syntax. - - Pull request preview deployment settings - - --pull-request-pattern=REGEX - A regular expression specifying which base Git branch to match for - pull request events. - - This pattern is used as a regex search for the base branch (the - branch you are trying to merge into) for pull request updates. For - example, --pull-request-pattern=foo will match "foo", "foobar", and - "barfoo". - - The syntax of the regular expressions accepted is the syntax - accepted by RE2 and described at - https://github.com/google/re2/wiki/Syntax. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --pull-request-preview - Enables previewing your application for each pull request. - - This configures your application to deploy to a target cluster when - a pull request is created or updated against a branch specified by - the --pull-request-pattern argument. The application will be - deployed to the namespace 'preview-[REPO_NAME]-[PR_NUMBER]'. This - namespace will be deleted after a number of days specified by the - --preview-expiry argument. - - The deployed preview application will still exist even after the - pull request is merged or closed. The preview application will - eventually get cleaned up by a Cloud Scheduler job after the - namespace expires. You can also delete the namespace manually. - - This flag argument must be specified if any of the other arguments - in this group are specified. - - --comment-control - Require a repo collaborator to add '/gcbrun' as a comment in the - pull request in order to run the build. - - --preview-expiry=PREVIEW_EXPIRY; default=3 - Number of days before a pull request preview deployment's namespace - is considered to be expired. An expired namespace will eventually - be deleted. Defaults to 3 days. - -OPTIONAL FLAGS - --app-name=APP_NAME - If specified, the following label is added to the Kubernetes manifests: - 'app.kubernetes.io/name: APP_NAME'. Defaults to the repository name - provided by --repo-name. - - --config=CONFIG - Path to the Kubernetes YAML, or directory containing multiple - Kubernetes YAML files, used to deploy the container image. The path is - relative to the repository root. The files must reference the provided - container image or tag. - - If this field is not set, a default Deployment config and Horizontal - Pod Autoscaler config are used to deploy the image. - - --dockerfile=DOCKERFILE - Path to the Dockerfile to build from, relative to the repository. - - Defaults to './Dockerfile'. - - --expose=EXPOSE - Port that the deployed application listens on. If set, a Kubernetes - Service of type 'LoadBalancer' is created with a single TCP port - mapping that exposes this port. - - --gcs-config-staging-dir=GCS_CONFIG_STAGING_DIR - Path to the Google Cloud Storage subdirectory into which to copy the - configs (suggested base and expanded Kubernetes YAML files) that are - used to stage and deploy your app. If the bucket in this path doesn't - exist, Cloud Build creates it. - - If this field is not set, the configs are written to - gs://[PROJECT_ID]_cloudbuild/deploy/config. - - --namespace=NAMESPACE - Namespace of the target cluster to deploy to. If this field is not set, - the 'default' namespace is used. - - --repo-owner=REPO_OWNER - Owner of the repository. - - --timeout=TIMEOUT - Maximum time a build is run before it times out. For example, "2h15m5s" - is two hours, fifteen minutes, and five seconds. If you do not specify - a unit, seconds is assumed. Overrides the default builds/timeout - property value for this command invocation. - -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/builds/deploy/configure/help b/gcloud/alpha/builds/deploy/configure/help deleted file mode 100644 index 047102a72..000000000 --- a/gcloud/alpha/builds/deploy/configure/help +++ /dev/null @@ -1,28 +0,0 @@ -NAME - gcloud alpha builds deploy configure - configure automated build and - deployment with Google Cloud Build - -SYNOPSIS - gcloud alpha builds deploy configure COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Configure automated build and deployment with Google Cloud Build. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - gke - (ALPHA) Configure automated build and deployment to a target Google - Kubernetes Engine cluster. - -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/builds/deploy/gke b/gcloud/alpha/builds/deploy/gke deleted file mode 100644 index 1e6aaf9a6..000000000 --- a/gcloud/alpha/builds/deploy/gke +++ /dev/null @@ -1,124 +0,0 @@ -NAME - gcloud alpha builds deploy gke - build and deploy to a target Google - Kubernetes Engine cluster - -SYNOPSIS - gcloud alpha builds deploy gke [[SOURCE] --no-source] --cluster=CLUSTER - --location=LOCATION [--app-name=APP_NAME] [--app-version=APP_VERSION] - [--async] [--config=CONFIG] [--expose=EXPOSE] - [--gcs-staging-dir=GCS_STAGING_DIR] [--namespace=NAMESPACE] - [--timeout=TIMEOUT] [--image=IMAGE | --tag=TAG] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Build and deploy to a target Google Kubernetes Engine cluster. - -POSITIONAL ARGUMENTS - At most one of these can be specified: - - [SOURCE] - Location of the source and configs to build and deploy. The location - can be a directory on a local disk or a gzipped archive file - (.tar.gz) in Google Cloud Storage. - - --no-source - Specify that no source should be uploaded with this build. - -REQUIRED FLAGS - --cluster=CLUSTER - Name of the target cluster to deploy to. - - --location=LOCATION - Region or zone of the target cluster to deploy to. - -OPTIONAL FLAGS - --app-name=APP_NAME - If specified, the following label is added to the Kubernetes manifests: - 'app.kubernetes.io/name: APP_NAME'. Defaults to the container image - name provided by --image or --tag without the tag, e.g. 'my-app' for - 'gcr.io/my-project/my-app:1.0.0'. - - --app-version=APP_VERSION - If specified, the following label is added to the Kubernetes manifests: - 'app.kubernetes.io/version: APP_VERSION'. Defaults to the container - image tag provided by --image or --tag. If no image tag is provided and - SOURCE is a valid git repository, defaults to the short revision hash - of the HEAD commit. - - --async - Return immediately, without waiting for the operation in progress to - complete. - - --config=CONFIG - Path to the Kubernetes YAML, or directory containing multiple - Kubernetes YAML files, used to deploy the container image. The path is - relative to the repository root provided by [SOURCE]. The files must - reference the provided container image or tag. - - If this field is not set, a default Deployment config and Horizontal - Pod Autoscaler config are used to deploy the image. - - --expose=EXPOSE - Port that the deployed application listens on. If set, a Kubernetes - Service of type 'LoadBalancer' is created with a single TCP port - mapping that exposes this port. - - --gcs-staging-dir=GCS_STAGING_DIR - Path to the Google Cloud Storage subdirectory into which to copy the - source and configs (suggested base and expanded Kubernetes YAML files) - that are used to stage and deploy your app. If the bucket in this path - doesn't exist, Cloud Build creates it. - - If this field is not set, the source and configs are written to - gs://[PROJECT_ID]_cloudbuild/deploy, where source is written to the - 'source' sub-directory and configs are written to the 'config' - sub-directory. - - --namespace=NAMESPACE - Namespace of the target cluster to deploy to. If this field is not set, - the 'default' namespace is used. - - --timeout=TIMEOUT - Maximum time a build is run before it times out. For example, "2h15m5s" - is 2 hours, 15 minutes, and 5 seconds. If you do not specify a unit, - seconds is assumed. Overrides the default builds/timeout property value - for this command invocation. - - Image to use to build and/or deploy. - - To build an image with a default tag, omit these flags. The resulting - tag will be in the format 'gcr.io/[PROJECT_ID]/[IMAGE]/[TAG], where - [PROJECT_ID] is your project ID, [IMAGE] is the value provided by - `--app-name`, if provided, else it is the name of the provided source - directory, and [TAG] is the value provided by `--app-version`, if - provided, else it is the commit SHA of your provided source. - - At most one of these can be specified: - - --image=IMAGE - Existing container image to deploy. If set, Cloud Build deploys the - container image to the target Kubernetes cluster. The image must be - in the gcr.io/* or *.gcr.io/* namespaces. - - --tag=TAG - Tag to use with a 'docker build' image creation. Cloud Build runs a - remote 'docker build -t $TAG .' command, where $TAG is the tag - provided by this flag. The tag must be in the gcr.io/* or - *.gcr.io/* namespaces. If you specify a tag in this command, your - source must include a Dockerfile. For instructions on building - using a Dockerfile see - https://cloud.google.com/cloud-build/docs/quickstart-docker. - -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/builds/deploy/help b/gcloud/alpha/builds/deploy/help deleted file mode 100644 index a87df3143..000000000 --- a/gcloud/alpha/builds/deploy/help +++ /dev/null @@ -1,34 +0,0 @@ -NAME - gcloud alpha builds deploy - build and deploy images with Google Cloud - Build - -SYNOPSIS - gcloud alpha builds deploy GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Build and deploy images with Google Cloud Build. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -GROUPS - GROUP is one of the following: - - configure - (ALPHA) Configure automated build and deployment with Google Cloud - Build. - -COMMANDS - COMMAND is one of the following: - - gke - (ALPHA) Build and deploy to a target Google Kubernetes Engine cluster. - -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/builds/help b/gcloud/alpha/builds/help index 5093b28c1..9cd3f5729 100644 --- a/gcloud/alpha/builds/help +++ b/gcloud/alpha/builds/help @@ -18,9 +18,6 @@ GROUPS connections (ALPHA) Manage connections for Google Cloud Build. - deploy - (ALPHA) Build and deploy images with Google Cloud Build. - enterprise-config (ALPHA) Manage Enterprise configurations for Google Cloud Build. diff --git a/gcloud/alpha/builds/triggers/create/bitbucketserver b/gcloud/alpha/builds/triggers/create/bitbucketserver index ecda7525d..b139bbe01 100644 --- a/gcloud/alpha/builds/triggers/create/bitbucketserver +++ b/gcloud/alpha/builds/triggers/create/bitbucketserver @@ -11,7 +11,7 @@ SYNOPSIS default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -92,8 +92,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/alpha/builds/triggers/create/cloud-source-repositories b/gcloud/alpha/builds/triggers/create/cloud-source-repositories index 911ff9a32..49d82f247 100644 --- a/gcloud/alpha/builds/triggers/create/cloud-source-repositories +++ b/gcloud/alpha/builds/triggers/create/cloud-source-repositories @@ -10,7 +10,7 @@ SYNOPSIS default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -71,8 +71,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/alpha/builds/triggers/create/github b/gcloud/alpha/builds/triggers/create/github index 376c8b9d4..1615db25f 100644 --- a/gcloud/alpha/builds/triggers/create/github +++ b/gcloud/alpha/builds/triggers/create/github @@ -14,7 +14,7 @@ SYNOPSIS : --enterprise-config=ENTERPRISE_CONFIG]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --include-logs-with-status --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -83,8 +83,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/alpha/builds/triggers/create/gitlab-enterprise b/gcloud/alpha/builds/triggers/create/gitlab-enterprise index 1af5f2899..d9594d766 100644 --- a/gcloud/alpha/builds/triggers/create/gitlab-enterprise +++ b/gcloud/alpha/builds/triggers/create/gitlab-enterprise @@ -13,7 +13,7 @@ SYNOPSIS (--gitlab-config-resource=GITLAB_CONFIG_RESOURCE --project-namespace=PROJECT_NAMESPACE) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME - --region=REGION --require-approval + --region=REGION --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -73,8 +73,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/alpha/builds/triggers/create/manual b/gcloud/alpha/builds/triggers/create/manual index 51fb63e2e..1f81b933d 100644 --- a/gcloud/alpha/builds/triggers/create/manual +++ b/gcloud/alpha/builds/triggers/create/manual @@ -8,10 +8,9 @@ SYNOPSIS | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -58,8 +57,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -145,10 +145,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/alpha/builds/triggers/create/pubsub b/gcloud/alpha/builds/triggers/create/pubsub index 4ac43e3bf..bedc94270 100644 --- a/gcloud/alpha/builds/triggers/create/pubsub +++ b/gcloud/alpha/builds/triggers/create/pubsub @@ -9,11 +9,10 @@ SYNOPSIS : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --subscription-filter=SUBSCRIPTION_FILTER --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -71,8 +70,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -163,10 +163,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/alpha/builds/triggers/create/webhook b/gcloud/alpha/builds/triggers/create/webhook index 14bcd68d1..216c293aa 100644 --- a/gcloud/alpha/builds/triggers/create/webhook +++ b/gcloud/alpha/builds/triggers/create/webhook @@ -9,11 +9,10 @@ SYNOPSIS : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --subscription-filter=SUBSCRIPTION_FILTER --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -77,8 +76,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -169,10 +169,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/alpha/compute/disks/stop-async-replication b/gcloud/alpha/compute/disks/stop-async-replication index 4fc6d01f9..80ef01922 100644 --- a/gcloud/alpha/compute/disks/stop-async-replication +++ b/gcloud/alpha/compute/disks/stop-async-replication @@ -4,9 +4,7 @@ NAME SYNOPSIS gcloud alpha compute disks stop-async-replication DISK_NAME - [--secondary-disk=SECONDARY_DISK] [--region=REGION | --zone=ZONE] - [--secondary-disk-region=SECONDARY_DISK_REGION - | --secondary-disk-zone=SECONDARY_DISK_ZONE] [GCLOUD_WIDE_FLAG ...] + [--region=REGION | --zone=ZONE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) gcloud alpha compute disks stop-async-replication stops async @@ -29,11 +27,6 @@ POSITIONAL ARGUMENTS Name of the disk to stop async replication. FLAGS - --secondary-disk=SECONDARY_DISK - (DEPRECATED) Secondary disk for asynchronous replication. - - Flag --secondary-disk is deprecated. - At most one of these can be specified: --region=REGION @@ -77,19 +70,6 @@ FLAGS Alternatively, the zone can be stored in the environment variable CLOUDSDK_COMPUTE_ZONE. - At most one of these can be specified: - - --secondary-disk-region=SECONDARY_DISK_REGION - (DEPRECATED) Region of the secondary disk for asynchronous - replication. - - Flag --secondary-disk-zone is deprecated. - - --secondary-disk-zone=SECONDARY_DISK_ZONE - (DEPRECATED) Zone of the secondary disk for asynchronous replication. - - Flag --secondary-disk-zone is deprecated. - 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/images/import b/gcloud/alpha/compute/images/import index b761b4010..938f4b8ef 100644 --- a/gcloud/alpha/compute/images/import +++ b/gcloud/alpha/compute/images/import @@ -3,13 +3,13 @@ NAME SYNOPSIS gcloud alpha compute images import IMAGE_NAME - (--aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION + (--source-file=SOURCE_FILE | --source-image=SOURCE_IMAGE + | --aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION --aws-secret-access-key=AWS_SECRET_ACCESS_KEY --aws-session-token=AWS_SESSION_TOKEN (--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH | --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION - --aws-ami-id=AWS_AMI_ID) | --source-file=SOURCE_FILE - | --source-image=SOURCE_IMAGE) [--no-address] [--async] + --aws-ami-id=AWS_AMI_ID)) [--no-address] [--async] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -59,6 +59,20 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + Image import from local file, Cloud Storage or Compute Engine image. + + At most one of these can be specified: + + --source-file=SOURCE_FILE + A local file, or the Cloud Storage URI of the virtual disk file to + import. For example: gs://my-bucket/my-image.vmdk or + ./my-local-image.vmdk. For more information about Cloud Storage + URIs, see + https://cloud.google.com/storage/docs/request-endpoints#json-api. + + --source-image=SOURCE_IMAGE + An existing Compute Engine image from which to import. + Image import from AWS. --aws-access-key-id=AWS_ACCESS_KEY_ID @@ -113,20 +127,6 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - Image import from local file, Cloud Storage or Compute Engine image. - - At most one of these can be specified: - - --source-file=SOURCE_FILE - A local file, or the Cloud Storage URI of the virtual disk file to - import. For example: gs://my-bucket/my-image.vmdk or - ./my-local-image.vmdk. For more information about Cloud Storage - URIs, see - https://cloud.google.com/storage/docs/request-endpoints#json-api. - - --source-image=SOURCE_IMAGE - An existing Compute Engine image from which to import. - OPTIONAL FLAGS --no-address Temporary VMs are created in your project during image import. Set this diff --git a/gcloud/alpha/compute/tpus/queued-resources/create b/gcloud/alpha/compute/tpus/queued-resources/create index eab5f5285..72debc437 100644 --- a/gcloud/alpha/compute/tpus/queued-resources/create +++ b/gcloud/alpha/compute/tpus/queued-resources/create @@ -8,6 +8,8 @@ SYNOPSIS --runtime-version=RUNTIME_VERSION (--node-id=NODE_ID | --node-count=NODE_COUNT --node-prefix=NODE_PREFIX) [--async] [--best-effort] [--guaranteed] [--internal-ips] + [--metadata=[METADATA,...]] + [--metadata-from-file=[METADATA_FROM_FILE,...]] [--network=NETWORK; default="default"] [--reservation-host-folder=RESERVATION_HOST_FOLDER] [--reservation-host-organization=RESERVATION_HOST_ORGANIZATION] @@ -129,6 +131,14 @@ OPTIONAL FLAGS default is that external IP addresses will be associated with the TPU workers. + --metadata=[METADATA,...] + List of comma-separated metadata key-value pairs for the Cloud TPU VM + node. Example: --metadata='key1=value1,key2=value2' + + --metadata-from-file=[METADATA_FROM_FILE,...] + Same as --metadata except the value for the entry will be read from a + local file. Example: --metadata-from-file='key1=value1.txt' + --network=NETWORK; default="default" Network that this TPU will be a part of. diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/create b/gcloud/alpha/container/bare-metal/admin-clusters/create index 29d875748..654ab2f4f 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/create +++ b/gcloud/alpha/container/bare-metal/admin-clusters/create @@ -15,8 +15,9 @@ SYNOPSIS --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]) ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT)) - [--annotations=[KEY=VALUE,...]] [--async] [--description=DESCRIPTION] - [--enable-application-logs] [--login-user=LOGIN_USER] + [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async] + [--description=DESCRIPTION] [--enable-application-logs] + [--login-user=LOGIN_USER] [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, ...]] [--max-pods-per-node=MAX_PODS_PER_NODE] [--validate-only] [--uri=URI : --no-proxy=[NO_PROXY,...]] [GCLOUD_WIDE_FLAG ...] @@ -179,6 +180,14 @@ REQUIRED FLAGS arguments in this group are specified. OPTIONAL FLAGS + Anthos on bare metal admin cluster security configuration. + + Admin cluster authorization configurations + + --admin-users=ADMIN_USERS + Users that will be granted the view role on the admin cluster, + providing view only access to the cluster. + --annotations=[KEY=VALUE,...] Annotations on the Anthos on bare metal resource. @@ -237,5 +246,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters create diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/describe b/gcloud/alpha/container/bare-metal/admin-clusters/describe index 39f0c4a97..8eef0c929 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/describe +++ b/gcloud/alpha/container/bare-metal/admin-clusters/describe @@ -56,5 +56,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters describe diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/enroll b/gcloud/alpha/container/bare-metal/admin-clusters/enroll index 4f8e21016..bdfd45520 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/enroll +++ b/gcloud/alpha/container/bare-metal/admin-clusters/enroll @@ -12,6 +12,17 @@ SYNOPSIS DESCRIPTION (ALPHA) Enroll an Anthos on bare metal admin cluster. +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud alpha container bare-metal admin-clusters enroll \ + my-cluster --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + POSITIONAL ARGUMENTS Admin cluster resource - admin cluster to enroll The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -88,5 +99,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters enroll diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/help b/gcloud/alpha/container/bare-metal/admin-clusters/help index 29ad51cfc..9f7f63a1a 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/help +++ b/gcloud/alpha/container/bare-metal/admin-clusters/help @@ -40,5 +40,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/list b/gcloud/alpha/container/bare-metal/admin-clusters/list index 733d17227..a3c017072 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/list +++ b/gcloud/alpha/container/bare-metal/admin-clusters/list @@ -78,5 +78,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters list diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config b/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config index cd60706c2..5d2380bb1 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config +++ b/gcloud/alpha/container/bare-metal/admin-clusters/query-version-config @@ -15,13 +15,15 @@ DESCRIPTION EXAMPLES To query versions for creating an admin cluster in location us-west1, run: - $ gcloud alpha container bare-metal admin-clusters \ query-version-config --location=us-west1 + $ gcloud alpha container bare-metal admin-clusters \ + query-version-config --location=us-west1 To query versions for upgrading an admin cluster named my-admin-cluster in location us-west1, run: - $ gcloud alpha container bare-metal admin-clusters \ query-version-config --location=us-west1 \ - --admin-cluster=my-admin-cluster + $ gcloud alpha container bare-metal admin-clusters \ + query-version-config --location=us-west1 \ + --admin-cluster=my-admin-cluster FLAGS Use cases for querying versions. @@ -75,5 +77,8 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters \ + query-version-config diff --git a/gcloud/alpha/container/bare-metal/admin-clusters/update b/gcloud/alpha/container/bare-metal/admin-clusters/update index 5cc843b6f..f7e6a3ca7 100644 --- a/gcloud/alpha/container/bare-metal/admin-clusters/update +++ b/gcloud/alpha/container/bare-metal/admin-clusters/update @@ -141,5 +141,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal admin-clusters update diff --git a/gcloud/alpha/container/bare-metal/clusters/create b/gcloud/alpha/container/bare-metal/clusters/create index ef1261ea3..f13bb0f62 100644 --- a/gcloud/alpha/container/bare-metal/clusters/create +++ b/gcloud/alpha/container/bare-metal/clusters/create @@ -10,16 +10,31 @@ SYNOPSIS (--control-plane-load-balancer-port=CONTROL_PLANE_LOAD_BALANCER_PORT (--control-plane-vip=CONTROL_PLANE_VIP --ingress-vip=INGRESS_VIP) (--enable-manual-lb - | [--metal-lb-address-pools=[addresses=ADDRESSES], + | [--bgp-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] --bgp-asn=BGP_ASN + --bgp-peer-configs=[asn=ASN, + ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + : [--bgp-load-balancer-node-configs=[node-ip=IP, + labels=KEY1=VALUE1;KEY2=VALUE2,...] + : --bgp-load-balancer-node-labels=[KEY=VALUE,...] + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS --disable-bgp-load-balancer-serialize-image-pulls]] | [--metal-lb-address-pools=[addresses=ADDRESSES], [avoid-buggy-ips=AVOID-BUGGY-IPS], [manual-assign=MANUAL-ASSIGN],[pool=POOL] : --metal-lb-load-balancer-node-configs=[labels=LABELS], [node-ip=NODE-IP] --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] - --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...]])) + --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --disable-metal-lb-load-balancer-serialize-image-pulls + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS])) ((((--control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] : --control-plane-node-labels=[KEY=VALUE,...] - --control-plane-node-taints=[KEY=VALUE:EFFECT,...]))) + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + --disable-control-plane-serialize-image-pulls))) : --api-server-args=[KEY=VALUE,...]) ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT)) @@ -145,14 +160,107 @@ REQUIRED FLAGS --enable-manual-lb ManualLB typed load balancers configuration. - MetalLB Configuration + BGP load balancer configuration. + + --bgp-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + BGP load balancer address pools configurations. + + Examples: + + To specify configurations for two address pools pool1 and pool2, + + $ gcloud alpha container bare-metal clusters create example_cluster + --bgp-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --bgp-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-asn=BGP_ASN + BGP autonomous system number (ASN) of the cluster. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-peer-configs=[asn=ASN,ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + List of BGP peers that the cluster will connect to. At least one + peer must be configured for each control plane node. + + Examples: + + To specify configurations for two peers of BGP autonomous system + number (ASN) 10000 and 20000, + + $ gcloud alpha container bare-metal clusters create example_cluster + --bgp-peer-configs 'asn=10000,ip=192.168.1.1,control-plane-nodes=192.168.1.2;192.168.1.3' + --bgp-peer-configs 'asn=20000,ip=192.168.2.1,control-plane-nodes=192.168.2.2;192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-load-balancer-node-configs=[node-ip=IP,labels=KEY1=VALUE1;KEY2=VALUE2,...] + BGP load balancer data plane node configurations. + + Examples: + + To specify configurations for two nodes of IP 192.168.0.1 and + 192.168.1.1, + + $ gcloud alpha container bare-metal clusters create example_cluster + --bgp-load-balancer-node-configs 'node-ip=192.168.0.1,labels=KEY1=VALUE1;KEY2=VALUE2' + --bgp-load-balancer-node-configs 'node-ip=192.168.1.1,labels=KEY3=VALUE3' + + Use quote around the flag value to escape semicolon in the + terminal. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-load-balancer-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a BGP node pool. + + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to burst + to this number, while still not exceeding registry_pull_qps. + + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + --disable-bgp-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + + MetalLB load balancer configuration. MetalLB address pools configuration. Exactly one of these must be specified: --metal-lb-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] - MetalLB address pools configuration. + MetalLB load balancer configurations. + + Examples: + + To specify MetalLB load balancer configurations for two address + pools pool1 and pool2, + + $ gcloud alpha container bare-metal clusters create example_cluster + --metal-lb-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --metal-lb-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. Anthos on bare metal node pool configuration for MetalLB load balancer nodes. @@ -172,6 +280,20 @@ REQUIRED FLAGS --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] Node taint applied to every node in a MetalLB node pool. + Modifiable kubelet configurations for bare metal machines. + + --disable-metal-lb-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at + a time. + + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + Anthos on bare metal cluster control plane configuration. At least one of these must be specified: @@ -204,6 +326,20 @@ REQUIRED FLAGS --control-plane-node-taints=[KEY=VALUE:EFFECT,...] Node taint applied to every Kubernetes node in a node pool. + Modifiable kubelet configurations for bare metal machines. + + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + --disable-control-plane-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + Anthos on bare metal cluster storage configuration. This must be specified. @@ -352,5 +488,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters create diff --git a/gcloud/alpha/container/bare-metal/clusters/delete b/gcloud/alpha/container/bare-metal/clusters/delete index 5fc59c01a..bd9a66cb6 100644 --- a/gcloud/alpha/container/bare-metal/clusters/delete +++ b/gcloud/alpha/container/bare-metal/clusters/delete @@ -76,5 +76,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters delete diff --git a/gcloud/alpha/container/bare-metal/clusters/describe b/gcloud/alpha/container/bare-metal/clusters/describe index fe20a438b..1b863bf86 100644 --- a/gcloud/alpha/container/bare-metal/clusters/describe +++ b/gcloud/alpha/container/bare-metal/clusters/describe @@ -54,5 +54,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters describe diff --git a/gcloud/alpha/container/bare-metal/clusters/enroll b/gcloud/alpha/container/bare-metal/clusters/enroll index 415105ca8..cdb800a0c 100644 --- a/gcloud/alpha/container/bare-metal/clusters/enroll +++ b/gcloud/alpha/container/bare-metal/clusters/enroll @@ -101,5 +101,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters enroll diff --git a/gcloud/alpha/container/bare-metal/clusters/help b/gcloud/alpha/container/bare-metal/clusters/help index d89dd0c90..4335753bc 100644 --- a/gcloud/alpha/container/bare-metal/clusters/help +++ b/gcloud/alpha/container/bare-metal/clusters/help @@ -42,5 +42,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters diff --git a/gcloud/alpha/container/bare-metal/clusters/list b/gcloud/alpha/container/bare-metal/clusters/list index 8e01cace3..9b0d82b75 100644 --- a/gcloud/alpha/container/bare-metal/clusters/list +++ b/gcloud/alpha/container/bare-metal/clusters/list @@ -76,5 +76,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters list diff --git a/gcloud/alpha/container/bare-metal/clusters/query-version-config b/gcloud/alpha/container/bare-metal/clusters/query-version-config index e027c0ffc..ce2c81231 100644 --- a/gcloud/alpha/container/bare-metal/clusters/query-version-config +++ b/gcloud/alpha/container/bare-metal/clusters/query-version-config @@ -124,5 +124,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters query-version-config diff --git a/gcloud/alpha/container/bare-metal/clusters/update b/gcloud/alpha/container/bare-metal/clusters/update index 821f20c9d..a655ca634 100644 --- a/gcloud/alpha/container/bare-metal/clusters/update +++ b/gcloud/alpha/container/bare-metal/clusters/update @@ -12,16 +12,31 @@ SYNOPSIS [--api-server-args=[KEY=VALUE,...] --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] --control-plane-node-labels=[KEY=VALUE,...] - --control-plane-node-taints=[KEY=VALUE:EFFECT,...]] - [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] - --disable-sr-iov-config | --enable-sr-iov-config] - [--metal-lb-address-pools=[addresses=ADDRESSES], + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + --disable-control-plane-serialize-image-pulls + | --enable-control-plane-serialize-image-pulls] + [--bgp-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] --bgp-asn=BGP_ASN + --bgp-peer-configs=[asn=ASN, + ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + --bgp-load-balancer-node-configs=[node-ip=IP, + labels=KEY1=VALUE1;KEY2=VALUE2,...] + --bgp-load-balancer-node-labels=[KEY=VALUE,...] + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS --disable-bgp-load-balancer-serialize-image-pulls | --enable-bgp-load-balancer-serialize-image-pulls | --metal-lb-address-pools=[addresses=ADDRESSES], [avoid-buggy-ips=AVOID-BUGGY-IPS], [manual-assign=MANUAL-ASSIGN],[pool=POOL] --metal-lb-load-balancer-node-configs=[labels=LABELS], [node-ip=NODE-IP] --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] - --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...]] + --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS --disable-metal-lb-load-balancer-serialize-image-pulls | --enable-metal-lb-load-balancer-serialize-image-pulls] + [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + --disable-sr-iov-config | --enable-sr-iov-config] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -129,37 +144,126 @@ FLAGS --control-plane-node-taints=[KEY=VALUE:EFFECT,...] Node taint applied to every Kubernetes node in a node pool. - Anthos on bare metal cluster network configurations. + Modifiable kubelet configurations for bare metal machines. - Populate one of the network configs. + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. - Island mode CIDR network configuration. + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + Limit of registry pulls per second. - --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] - IPv4 address range for all services in the cluster. + At most one of these can be specified: - SR-IOV networking operator configurations. + --disable-control-plane-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at + a time. - At most one of these can be specified: - - --disable-sr-iov-config - If set, the SR-IOV operator won't be installed. - - --enable-sr-iov-config - If set, install the SR-IOV operator. + --enable-control-plane-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a + time. Anthos on bare metal cluster load balancer configuration. Populate one of the load balancers. - MetalLB Configuration + At most one of these can be specified: + + BGP load balancer configuration. + + --bgp-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + BGP load balancer address pools configurations. + + Examples: + + To specify configurations for two address pools pool1 and pool2, + + $ gcloud alpha container bare-metal clusters update example_cluster + --bgp-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --bgp-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + --bgp-asn=BGP_ASN + BGP autonomous system number (ASN) of the cluster. + + --bgp-peer-configs=[asn=ASN,ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + List of BGP peers that the cluster will connect to. At least one + peer must be configured for each control plane node. + + Examples: + + To specify configurations for two peers of BGP autonomous system + number (ASN) 10000 and 20000, + + $ gcloud alpha container bare-metal clusters update example_cluster + --bgp-peer-configs 'asn=10000,ip=192.168.1.1,control-plane-nodes=192.168.1.2;192.168.1.3' + --bgp-peer-configs 'asn=20000,ip=192.168.2.1,control-plane-nodes=192.168.2.2;192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + --bgp-load-balancer-node-configs=[node-ip=IP,labels=KEY1=VALUE1;KEY2=VALUE2,...] + BGP load balancer data plane node configurations. + + Examples: + + To specify configurations for two nodes of IP 192.168.0.1 and + 192.168.1.1, + + $ gcloud alpha container bare-metal clusters update example_cluster + --bgp-load-balancer-node-configs 'node-ip=192.168.0.1,labels=KEY1=VALUE1;KEY2=VALUE2' + --bgp-load-balancer-node-configs 'node-ip=192.168.1.1,labels=KEY3=VALUE3' + + Use quote around the flag value to escape semicolon in the + terminal. + + --bgp-load-balancer-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a BGP node pool. + + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to burst + to this number, while still not exceeding registry_pull_qps. + + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + At most one of these can be specified: + + --disable-bgp-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + + --enable-bgp-load-balancer-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a time. + + MetalLB load balancer configuration. MetalLB address pools configuration. At most one of these can be specified: --metal-lb-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] - MetalLB address pools configuration. + MetalLB load balancer configurations. + + Examples: + + To specify MetalLB load balancer configurations for two address + pools pool1 and pool2, + + $ gcloud alpha container bare-metal clusters update example_cluster + --metal-lb-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --metal-lb-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. Anthos on bare metal node pool configuration for MetalLB load balancer nodes. @@ -179,6 +283,45 @@ FLAGS --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] Node taint applied to every node in a MetalLB node pool. + Modifiable kubelet configurations for bare metal machines. + + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + At most one of these can be specified: + + --disable-metal-lb-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images + at a time. + + --enable-metal-lb-load-balancer-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a + time. + + Anthos on bare metal cluster network configurations. + + Populate one of the network configs. + + Island mode CIDR network configuration. + + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + IPv4 address range for all services in the cluster. + + SR-IOV networking operator configurations. + + At most one of these can be specified: + + --disable-sr-iov-config + If set, the SR-IOV operator won't be installed. + + --enable-sr-iov-config + If set, install the SR-IOV operator. + GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, --billing-project, --configuration, --flags-file, --flatten, --format, @@ -191,5 +334,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal clusters update diff --git a/gcloud/alpha/container/bare-metal/help b/gcloud/alpha/container/bare-metal/help index 21538d543..07fae3310 100644 --- a/gcloud/alpha/container/bare-metal/help +++ b/gcloud/alpha/container/bare-metal/help @@ -34,5 +34,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal diff --git a/gcloud/alpha/container/bare-metal/node-pools/create b/gcloud/alpha/container/bare-metal/node-pools/create index f65cafa55..3b4b5a020 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/create +++ b/gcloud/alpha/container/bare-metal/node-pools/create @@ -7,10 +7,7 @@ SYNOPSIS (NODE_POOL : --cluster=CLUSTER --location=LOCATION) (--node-configs=[labels=LABELS],[node-ip=NODE-IP] : --node-labels=[KEY=VALUE,...] --node-taints=[KEY=VALUE:EFFECT,...] - --cpu-cfs-quota-period=CPU_CFS_QUOTA_PERIOD - --cpu-manager-policy=CPU_MANAGER_POLICY --disable-cpu-cfs-quota - --disable-serialize-image-pulls --feature-gates=[FEATURE=BOOL,...] - --pod-pids-limit=POD_PIDS_LIMIT --registry-burst=REGISTRY_BURST + --disable-serialize-image-pulls --registry-burst=REGISTRY_BURST --registry-pull-qps=REGISTRY_PULL_QPS) [--annotations=[KEY=VALUE,...]] [--async] [--display-name=DISPLAY_NAME] [--validate-only] [GCLOUD_WIDE_FLAG ...] @@ -77,32 +74,13 @@ REQUIRED FLAGS --node-taints=[KEY=VALUE:EFFECT,...] Node taint applied to every Kubernetes node in a node pool. - Sets the modifiable kubelet configurations for bare metal machines. - - --cpu-cfs-quota-period=CPU_CFS_QUOTA_PERIOD - CPU Completely Fair Scheduler (CFS) quota period value. Specify - with seconds as the time unit, such as 0.2s. - - --cpu-manager-policy=CPU_MANAGER_POLICY - The kubelet CPU manager policy. CPU_MANAGER_POLICY must be one of: - NONE, STATIC. - - --disable-cpu-cfs-quota - If set, disable CPU Completely Fair Scheduler (CFS) quota - enforcement for containers that specify CPU limits. + Modifiable kubelet configurations for bare metal machines. --disable-serialize-image-pulls If set, prevent the Kubelet from pulling multiple images at a time. - --feature-gates=[FEATURE=BOOL,...] - A map of feature names to bools that enable or disable experimental - features. - - --pod-pids-limit=POD_PIDS_LIMIT - Maximum number of PIDs in any pod. - --registry-burst=REGISTRY_BURST - Maximum size of bursty pulls, temporarily allows pulls to burst to + Maximum size of bursty pulls, temporarily allow pulls to burst to this number, while still not exceeding registry_pull_qps. --registry-pull-qps=REGISTRY_PULL_QPS @@ -135,5 +113,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools create diff --git a/gcloud/alpha/container/bare-metal/node-pools/delete b/gcloud/alpha/container/bare-metal/node-pools/delete index 14be263ff..508f053eb 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/delete +++ b/gcloud/alpha/container/bare-metal/node-pools/delete @@ -80,5 +80,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools delete diff --git a/gcloud/alpha/container/bare-metal/node-pools/describe b/gcloud/alpha/container/bare-metal/node-pools/describe index 16a98de14..5ae3ad5f0 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/describe +++ b/gcloud/alpha/container/bare-metal/node-pools/describe @@ -63,5 +63,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools describe diff --git a/gcloud/alpha/container/bare-metal/node-pools/enroll b/gcloud/alpha/container/bare-metal/node-pools/enroll index ded4472df..9af2e9cf1 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/enroll +++ b/gcloud/alpha/container/bare-metal/node-pools/enroll @@ -72,5 +72,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools enroll diff --git a/gcloud/alpha/container/bare-metal/node-pools/help b/gcloud/alpha/container/bare-metal/node-pools/help index 65004aab5..b363eff69 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/help +++ b/gcloud/alpha/container/bare-metal/node-pools/help @@ -38,5 +38,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools diff --git a/gcloud/alpha/container/bare-metal/node-pools/list b/gcloud/alpha/container/bare-metal/node-pools/list index 61cac9a21..d83167f81 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/list +++ b/gcloud/alpha/container/bare-metal/node-pools/list @@ -89,5 +89,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools list diff --git a/gcloud/alpha/container/bare-metal/node-pools/update b/gcloud/alpha/container/bare-metal/node-pools/update index 94c28d72b..b2f82b3fc 100644 --- a/gcloud/alpha/container/bare-metal/node-pools/update +++ b/gcloud/alpha/container/bare-metal/node-pools/update @@ -8,12 +8,8 @@ SYNOPSIS [--async] [--display-name=DISPLAY_NAME] [--validate-only] [--node-configs=[labels=LABELS],[node-ip=NODE-IP] --node-labels=[KEY=VALUE,...] --node-taints=[KEY=VALUE:EFFECT,...] - --cpu-cfs-quota-period=CPU_CFS_QUOTA_PERIOD - --cpu-manager-policy=CPU_MANAGER_POLICY - --feature-gates=[FEATURE=BOOL,...] --pod-pids-limit=POD_PIDS_LIMIT --registry-burst=REGISTRY_BURST - --registry-pull-qps=REGISTRY_PULL_QPS --disable-cpu-cfs-quota - | --enable-cpu-cfs-quota --disable-serialize-image-pulls + --registry-pull-qps=REGISTRY_PULL_QPS --disable-serialize-image-pulls | --enable-serialize-image-pulls] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -92,40 +88,15 @@ FLAGS --node-taints=[KEY=VALUE:EFFECT,...] Node taint applied to every Kubernetes node in a node pool. - Sets the modifiable kubelet configurations for bare metal machines. - - --cpu-cfs-quota-period=CPU_CFS_QUOTA_PERIOD - CPU Completely Fair Scheduler (CFS) quota period value. Specify - with seconds as the time unit, such as 0.2s. - - --cpu-manager-policy=CPU_MANAGER_POLICY - The kubelet CPU manager policy. CPU_MANAGER_POLICY must be one of: - NONE, STATIC. - - --feature-gates=[FEATURE=BOOL,...] - A map of feature names to bools that enable or disable experimental - features. - - --pod-pids-limit=POD_PIDS_LIMIT - Maximum number of PIDs in any pod. + Modifiable kubelet configurations for bare metal machines. --registry-burst=REGISTRY_BURST - Maximum size of bursty pulls, temporarily allows pulls to burst to + Maximum size of bursty pulls, temporarily allow pulls to burst to this number, while still not exceeding registry_pull_qps. --registry-pull-qps=REGISTRY_PULL_QPS Limit of registry pulls per second. - At most one of these can be specified: - - --disable-cpu-cfs-quota - If set, disable CPU Completely Fair Scheduler (CFS) quota - enforcement for containers that specify CPU limits. - - --enable-cpu-cfs-quota - If set, enable CPU Completely Fair Scheduler (CFS) quota - enforcement for containers that specify CPU limits. - At most one of these can be specified: --disable-serialize-image-pulls @@ -147,5 +118,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal node-pools update diff --git a/gcloud/alpha/container/bare-metal/operations/describe b/gcloud/alpha/container/bare-metal/operations/describe index 36bcf86db..40b597712 100644 --- a/gcloud/alpha/container/bare-metal/operations/describe +++ b/gcloud/alpha/container/bare-metal/operations/describe @@ -55,5 +55,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal operations describe diff --git a/gcloud/alpha/container/bare-metal/operations/help b/gcloud/alpha/container/bare-metal/operations/help index 2a789d29b..4314214e9 100644 --- a/gcloud/alpha/container/bare-metal/operations/help +++ b/gcloud/alpha/container/bare-metal/operations/help @@ -29,5 +29,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal operations diff --git a/gcloud/alpha/container/bare-metal/operations/list b/gcloud/alpha/container/bare-metal/operations/list index 89e31cef9..73fa3d242 100644 --- a/gcloud/alpha/container/bare-metal/operations/list +++ b/gcloud/alpha/container/bare-metal/operations/list @@ -77,5 +77,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal operations list diff --git a/gcloud/alpha/container/bare-metal/operations/wait b/gcloud/alpha/container/bare-metal/operations/wait index 8bd8b82dc..84dd51e65 100644 --- a/gcloud/alpha/container/bare-metal/operations/wait +++ b/gcloud/alpha/container/bare-metal/operations/wait @@ -55,5 +55,7 @@ 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. This variant is also available: + + $ gcloud beta container bare-metal operations wait diff --git a/gcloud/alpha/container/clusters/create b/gcloud/alpha/container/clusters/create index 13129bbe1..d33526dcc 100644 --- a/gcloud/alpha/container/clusters/create +++ b/gcloud/alpha/container/clusters/create @@ -1040,12 +1040,16 @@ FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal to - 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 and + less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/alpha/container/node-pools/create b/gcloud/alpha/container/node-pools/create index 191c2db29..d66563300 100644 --- a/gcloud/alpha/container/node-pools/create +++ b/gcloud/alpha/container/node-pools/create @@ -522,12 +522,16 @@ FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal to - 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 and + less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/alpha/container/node-pools/update b/gcloud/alpha/container/node-pools/update index 220edc63b..9c09d52cf 100644 --- a/gcloud/alpha/container/node-pools/update +++ b/gcloud/alpha/container/node-pools/update @@ -159,12 +159,16 @@ REQUIRED FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal - to 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 + and less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/alpha/container/vmware/admin-clusters/describe b/gcloud/alpha/container/vmware/admin-clusters/describe index 9360671f2..6f0bde142 100644 --- a/gcloud/alpha/container/vmware/admin-clusters/describe +++ b/gcloud/alpha/container/vmware/admin-clusters/describe @@ -56,5 +56,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware admin-clusters describe diff --git a/gcloud/alpha/container/vmware/admin-clusters/enroll b/gcloud/alpha/container/vmware/admin-clusters/enroll index aa9009596..cdb1cae37 100644 --- a/gcloud/alpha/container/vmware/admin-clusters/enroll +++ b/gcloud/alpha/container/vmware/admin-clusters/enroll @@ -12,6 +12,17 @@ SYNOPSIS DESCRIPTION (ALPHA) Enroll an Anthos on VMware admin cluster. +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud alpha container vmware admin-clusters enroll my-cluster \ + --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + POSITIONAL ARGUMENTS Admin cluster resource - admin cluster to enroll The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some @@ -88,5 +99,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware admin-clusters enroll diff --git a/gcloud/alpha/container/vmware/admin-clusters/help b/gcloud/alpha/container/vmware/admin-clusters/help index 155695121..cc0a498ad 100644 --- a/gcloud/alpha/container/vmware/admin-clusters/help +++ b/gcloud/alpha/container/vmware/admin-clusters/help @@ -32,5 +32,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware admin-clusters diff --git a/gcloud/alpha/container/vmware/admin-clusters/list b/gcloud/alpha/container/vmware/admin-clusters/list index 2f95618b0..dd9852ffa 100644 --- a/gcloud/alpha/container/vmware/admin-clusters/list +++ b/gcloud/alpha/container/vmware/admin-clusters/list @@ -78,5 +78,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware admin-clusters list diff --git a/gcloud/alpha/container/vmware/admin-clusters/update b/gcloud/alpha/container/vmware/admin-clusters/update index e7f535510..bedcc6b96 100644 --- a/gcloud/alpha/container/vmware/admin-clusters/update +++ b/gcloud/alpha/container/vmware/admin-clusters/update @@ -68,5 +68,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware admin-clusters update diff --git a/gcloud/alpha/container/vmware/clusters/create b/gcloud/alpha/container/vmware/clusters/create index f4250efbc..a0ae69db8 100644 --- a/gcloud/alpha/container/vmware/clusters/create +++ b/gcloud/alpha/container/vmware/clusters/create @@ -20,14 +20,17 @@ SYNOPSIS : --f5-config-snat-pool=F5_CONFIG_SNAT_POOL])) (--pod-address-cidr-blocks=POD_ADDRESS --service-address-cidr-blocks=SERVICE_ADDRESS - : --dns-search-domains=[DNS_SEARCH_DOMAINS,...] + : --control-plane-ip-block=[gateway=GATEWAY], + [ips=IPS],[netmask=NETMASK] + --dns-search-domains=[DNS_SEARCH_DOMAINS,...] --dns-servers=[DNS_SERVERS,...] --ntp-servers=[NTP_SERVERS,...] --enable-dhcp | --static-ip-config-ip-blocks=[gateway=GATEWAY], [ips=IPS],[netmask=NETMASK]) [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async] [--description=DESCRIPTION] [--disable-aag-config] [--disable-vsphere-csi] [--enable-auto-repair] - [--enable-vm-tracking] [--validate-only] [--version=VERSION] + [--enable-control-plane-v2] [--enable-vm-tracking] [--validate-only] + [--version=VERSION] [--cpus=CPUS --enable-auto-resize --memory=MEMORY --replicas=REPLICAS] [--enable-advanced-networking --enable-dataplane-v2] [GCLOUD_WIDE_FLAG ...] @@ -193,6 +196,18 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. + Control plane v2 mode configurations. + + --control-plane-ip-block=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK] + Static IP addresses for the control plane nodes. The number of IP + addresses should match the number of replicas for the control plane + nodes, specified by --replicas. + + To specify the control plane IP block, + + $ gcloud gcloud alpha container vmware clusters create + --control-plane-ip-block 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;' + Common parameters for all hosts irrespective of their IP address --dns-search-domains=[DNS_SEARCH_DOMAINS,...] @@ -269,6 +284,9 @@ OPTIONAL FLAGS --enable-auto-repair If set, deploy the cluster-health-controller. + --enable-control-plane-v2 + If set, enable control plane v2. + --enable-vm-tracking If set, enable VM tracking. @@ -319,5 +337,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters create diff --git a/gcloud/alpha/container/vmware/clusters/delete b/gcloud/alpha/container/vmware/clusters/delete index 75bd8858f..342b84522 100644 --- a/gcloud/alpha/container/vmware/clusters/delete +++ b/gcloud/alpha/container/vmware/clusters/delete @@ -76,5 +76,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters delete diff --git a/gcloud/alpha/container/vmware/clusters/describe b/gcloud/alpha/container/vmware/clusters/describe index baca67f17..1a2ef4780 100644 --- a/gcloud/alpha/container/vmware/clusters/describe +++ b/gcloud/alpha/container/vmware/clusters/describe @@ -54,5 +54,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters describe diff --git a/gcloud/alpha/container/vmware/clusters/enroll b/gcloud/alpha/container/vmware/clusters/enroll index f93265a1c..fd648ea03 100644 --- a/gcloud/alpha/container/vmware/clusters/enroll +++ b/gcloud/alpha/container/vmware/clusters/enroll @@ -7,11 +7,23 @@ SYNOPSIS (CLUSTER : --location=LOCATION) (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT) - [--async] [GCLOUD_WIDE_FLAG ...] + [--async] [--local-name=LOCAL_NAME] [--validate-only] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Enroll an Anthos cluster on VMware. +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud alpha container vmware clusters enroll my-cluster \ + --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + POSITIONAL ARGUMENTS Cluster resource - cluster to enroll The arguments in this group can be used to specify the attributes of this resource. (NOTE) Some attributes @@ -78,6 +90,19 @@ OPTIONAL FLAGS Return immediately, without waiting for the operation in progress to complete. + --local-name=LOCAL_NAME + The object name of the VMware OnPremUserCluster custom resource on the + associated admin cluster. This field is used to support conflicting + resource names when enrolling existing clusters to the API. When not + provided, this field will resolve to the vmware_cluster_id. Otherwise, + it must match the object name of the VMware OnPremUserCluster custom + resource. It is not modifiable outside / beyond the enrollment + operation. + + --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, @@ -90,5 +115,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters enroll diff --git a/gcloud/alpha/container/vmware/clusters/help b/gcloud/alpha/container/vmware/clusters/help index efb706cab..027919a9b 100644 --- a/gcloud/alpha/container/vmware/clusters/help +++ b/gcloud/alpha/container/vmware/clusters/help @@ -45,5 +45,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters diff --git a/gcloud/alpha/container/vmware/clusters/list b/gcloud/alpha/container/vmware/clusters/list index ad93a587f..13cd88e1f 100644 --- a/gcloud/alpha/container/vmware/clusters/list +++ b/gcloud/alpha/container/vmware/clusters/list @@ -77,5 +77,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters list diff --git a/gcloud/alpha/container/vmware/clusters/query-version-config b/gcloud/alpha/container/vmware/clusters/query-version-config index 16a19afc8..75b8ff890 100644 --- a/gcloud/alpha/container/vmware/clusters/query-version-config +++ b/gcloud/alpha/container/vmware/clusters/query-version-config @@ -124,5 +124,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters query-version-config diff --git a/gcloud/alpha/container/vmware/clusters/update b/gcloud/alpha/container/vmware/clusters/update index 9942195ef..7a5364852 100644 --- a/gcloud/alpha/container/vmware/clusters/update +++ b/gcloud/alpha/container/vmware/clusters/update @@ -198,5 +198,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters update diff --git a/gcloud/alpha/container/vmware/clusters/upgrade b/gcloud/alpha/container/vmware/clusters/upgrade index 8248ca196..c522816df 100644 --- a/gcloud/alpha/container/vmware/clusters/upgrade +++ b/gcloud/alpha/container/vmware/clusters/upgrade @@ -60,5 +60,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware clusters upgrade diff --git a/gcloud/alpha/container/vmware/help b/gcloud/alpha/container/vmware/help index db1958dba..95fe88eac 100644 --- a/gcloud/alpha/container/vmware/help +++ b/gcloud/alpha/container/vmware/help @@ -32,5 +32,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware diff --git a/gcloud/alpha/container/vmware/node-pools/create b/gcloud/alpha/container/vmware/node-pools/create index 552c43a57..6faabb8bc 100644 --- a/gcloud/alpha/container/vmware/node-pools/create +++ b/gcloud/alpha/container/vmware/node-pools/create @@ -141,5 +141,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools create diff --git a/gcloud/alpha/container/vmware/node-pools/delete b/gcloud/alpha/container/vmware/node-pools/delete index f515ac4e0..02cf47467 100644 --- a/gcloud/alpha/container/vmware/node-pools/delete +++ b/gcloud/alpha/container/vmware/node-pools/delete @@ -80,5 +80,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools delete diff --git a/gcloud/alpha/container/vmware/node-pools/describe b/gcloud/alpha/container/vmware/node-pools/describe index e68fb6f37..3deda03d7 100644 --- a/gcloud/alpha/container/vmware/node-pools/describe +++ b/gcloud/alpha/container/vmware/node-pools/describe @@ -63,5 +63,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools describe diff --git a/gcloud/alpha/container/vmware/node-pools/enroll b/gcloud/alpha/container/vmware/node-pools/enroll index 8e13c7a4f..80cd2cdbf 100644 --- a/gcloud/alpha/container/vmware/node-pools/enroll +++ b/gcloud/alpha/container/vmware/node-pools/enroll @@ -68,5 +68,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools enroll diff --git a/gcloud/alpha/container/vmware/node-pools/help b/gcloud/alpha/container/vmware/node-pools/help index 0b6522467..ff66bdd32 100644 --- a/gcloud/alpha/container/vmware/node-pools/help +++ b/gcloud/alpha/container/vmware/node-pools/help @@ -38,5 +38,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools diff --git a/gcloud/alpha/container/vmware/node-pools/list b/gcloud/alpha/container/vmware/node-pools/list index 6f44edff6..51ba27ec6 100644 --- a/gcloud/alpha/container/vmware/node-pools/list +++ b/gcloud/alpha/container/vmware/node-pools/list @@ -89,5 +89,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools list diff --git a/gcloud/alpha/container/vmware/node-pools/update b/gcloud/alpha/container/vmware/node-pools/update index e3bcbf00a..c6674cec2 100644 --- a/gcloud/alpha/container/vmware/node-pools/update +++ b/gcloud/alpha/container/vmware/node-pools/update @@ -131,5 +131,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware node-pools update diff --git a/gcloud/alpha/container/vmware/operations/describe b/gcloud/alpha/container/vmware/operations/describe index cbd30c6f9..2ac85212f 100644 --- a/gcloud/alpha/container/vmware/operations/describe +++ b/gcloud/alpha/container/vmware/operations/describe @@ -54,5 +54,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware operations describe diff --git a/gcloud/alpha/container/vmware/operations/help b/gcloud/alpha/container/vmware/operations/help index ab2a56aa1..5f42f9c0b 100644 --- a/gcloud/alpha/container/vmware/operations/help +++ b/gcloud/alpha/container/vmware/operations/help @@ -29,5 +29,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware operations diff --git a/gcloud/alpha/container/vmware/operations/list b/gcloud/alpha/container/vmware/operations/list index 83808fb17..27482c8da 100644 --- a/gcloud/alpha/container/vmware/operations/list +++ b/gcloud/alpha/container/vmware/operations/list @@ -76,5 +76,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware operations list diff --git a/gcloud/alpha/container/vmware/operations/wait b/gcloud/alpha/container/vmware/operations/wait index b99a3dec4..5b84d2cb9 100644 --- a/gcloud/alpha/container/vmware/operations/wait +++ b/gcloud/alpha/container/vmware/operations/wait @@ -55,5 +55,7 @@ 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. This variant is also available: + + $ gcloud beta container vmware operations wait diff --git a/gcloud/alpha/datastore/indexes/create b/gcloud/alpha/datastore/indexes/create index 231f8a923..16f841eb0 100644 --- a/gcloud/alpha/datastore/indexes/create +++ b/gcloud/alpha/datastore/indexes/create @@ -3,7 +3,8 @@ NAME on your local index configuration SYNOPSIS - gcloud alpha datastore indexes create INDEX_FILE [GCLOUD_WIDE_FLAG ...] + gcloud alpha datastore indexes create INDEX_FILE [--database=DATABASE] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Create new datastore indexes based on your local index @@ -25,6 +26,10 @@ POSITIONAL ARGUMENTS your index.yaml file, refer to this configuration guide: https://cloud.google.com/datastore/docs/tools/indexconfig#Datastore_About_index_yaml +FLAGS + --database=DATABASE + The database to operate on. + 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/edge-cloud/container/vpn-connections/create b/gcloud/alpha/edge-cloud/container/vpn-connections/create index 877aa9ffe..6fe7f0f4b 100644 --- a/gcloud/alpha/edge-cloud/container/vpn-connections/create +++ b/gcloud/alpha/edge-cloud/container/vpn-connections/create @@ -3,11 +3,11 @@ NAME connection between an Edge Container cluster and a VPC network SYNOPSIS - gcloud alpha edge-cloud container vpn-connections create - (VPN_CONNECTION : --location=LOCATION) --cluster=CLUSTER - --vpc-network=VPC_NETWORK [--async] [--high-availability] - [--labels=[KEY=VALUE,...]] [--nat-gateway-ip=NAT_GATEWAY_IP] - [--router=ROUTER] [--vpc-project=VPC_PROJECT] [GCLOUD_WIDE_FLAG ...] + gcloud alpha edge-cloud container vpn-connections create VPN_CONNECTION + --cluster=CLUSTER --vpc-network=VPC_NETWORK [--async] + [--high-availability] [--labels=[KEY=VALUE,...]] [--location=LOCATION] + [--nat-gateway-ip=NAT_GATEWAY_IP] [--router=ROUTER] + [--vpc-project=VPC_PROJECT] [GCLOUD_WIDE_FLAG ...] DESCRIPTION (ALPHA) Creates a new VPN connection. @@ -24,14 +24,18 @@ EXAMPLES Here VPC network and cluster should be under the same project. POSITIONAL ARGUMENTS - Vpn connection resource - VPN connection 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: + Vpn connection resource - VPN connection to create. 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 vpn_connection on the command line with a fully specified name; ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument vpn_connection on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property edge_container/location. This must be specified. @@ -40,19 +44,27 @@ POSITIONAL ARGUMENTS connection. To set the vpn_connection attribute: ▸ provide the argument vpn_connection on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The global location name. To set the location attribute: - ▸ provide the argument vpn_connection on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property edge_container/location. - REQUIRED FLAGS - --cluster=CLUSTER - The name of the cluster to be connected under current project. + Cluster resource - The name of the cluster to be connected under current + project. 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 --cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property edge_container/location. + + This must be specified. + + --cluster=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. --vpc-network=VPC_NETWORK The name of the VPC network to be connected. By default it is assumed @@ -77,6 +89,11 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --location=LOCATION + For resources [vpn connection, cluster], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + --nat-gateway-ip=NAT_GATEWAY_IP The NAT gateway IP for the gateway floating IPs. Required if cluster sits behind NAT. diff --git a/gcloud/alpha/functions/deploy b/gcloud/alpha/functions/deploy index 69056b6a5..9697da5ae 100644 --- a/gcloud/alpha/functions/deploy +++ b/gcloud/alpha/functions/deploy @@ -132,7 +132,9 @@ FLAGS If enabled, this command will use Cloud Functions (Second generation). If disabled with --no-gen2, Cloud Functions (First generation) will be used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/alpha/iam/workforce-pools/providers/create-oidc b/gcloud/alpha/iam/workforce-pools/providers/create-oidc index 9f7fea88f..f4908bed5 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/create-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/create-oidc @@ -174,9 +174,10 @@ OPTIONAL FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/alpha/iam/workforce-pools/providers/update-oidc b/gcloud/alpha/iam/workforce-pools/providers/update-oidc index a304dac20..5adf4b207 100644 --- a/gcloud/alpha/iam/workforce-pools/providers/update-oidc +++ b/gcloud/alpha/iam/workforce-pools/providers/update-oidc @@ -170,9 +170,10 @@ FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/alpha/iam/workforce-pools/update b/gcloud/alpha/iam/workforce-pools/update index 925b20768..c0017ccf0 100644 --- a/gcloud/alpha/iam/workforce-pools/update +++ b/gcloud/alpha/iam/workforce-pools/update @@ -49,9 +49,9 @@ FLAGS length. --disabled - Whether or not the workforce pool is disabled. You cannot use a - disabled workforce pool to perform new token exchanges or sign-ins - using any provider in the workforce pool. + Disables the workforce pool. You cannot use a disabled workforce pool + to perform new token exchanges or sign-ins using any provider in the + workforce pool. Specify --no-disabled to enable a disabled pool. --display-name=DISPLAY_NAME A display name for the workforce pool. Cannot exceed 32 characters in diff --git a/gcloud/alpha/netapp/locations/list b/gcloud/alpha/netapp/locations/list index c2e2378ea..f8d1592ce 100644 --- a/gcloud/alpha/netapp/locations/list +++ b/gcloud/alpha/netapp/locations/list @@ -7,7 +7,13 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List all Cloud NetApp Files locations. + (ALPHA) Lists all Cloud NetApp Files locations. + +EXAMPLES + The following command shows the details for the NetApp Files location named + NAME. + + $ gcloud alpha netapp locations list LIST COMMAND FLAGS --filter=EXPRESSION diff --git a/gcloud/alpha/netapp/volumes/snapshots/delete b/gcloud/alpha/netapp/volumes/snapshots/delete index 3bdbcf72f..9e0c2bf87 100644 --- a/gcloud/alpha/netapp/volumes/snapshots/delete +++ b/gcloud/alpha/netapp/volumes/snapshots/delete @@ -1,6 +1,6 @@ NAME - gcloud alpha netapp volumes snapshots delete - deletes a Cloud NetApp - Volume Snapshot + gcloud alpha netapp volumes snapshots delete - delete a Cloud NetApp Volume + Snapshot SYNOPSIS gcloud alpha netapp volumes snapshots delete @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Deletes a Cloud NetApp Volume Snapshot. + (ALPHA) Delete a Cloud NetApp Volume Snapshot. POSITIONAL ARGUMENTS Snapshot resource - The Snapshot to delete. The arguments in this group diff --git a/gcloud/alpha/netapp/volumes/snapshots/describe b/gcloud/alpha/netapp/volumes/snapshots/describe index f2c240225..e08708fbf 100644 --- a/gcloud/alpha/netapp/volumes/snapshots/describe +++ b/gcloud/alpha/netapp/volumes/snapshots/describe @@ -1,5 +1,5 @@ NAME - gcloud alpha netapp volumes snapshots describe - describes a Cloud NetApp + gcloud alpha netapp volumes snapshots describe - describe a Cloud NetApp Volume Snapshot SYNOPSIS @@ -8,7 +8,7 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Describes a Cloud NetApp Volume Snapshot. + (ALPHA) Describe a Cloud NetApp Volume Snapshot. POSITIONAL ARGUMENTS Snapshot resource - The Snapshot to describe. The arguments in this group diff --git a/gcloud/alpha/netapp/volumes/snapshots/help b/gcloud/alpha/netapp/volumes/snapshots/help index 9445e3dc6..5b8469da8 100644 --- a/gcloud/alpha/netapp/volumes/snapshots/help +++ b/gcloud/alpha/netapp/volumes/snapshots/help @@ -20,16 +20,16 @@ COMMANDS (ALPHA) Creates a Cloud NetApp Volume Snapshot. delete - (ALPHA) Deletes a Cloud NetApp Volume Snapshot. + (ALPHA) Delete a Cloud NetApp Volume Snapshot. describe - (ALPHA) Describes a Cloud NetApp Volume Snapshot. + (ALPHA) Describe a Cloud NetApp Volume Snapshot. list (ALPHA) List Cloud NetApp Volume Snapshots. update - (ALPHA) Creates a Cloud NetApp Volume Snapshot. + (ALPHA) Update a Cloud NetApp Volume Snapshot. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/netapp/volumes/snapshots/update b/gcloud/alpha/netapp/volumes/snapshots/update index 21ca5ebae..3122b55c0 100644 --- a/gcloud/alpha/netapp/volumes/snapshots/update +++ b/gcloud/alpha/netapp/volumes/snapshots/update @@ -1,6 +1,6 @@ NAME - gcloud alpha netapp volumes snapshots update - creates a Cloud NetApp - Volume Snapshot + gcloud alpha netapp volumes snapshots update - update a Cloud NetApp Volume + Snapshot SYNOPSIS gcloud alpha netapp volumes snapshots update @@ -9,7 +9,7 @@ SYNOPSIS [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Creates a Cloud NetApp Volume Snapshot. + (ALPHA) Update a Cloud NetApp Volume Snapshot. POSITIONAL ARGUMENTS Snapshot resource - The Snapshot to update. The arguments in this group diff --git a/gcloud/alpha/redis/instances/update b/gcloud/alpha/redis/instances/update index fbea1108b..72f91cad8 100644 --- a/gcloud/alpha/redis/instances/update +++ b/gcloud/alpha/redis/instances/update @@ -82,10 +82,10 @@ FLAGS Specifies which maintenance version to apply to your instance during self-service maintenance. To view the available maintenance versions for your instance, run gcloud redis instances describe [INSTANCE_ID]. - Acceptable values for this flag are either latest or one of the - specific versions listed by the describe command. If you pass the value - latest, the Memorystore updates to the most recent available - maintenance version during self service maintenance. + Acceptable values for this flag are either current_default or one of + the specific versions listed by the describe command. If you pass the + value current_default, the Memorystore updates to the most recent + available maintenance version during self service maintenance. --persistence-mode=PERSISTENCE_MODE Operation mode for automated persistence. PERSISTENCE_MODE must be one diff --git a/gcloud/alpha/scc/custom-modules/help b/gcloud/alpha/scc/custom-modules/help index 9acafa55a..8a174cdc5 100644 --- a/gcloud/alpha/scc/custom-modules/help +++ b/gcloud/alpha/scc/custom-modules/help @@ -1,11 +1,12 @@ NAME - gcloud alpha scc custom-modules - manage custom modules + gcloud alpha scc custom-modules - manage Cloud SCC + (Security Command Center) custom modules SYNOPSIS gcloud alpha scc custom-modules GROUP [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage custom modules. + (ALPHA) Manage Cloud SCC (Security Command Center) custom modules. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -16,11 +17,13 @@ GROUPS GROUP is one of the following: sha - (ALPHA) Manage custom modules. + (ALPHA) Manage Security Health Analytics custom modules. 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. This variant is also available: + + $ gcloud scc custom-modules diff --git a/gcloud/alpha/scc/custom-modules/sha/create b/gcloud/alpha/scc/custom-modules/sha/create index 54c6cde14..0ca77b510 100644 --- a/gcloud/alpha/scc/custom-modules/sha/create +++ b/gcloud/alpha/scc/custom-modules/sha/create @@ -21,10 +21,6 @@ EXAMPLES --display-name="test_display_name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha create --organization=123 \ - --display-name="test_display_name" \ - --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml To create a Security Health Analytics custom module for given folder 456, run: @@ -33,10 +29,6 @@ EXAMPLES --display-name="test_display_name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha create --folder=456 \ - --display-name="test_display_name" \ - --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml To create a Security Health Analytics custom module for given project 789, run: @@ -45,24 +37,24 @@ EXAMPLES --project=projects/789 --display-name="test_display_name" \ --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha create --project=789 \ - --display-name="test_display_name" \ - --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml REQUIRED FLAGS --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE - Path to a yaml file containing the custom configuration for the - Security Health Analytics custom module. + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. --display-name=DISPLAY_NAME - The text that will be used to represent a Security Health Analytics - custom module display name. Display name must be at most 64 characters + Sets the display name of the Security Health Analytics custom module. + This display name becomes the finding category for all findings that + are returned by this custom module. The display name must be between 1 + and 128 characters, start with a lowercase letter, and contain + alphanumeric characters or underscores only. --enablement-state=ENABLEMENT_STATE - The enablement state of the Security Health Analytics custom module. - ENABLEMENT_STATE must be one of: disabled, enabled, - enablement-state-unspecified, inherited. + Sets the enablement state of the Security Health Analytics custom + module. From the following list of possible enablement states, specify + either enabled or disabled only. ENABLEMENT_STATE must be one of: + disabled, enabled, enablement-state-unspecified, inherited. OPTIONAL FLAGS At most one of these can be specified: @@ -76,8 +68,8 @@ OPTIONAL FLAGS resides. Formatted as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Security Health Analytics custom - module resides. Formatted as projects/789 or just 789. + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -95,5 +87,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha create diff --git a/gcloud/alpha/scc/custom-modules/sha/delete b/gcloud/alpha/scc/custom-modules/sha/delete index 6984e590d..2f4df251a 100644 --- a/gcloud/alpha/scc/custom-modules/sha/delete +++ b/gcloud/alpha/scc/custom-modules/sha/delete @@ -11,40 +11,29 @@ DESCRIPTION (ALPHA) Delete a Security Health Analytics custom module. EXAMPLES - To delete a Security Health Analytics custom module with id 123456 for + To delete a Security Health Analytics custom module with ID 123456 for organization 123, run: $ gcloud alpha scc custom-modules sha delete 123456 \ --organization=organizations/123 - $ gcloud alpha scc custom-modules sha delete 123456 \ - --organization=123 - $ gcloud alpha scc custom-modules sha delete \ - organizations/123/securityHealthAnalyticsSettings/\ - customModules/123456 - To delete a Security Health Analytics custom module with id 123456 for + To delete a Security Health Analytics custom module with ID 123456 for folder 456, run: $ gcloud alpha scc custom-modules sha delete 123456 \ --folder=folders/456 - $ gcloud alpha scc custom-modules sha delete 123456 --folder=456 - $ gcloud alpha scc custom-modules sha delete \ - folders/456/securityHealthAnalyticsSettings/customModules/123456 - To delete a Security Health Analytics custom module with id 123456 for + To delete a Security Health Analytics custom module with ID 123456 for project 789, run: $ gcloud alpha scc custom-modules sha delete 123456 \ --project=projects/789 - $ gcloud alpha scc custom-modules sha delete 123456 --project=789 - $ gcloud alpha scc custom-modules sha delete \ - projects/789/securityHealthAnalyticsSettings/customModules/\ - 123456 POSITIONAL ARGUMENTS CUSTOM_MODULE - Id or the full resource name of the Security Health Analytics custom - module. + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. FLAGS At most one of these can be specified: @@ -58,8 +47,8 @@ FLAGS resides. Formatted as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Security Health Analytics custom - module resides. Formatted as projects/789 or just 789. + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -77,5 +66,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha delete diff --git a/gcloud/alpha/scc/custom-modules/sha/get b/gcloud/alpha/scc/custom-modules/sha/get index 8604cf1f4..6409f9cc6 100644 --- a/gcloud/alpha/scc/custom-modules/sha/get +++ b/gcloud/alpha/scc/custom-modules/sha/get @@ -1,6 +1,6 @@ NAME - gcloud alpha scc custom-modules sha get - get a Security Health Analytics - custom module + gcloud alpha scc custom-modules sha get - get the details of a Security + Health Analytics custom module SYNOPSIS gcloud alpha scc custom-modules sha get CUSTOM_MODULE @@ -8,56 +8,52 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get a Security Health Analytics custom module. + (ALPHA) Get the details of a Security Health Analytics custom module. It + does not resolve INHERITED enablement states to ENABLED or DISABLED for + modules created at ancestor levels. For example, if the module is enabled + at the ancestor level, modules for all child resources will have the + enablement state set to INHERITED. Use gcloud scc custom-modules sha + get-effective to retrieve a custom module with its effective enablement + state. EXAMPLES - To get a Security Health Analytics custom module with id 123456 for - organization 123, run: + To get the details of a Security Health Analytics custom module with ID + 123456 for organization 123, run: $ gcloud alpha scc custom-modules sha get 123456 \ --organization=organizations/123 - $ gcloud alpha scc custom-modules sha get 123456 --organization=123 - $ gcloud alpha scc custom-modules sha get \ - organizations/123/securityHealthAnalyticsSettings/\ - customModules/123456 - To get a Security Health Analytics custom module with id 123456 for folder - 456, run: + To get the details of a Security Health Analytics custom module with ID + 123456 for folder 456, run: $ gcloud alpha scc custom-modules sha get 123456 --folder=folders/456 - $ gcloud alpha scc custom-modules sha get 123456 --folder=456 - $ gcloud alpha scc custom-modules sha get \ - folders/456/securityHealthAnalyticsSettings/customModules/123456 - To get a Security Health Analytics custom module with id 123456 for project - 789, run: + To get the details of a Security Health Analytics custom module with ID + 123456 for project 789, run: $ gcloud alpha scc custom-modules sha get 123456 \ --project=projects/789 - $ gcloud alpha scc custom-modules sha get 123456 --project=789 - $ gcloud alpha scc custom-modules sha get \ - projects/789/securityHealthAnalyticsSettings/customModules/\ - 123456 POSITIONAL ARGUMENTS CUSTOM_MODULE - Id or the full resource name of the Security Health Analytics custom - module. + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. FLAGS At most one of these can be specified: --folder=FOLDER - Folder where the Security Health Analytics custom module resides. - Formatted as folders/456 or just 456. + Folder from which to get the custom module details. Formatted as + folders/456 or just 456. --organization=ORGANIZATION - Organization where the Security Health Analytics custom module - resides. Formatted as organizations/123 or just 123. + Organization from which to get the custom module details. Formatted + as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Security Health Analytics custom - module resides. Formatted as projects/789 or just 789. + ID or number of the project from which to get the custom module + details. Formatted as projects/789 or just 789. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -75,5 +71,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha get diff --git a/gcloud/alpha/scc/custom-modules/sha/get-effective b/gcloud/alpha/scc/custom-modules/sha/get-effective index 4482f51d6..efde45782 100644 --- a/gcloud/alpha/scc/custom-modules/sha/get-effective +++ b/gcloud/alpha/scc/custom-modules/sha/get-effective @@ -1,6 +1,6 @@ NAME - gcloud alpha scc custom-modules sha get-effective - get an effective - Security Health Analytics custom module + gcloud alpha scc custom-modules sha get-effective - get the details of a + Security Health Analytics custom module with effective enablement state SYNOPSIS gcloud alpha scc custom-modules sha get-effective CUSTOM_MODULE @@ -8,61 +8,52 @@ SYNOPSIS [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Get an effective Security Health Analytics custom module. + (ALPHA) Get the details of a Security Health Analytics custom module. For + inherited custom modules, the get-effective command resolves INHERITED + enablement states to ENABLED or DISABLED. For example, if an inherited + custom module is enabled at the ancestor level, then the get-effective + command displays the enablement state as ENABLED instead of INHERITED in a + child folder or project. EXAMPLES - To get an effective Security Health Analytics custom module with id 123456 - for organization 123, run: + To get the details of a Security Health Analytics custom module 123456 with + its effective enablement state from organization 123, run: $ gcloud alpha scc custom-modules sha get-effective 123456 \ --organization=organizations/123 - $ gcloud alpha scc custom-modules sha get-effective 123456 \ - --organization=123 - $ gcloud alpha scc custom-modules sha get-effective \ - organizations/123/securityHealthAnalyticsSettings/\ - effectiveCustomModules/123456 - To get an effective Security Health Analytics custom module with id 123456 - for folder 456, run: + To get the details of a Security Health Analytics custom module 123456 with + its effective enablement state from folder 456, run: $ gcloud alpha scc custom-modules sha get-effective 123456 \ --folder=folders/456 - $ gcloud alpha scc custom-modules sha get-effective 123456 \ - --folder=456 - $ gcloud alpha scc custom-modules sha get-effective \ - folders/456/securityHealthAnalyticsSettings/\ - effectiveCustomModules/123456 - To get an effective Security Health Analytics custom module with id 123456 - for project 789, run: + To get the details of a Security Health Analytics custom module 123456 with + its effective enablement state from project 789, run: $ gcloud alpha scc custom-modules sha get-effective 123456 \ --project=projects/789 - $ gcloud alpha scc custom-modules sha get-effective 123456 \ - --project=789 - $ gcloud alpha scc custom-modules sha get-effective \ - projects/789/securityHealthAnalyticsSettings/\ - effectiveCustomModules/123456 POSITIONAL ARGUMENTS CUSTOM_MODULE - Id or the full resource name of the effective Security Health Analytics - custom module. + ID or the full resource name of the effective Security Health Analytics + custom module. If you specify the full resource name, you do not need + to specify the --organization, --folder, or --project flags. FLAGS At most one of these can be specified: --folder=FOLDER - Folder where the effective Security Health Analytics custom module - resides. Formatted as folders/456 or just 456. + Folder from which to get the custom module details. Formatted as + folders/456 or just 456. --organization=ORGANIZATION - Organization where the effective Security Health Analytics custom - module resides. Formatted as organizations/123 or just 123. + Organization from which to get the custom module details. Formatted + as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the effective Security Health Analytics - custom module resides. Formatted as projects/789 or just 789. + ID or number of the project from which to get the custom module + details. Formatted as projects/789 or just 789. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -80,5 +71,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha get-effective diff --git a/gcloud/alpha/scc/custom-modules/sha/help b/gcloud/alpha/scc/custom-modules/sha/help index fdf2eb28e..5e9692f75 100644 --- a/gcloud/alpha/scc/custom-modules/sha/help +++ b/gcloud/alpha/scc/custom-modules/sha/help @@ -1,11 +1,12 @@ NAME - gcloud alpha scc custom-modules sha - manage custom modules + gcloud alpha scc custom-modules sha - manage Security Health Analytics + custom modules SYNOPSIS gcloud alpha scc custom-modules sha COMMAND [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) Manage custom modules. + (ALPHA) Manage Security Health Analytics custom modules. GCLOUD WIDE FLAGS These flags are available to all commands: --help. @@ -22,19 +23,22 @@ COMMANDS (ALPHA) Delete a Security Health Analytics custom module. get - (ALPHA) Get a Security Health Analytics custom module. + (ALPHA) Get the details of a Security Health Analytics custom module. get-effective - (ALPHA) Get an effective Security Health Analytics custom module. + (ALPHA) Get the details of a Security Health Analytics custom module + with effective enablement state. list - (ALPHA) List Security Health Analytics custom modules. + (ALPHA) List the details of Security Health Analytics custom modules. list-descendant - (ALPHA) List Descendant Security Health Analytics custom modules. + (ALPHA) List the details of the resident and descendant Security Health + Analytics custom modules. list-effective - (ALPHA) List Effective Security Health Analytics custom modules. + (ALPHA) List the details of Security Health Analytics custom modules + with effective enablement states. test (ALPHA) Test a Security Health Analytics custom module. @@ -46,5 +50,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha diff --git a/gcloud/alpha/scc/custom-modules/sha/list b/gcloud/alpha/scc/custom-modules/sha/list index 049838d58..f6b201af6 100644 --- a/gcloud/alpha/scc/custom-modules/sha/list +++ b/gcloud/alpha/scc/custom-modules/sha/list @@ -1,6 +1,6 @@ NAME - gcloud alpha scc custom-modules sha list - list Security Health Analytics - custom modules + gcloud alpha scc custom-modules sha list - list the details of Security + Health Analytics custom modules SYNOPSIS gcloud alpha scc custom-modules sha list @@ -9,40 +9,48 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Security Health Analytics custom modules. + (ALPHA) List the details of the resident and inherited Security Health + Analytics custom modules for the specified folder or project. For an + organization, this command lists only the custom modules that are created + at the organization level. Custom modules created in child folders or + projects are not included in the list. To list the resident custom modules + and the modules that are created in child folders or projects, use gcloud + scc custom-modules sha list-descendant. EXAMPLES - To list Security Health Analytics custom modules under organization 123, - run: + To list resident and inherited Security Health Analytics custom modules for + organization 123, run: $ gcloud alpha scc custom-modules sha list \ --organization=organizations/123 - $ gcloud alpha scc custom-modules sha list --organization=123 - To list Security Health Analytics custom modules under folder 456, run: + To list resident and inherited Security Health Analytics custom modules for + folder 456, run: $ gcloud alpha scc custom-modules sha list --folder=folders/456 - $ gcloud alpha scc custom-modules sha list --folder=456 - To list Security Health Analytics custom modules under project 789, run: + To list resident and inherited Security Health Analytics custom modules for + project 789, run: $ gcloud alpha scc custom-modules sha list --project=projects/789 - $ gcloud alpha scc custom-modules sha list --project=789 REQUIRED FLAGS Exactly one of these must be specified: --folder=FOLDER - Folder where the Security Health Analytics custom modules resides. - Formatted as folders/456 or just 456. + Folder for listing the Security Health Analytics custom modules + created at the current folder level and inherited modules from CRM + ancestors. Formatted as folders/456 or just 456. --organization=ORGANIZATION - Organization where the Security Health Analytics custom modules - resides. Formatted as organizations/123 or just 123. + Organization for listing the Security Health Analytics custom modules + created at the organization level. Formatted as organizations/123 or + just 123. --project=PROJECT - Project (id or number) where the Security Health Analytics custom - modules resides. Formatted as projects/789 or just 789. + ID or number of the project for listing the Security Health Analytics + custom modules created at current project level and inherited modules + from CRM ancestors. Formatted as projects/789 or just 789. LIST COMMAND FLAGS --filter=EXPRESSION @@ -86,5 +94,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha list diff --git a/gcloud/alpha/scc/custom-modules/sha/list-descendant b/gcloud/alpha/scc/custom-modules/sha/list-descendant index 1de5f17f3..8831ab68d 100644 --- a/gcloud/alpha/scc/custom-modules/sha/list-descendant +++ b/gcloud/alpha/scc/custom-modules/sha/list-descendant @@ -1,6 +1,6 @@ NAME - gcloud alpha scc custom-modules sha list-descendant - list Descendant - Security Health Analytics custom modules + gcloud alpha scc custom-modules sha list-descendant - list the details of + the resident and descendant Security Health Analytics custom modules SYNOPSIS gcloud alpha scc custom-modules sha list-descendant @@ -9,45 +9,50 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Descendant Security Health Analytics custom modules. + (ALPHA) List the details of the resident and descendant Security Health + Analytics custom modules for a specified organization or folder. For a + project, this command lists only the custom modules that are created in the + project. Modules created in a parent organization or folder are excluded + from the list. To list the resident custom modules and the modules that are + inherited from a parent organization and folder, use gcloud scc + custom-modules sha list. EXAMPLES - To list Descendant Security Health Analytics custom modules under - organization 123, run: + To list resident and descendant Security Health Analytics custom modules + for organization 123, run: $ gcloud alpha scc custom-modules sha list-descendant \ --organization=organizations/123 - $ gcloud alpha scc custom-modules sha list-descendant \ - --organization=123 - To list Descendant Security Health Analytics custom modules under folder - 456, run: + To list resident and descendant Security Health Analytics custom modules + for folder 456, run: $ gcloud alpha scc custom-modules sha list-descendant \ --folder=folders/456 - $ gcloud alpha scc custom-modules sha list-descendant --folder=456 - To list Descendant Security Health Analytics custom modules under project - 789, run: + To list resident and descendant Security Health Analytics custom modules + for project 789, run: $ gcloud alpha scc custom-modules sha list-descendant \ --project=projects/789 - $ gcloud alpha scc custom-modules sha list-descendant --project=789 REQUIRED FLAGS Exactly one of these must be specified: --folder=FOLDER - Folder where the Descendant Security Health Analytics custom modules - resides. Formatted as folders/456 or just 456. + Folder for listing the Security Health Analytics custom modules + created at the current folder level and its child resources. + Formatted as folders/456 or just 456. --organization=ORGANIZATION - Organization where the Descendant Security Health Analytics custom - modules resides. Formatted as organizations/123 or just 123. + Organization for listing the Security Health Analytics custom modules + created at the organization level and its child resources. Formatted + as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Descendant Security Health Analytics - custom modules resides. Formatted as projects/789 or just 789. + ID or number of the project for listing the Security Health Analytics + custom modules at current project level. Formatted as projects/789 or + just 789. LIST COMMAND FLAGS --filter=EXPRESSION @@ -91,5 +96,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha list-descendant diff --git a/gcloud/alpha/scc/custom-modules/sha/list-effective b/gcloud/alpha/scc/custom-modules/sha/list-effective index acc9057b7..9abd3d8b0 100644 --- a/gcloud/alpha/scc/custom-modules/sha/list-effective +++ b/gcloud/alpha/scc/custom-modules/sha/list-effective @@ -1,6 +1,7 @@ NAME - gcloud alpha scc custom-modules sha list-effective - list Effective - Security Health Analytics custom modules + gcloud alpha scc custom-modules sha list-effective - list the details of + Security Health Analytics custom modules with effective enablement + states SYNOPSIS gcloud alpha scc custom-modules sha list-effective @@ -9,45 +10,48 @@ SYNOPSIS [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] DESCRIPTION - (ALPHA) List Effective Security Health Analytics custom modules. + (ALPHA) List the details of resident and inherited Security Health + Analytics custom modules for the specified folder or project with their + effective enablement states. For an organization, this command lists only + the custom modules that are created at the organization level. Custom + modules created in child folders or projects are not included in the list. EXAMPLES - To list Effective Security Health Analytics custom modules under - organization 123, run: + To list resident and inherited Security Health Analytics custom modules + with effective enablement states for organization 123, run: $ gcloud alpha scc custom-modules sha list-effective \ --organization=organizations/123 - $ gcloud alpha scc custom-modules sha list-effective \ - --organization=123 - To list Effective Security Health Analytics custom modules under folder - 456, run: + To list resident and inherited effective Security Health Analytics custom + modules with effective enablement states for folder 456, run: $ gcloud alpha scc custom-modules sha list-effective \ --folder=folders/456 - $ gcloud alpha scc custom-modules sha list-effective --folder=456 - To list Effective Security Health Analytics custom modules under project - 789, run: + To list resident and inherited effective Security Health Analytics custom + modules with effective enablement states for project 789, run: $ gcloud alpha scc custom-modules sha list-effective \ --project=projects/789 - $ gcloud alpha scc custom-modules sha list-effective --project=789 REQUIRED FLAGS Exactly one of these must be specified: --folder=FOLDER - Folder where the Effective Security Health Analytics custom modules - resides. Formatted as folders/456 or just 456. + Folder for listing the effective Security Health Analytics custom + modules created at the current folder level and inherited modules + from CRM ancestors. Formatted as folders/456 or just 456. --organization=ORGANIZATION - Organization where the Effective Security Health Analytics custom - modules resides. Formatted as organizations/123 or just 123. + Organization for listing the effective Security Health Analytics + custom modules created at the organization level. Formatted as + organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Effective Security Health Analytics - custom modules resides. Formatted as projects/789 or just 789. + ID or number of the project for listing the effective Security Health + Analytics custom modules for the current project level and inherited + modules from CRM ancestors. Formatted as projects/789 or just 789. LIST COMMAND FLAGS --filter=EXPRESSION @@ -91,5 +95,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha list-effective diff --git a/gcloud/alpha/scc/custom-modules/sha/test b/gcloud/alpha/scc/custom-modules/sha/test index 9af4e92c7..aab38d333 100644 --- a/gcloud/alpha/scc/custom-modules/sha/test +++ b/gcloud/alpha/scc/custom-modules/sha/test @@ -14,74 +14,54 @@ DESCRIPTION (ALPHA) Test a Security Health Analytics custom module. EXAMPLES - To test a Security Health Analytics custom module with id 123456 for + To test a Security Health Analytics custom module with ID 123456 for organization 123, run: $ gcloud alpha scc custom-modules sha test 123456 \ --organization=organizations/123 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml - $ gcloud alpha scc custom-modules sha test 123456 \ - --organization=123 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml - $ gcloud alpha scc custom-modules sha test \ - organizations/123/securityHealthAnalyticsSettings/\ - customModules/123456 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml + --display-name="test_display_name" \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --test-data-from-file=/tmp/test_data.yaml - To test a Security Health Analytics custom module with id 123456 for folder + To test a Security Health Analytics custom module with ID 123456 for folder 456, run: $ gcloud alpha scc custom-modules sha test 123456 \ - --folder=folders/456 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml - $ gcloud alpha scc custom-modules sha test 123456 --folder=456 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml - $ gcloud alpha scc custom-modules sha test \ - folders/456/securityHealthAnalyticsSettings/customModules/\ - 123456 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml + --folder=folders/456 --display-name="test_display_name" \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --test-data-from-file=/tmp/test_data.yaml - To test a Security Health Analytics custom module with id 123456 for + To test a Security Health Analytics custom module with ID 123456 for project 789, run: $ gcloud alpha scc custom-modules sha test 123456 \ - --project=projects/789 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml - $ gcloud alpha scc custom-modules sha test 123456 --project=789 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml - $ gcloud alpha scc custom-modules sha test \ - projects/789/securityHealthAnalyticsSettings/customModules/\ - 123456 \ - --display-name="test_display_name"--custom-config-from-file=/\ - tmp/custom_config.yaml --test-data-from-file=/tmp/test_data.yaml + --project=projects/789 --display-name="test_display_name" \ + --custom-config-from-file=/tmp/custom_config.yaml \ + --test-data-from-file=/tmp/test_data.yaml POSITIONAL ARGUMENTS CUSTOM_MODULE - Id or the full resource name of the Security Health Analytics custom - module. + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. REQUIRED FLAGS --test-data-from-file=TEST_DATA_FROM_FILE - Path to a YAML file containing the resource data to test the Security - Health Analytics custom module against. + Path to a YAML file that contains the resource data to test the + Security Health Analytics custom module against. OPTIONAL FLAGS --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE - Path to a YAML file containing the custom configuration for the - Security Health Analytics custom module. If not specified, the existing - module with the given ID or resource name is used. + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. If not specified, the existing module + with the given ID or resource name is used. --display-name=DISPLAY_NAME - Display name of the Security Health Analytics custom module. Display - name must be at most 64 characters. Only relevant when + Sets the display name of the Security Health Analytics custom module. + This display name becomes the finding category for all findings that + are returned by this the custom module. The display name must be + between 1 and 128 characters, start with a lowercase letter, and + contain alphanumeric characters or underscores only. Only relevant when --custom-config-from-file is also specified. At most one of these can be specified: @@ -95,8 +75,8 @@ OPTIONAL FLAGS resides. Formatted as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Security Health Analytics custom - module resides. Formatted as projects/789 or just 789. + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/alpha/scc/custom-modules/sha/update b/gcloud/alpha/scc/custom-modules/sha/update index d1427dd76..a3a3603d1 100644 --- a/gcloud/alpha/scc/custom-modules/sha/update +++ b/gcloud/alpha/scc/custom-modules/sha/update @@ -13,62 +13,43 @@ DESCRIPTION (ALPHA) Update a Security Health Analytics custom module. EXAMPLES - To update a Security Health Analytics custom module with id 123456 for + To update a Security Health Analytics custom module with ID 123456 for organization 123, run: $ gcloud alpha scc custom-modules sha update 123456 \ --organization=organizations/123 --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha update 123456 \ - --organization=123 --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha update \ - organizations/123/securityHealthAnalyticsSettings/\ - customModules/123456 --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml - To update a Security Health Analytics custom module with id 123456 for + To update a Security Health Analytics custom module with ID 123456 for folder 456, run: $ gcloud alpha scc custom-modules sha update 123456 \ --folder=folders/456 --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha update 123456 --folder=456 \ - --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha update \ - folders/456/securityHealthAnalyticsSettings/customModules/\ - 123456 --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml - To update a Security Health Analytics custom module with id 123456 for + To update a Security Health Analytics custom module with ID 123456 for project 789, run: $ gcloud alpha scc custom-modules sha update 123456 \ --project=projects/789 --enablement-state="ENABLED" \ --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha update 123456 --project=789 \ - --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml - $ gcloud alpha scc custom-modules sha update \ - projects/789/securityHealthAnalyticsSettings/customModules/\ - 123456 --enablement-state="ENABLED" \ - --custom-config-from-file=custom_config.yaml POSITIONAL ARGUMENTS CUSTOM_MODULE - Id or the full resource name of the Security Health Analytics custom - module. + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. FLAGS --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE - Path to a yaml file containing the custom configuration for the - Security Health Analytics custom module. + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. --enablement-state=ENABLEMENT_STATE - The enablement state of the Security Health Analytics custom module. - ENABLEMENT_STATE must be one of: disabled, enabled, - enablement-state-unspecified, inherited. + Sets the enablement state of the Security Health Analytics custom + module. From the following list of possible enablement states, specify + either enabled, disabled or inherited only. ENABLEMENT_STATE must be + one of: disabled, enabled, enablement-state-unspecified, inherited. --update-mask=UPDATE_MASK Optional: If left unspecified (default), an update-mask is @@ -86,8 +67,8 @@ FLAGS resides. Formatted as organizations/123 or just 123. --project=PROJECT - Project (id or number) where the Security Health Analytics custom - module resides. Formatted as projects/789 or just 789. + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, @@ -105,5 +86,7 @@ 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. This variant is also available: + + $ gcloud scc custom-modules sha update diff --git a/gcloud/alpha/scc/help b/gcloud/alpha/scc/help index a3ac1f2aa..481bcb5e7 100644 --- a/gcloud/alpha/scc/help +++ b/gcloud/alpha/scc/help @@ -20,7 +20,7 @@ GROUPS (ALPHA) Manage Cloud SCC (Security Command Center) assets. custom-modules - (ALPHA) Manage custom modules. + (ALPHA) Manage Cloud SCC (Security Command Center) custom modules. findings (ALPHA) Manage Cloud SCC (Security Command Center) findings. diff --git a/gcloud/batch/jobs/submit b/gcloud/batch/jobs/submit index 942be33ce..9401d7b43 100644 --- a/gcloud/batch/jobs/submit +++ b/gcloud/batch/jobs/submit @@ -9,7 +9,8 @@ SYNOPSIS | --script-file-path=SCRIPT_FILE_PATH | --script-text=SCRIPT_TEXT) [--machine-type=MACHINE_TYPE] [--priority=PRIORITY] [--provisioning-model=PROVISIONING_MODEL] - [--network=NETWORK --subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...] + [--network=NETWORK --subnetwork=SUBNETWORK : --no-external-ip-address] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION This command can fail for the following reasons: @@ -139,6 +140,11 @@ OPTIONAL FLAGS The URL for the subnetwork resource. Must specify network as well if subnetwork is specified + --no-external-ip-address + Required if no external public IP address is attached to the VM. If no + external public IP address, additional configuration is required to + allow the VM to access Google Services. + 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/batch/jobs/submit b/gcloud/beta/batch/jobs/submit index 32af1edb8..302fc259b 100644 --- a/gcloud/beta/batch/jobs/submit +++ b/gcloud/beta/batch/jobs/submit @@ -9,7 +9,8 @@ SYNOPSIS | --script-file-path=SCRIPT_FILE_PATH | --script-text=SCRIPT_TEXT) [--machine-type=MACHINE_TYPE] [--priority=PRIORITY] [--provisioning-model=PROVISIONING_MODEL] - [--network=NETWORK --subnetwork=SUBNETWORK] [GCLOUD_WIDE_FLAG ...] + [--network=NETWORK --subnetwork=SUBNETWORK : --no-external-ip-address] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION (BETA) This command can fail for the following reasons: @@ -139,6 +140,11 @@ OPTIONAL FLAGS The URL for the subnetwork resource. Must specify network as well if subnetwork is specified + --no-external-ip-address + Required if no external public IP address is attached to the VM. If no + external public IP address, additional configuration is required to + allow the VM to access Google Services. + 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/bigtable/app-profiles/update b/gcloud/beta/bigtable/app-profiles/update index c762b50cf..8eef35e16 100644 --- a/gcloud/beta/bigtable/app-profiles/update +++ b/gcloud/beta/bigtable/app-profiles/update @@ -93,6 +93,10 @@ FLAGS --transactional-writes Allow transactional writes with a Single Cluster Routing policy. + If your app profile has single row transactions enabled, you must + specify this flag when updating that app profile. If you do not + specify this flag, then single row transactions are disabled. + 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/builds/triggers/create/bitbucketserver b/gcloud/beta/builds/triggers/create/bitbucketserver index f6251968a..db61d3009 100644 --- a/gcloud/beta/builds/triggers/create/bitbucketserver +++ b/gcloud/beta/builds/triggers/create/bitbucketserver @@ -11,7 +11,7 @@ SYNOPSIS default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -92,8 +92,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/beta/builds/triggers/create/cloud-source-repositories b/gcloud/beta/builds/triggers/create/cloud-source-repositories index 729fd1a3c..120a0486e 100644 --- a/gcloud/beta/builds/triggers/create/cloud-source-repositories +++ b/gcloud/beta/builds/triggers/create/cloud-source-repositories @@ -10,7 +10,7 @@ SYNOPSIS default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -71,8 +71,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/beta/builds/triggers/create/github b/gcloud/beta/builds/triggers/create/github index b7fae51ac..fe51d7bf4 100644 --- a/gcloud/beta/builds/triggers/create/github +++ b/gcloud/beta/builds/triggers/create/github @@ -14,7 +14,7 @@ SYNOPSIS : --enterprise-config=ENTERPRISE_CONFIG]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --include-logs-with-status --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -83,8 +83,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/beta/builds/triggers/create/gitlab-enterprise b/gcloud/beta/builds/triggers/create/gitlab-enterprise index 1c72a9750..d2d1e85de 100644 --- a/gcloud/beta/builds/triggers/create/gitlab-enterprise +++ b/gcloud/beta/builds/triggers/create/gitlab-enterprise @@ -13,7 +13,7 @@ SYNOPSIS (--gitlab-config-resource=GITLAB_CONFIG_RESOURCE --project-namespace=PROJECT_NAMESPACE) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME - --region=REGION --require-approval + --region=REGION --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -73,8 +73,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/beta/builds/triggers/create/manual b/gcloud/beta/builds/triggers/create/manual index ed2ba8e55..465af31c4 100644 --- a/gcloud/beta/builds/triggers/create/manual +++ b/gcloud/beta/builds/triggers/create/manual @@ -8,10 +8,9 @@ SYNOPSIS | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -58,8 +57,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -145,10 +145,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/beta/builds/triggers/create/pubsub b/gcloud/beta/builds/triggers/create/pubsub index b98d0f074..181dc9540 100644 --- a/gcloud/beta/builds/triggers/create/pubsub +++ b/gcloud/beta/builds/triggers/create/pubsub @@ -9,11 +9,10 @@ SYNOPSIS : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --subscription-filter=SUBSCRIPTION_FILTER --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -71,8 +70,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -163,10 +163,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/beta/builds/triggers/create/webhook b/gcloud/beta/builds/triggers/create/webhook index 756e6dd35..1cc5e8b88 100644 --- a/gcloud/beta/builds/triggers/create/webhook +++ b/gcloud/beta/builds/triggers/create/webhook @@ -9,11 +9,10 @@ SYNOPSIS : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --subscription-filter=SUBSCRIPTION_FILTER --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -77,8 +76,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -169,10 +169,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/beta/compute/images/import b/gcloud/beta/compute/images/import index 510bb7476..56f81034b 100644 --- a/gcloud/beta/compute/images/import +++ b/gcloud/beta/compute/images/import @@ -3,13 +3,13 @@ NAME SYNOPSIS gcloud beta compute images import IMAGE_NAME - (--aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION + (--source-file=SOURCE_FILE | --source-image=SOURCE_IMAGE + | --aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION --aws-secret-access-key=AWS_SECRET_ACCESS_KEY --aws-session-token=AWS_SESSION_TOKEN (--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH | --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION - --aws-ami-id=AWS_AMI_ID) | --source-file=SOURCE_FILE - | --source-image=SOURCE_IMAGE) [--no-address] [--async] + --aws-ami-id=AWS_AMI_ID)) [--no-address] [--async] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -59,6 +59,20 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + Image import from local file, Cloud Storage or Compute Engine image. + + At most one of these can be specified: + + --source-file=SOURCE_FILE + A local file, or the Cloud Storage URI of the virtual disk file to + import. For example: gs://my-bucket/my-image.vmdk or + ./my-local-image.vmdk. For more information about Cloud Storage + URIs, see + https://cloud.google.com/storage/docs/request-endpoints#json-api. + + --source-image=SOURCE_IMAGE + An existing Compute Engine image from which to import. + Image import from AWS. --aws-access-key-id=AWS_ACCESS_KEY_ID @@ -113,20 +127,6 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - Image import from local file, Cloud Storage or Compute Engine image. - - At most one of these can be specified: - - --source-file=SOURCE_FILE - A local file, or the Cloud Storage URI of the virtual disk file to - import. For example: gs://my-bucket/my-image.vmdk or - ./my-local-image.vmdk. For more information about Cloud Storage - URIs, see - https://cloud.google.com/storage/docs/request-endpoints#json-api. - - --source-image=SOURCE_IMAGE - An existing Compute Engine image from which to import. - OPTIONAL FLAGS --no-address Temporary VMs are created in your project during image import. Set this diff --git a/gcloud/beta/compute/instances/bulk/create b/gcloud/beta/compute/instances/bulk/create index 4b97fd70f..4bc7f1745 100644 --- a/gcloud/beta/compute/instances/bulk/create +++ b/gcloud/beta/compute/instances/bulk/create @@ -23,6 +23,7 @@ SYNOPSIS [--local-ssd=[device-name=DEVICE-NAME], [interface=INTERFACE],[size=SIZE]] [--location-policy=[ZONE=POLICY,...]] [--machine-type=MACHINE_TYPE] + [--max-count-per-zone=[ZONE=MAX_COUNT_PER_ZONE,...]] [--max-run-duration=MAX_RUN_DURATION] [--metadata=KEY=VALUE,[KEY=VALUE,...]] [--metadata-from-file=KEY=LOCAL_FILE_PATH,[...]] @@ -464,6 +465,17 @@ OPTIONAL FLAGS available machine types, run 'gcloud compute machine-types list'. If unspecified, the default type is n1-standard-1. + --max-count-per-zone=[ZONE=MAX_COUNT_PER_ZONE,...] + Maximum number of instances per zone specified as key-value pairs. The + zone name is the key and the max count per zone is the value in that + zone. + + Example: + + gcloud compute instances bulk create --name-pattern=example-### + --count=5 --region=us-east1 + --max-count-per-zone=us-east1-b=2,us-east-1-c=1 + --max-run-duration=MAX_RUN_DURATION Limits how long this VM instance can run, specified as a duration relative to the VM instance's most-recent start time. Format the diff --git a/gcloud/beta/container/bare-metal/admin-clusters/create b/gcloud/beta/container/bare-metal/admin-clusters/create new file mode 100644 index 000000000..2a93e4e80 --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/create @@ -0,0 +1,250 @@ +NAME + gcloud beta container bare-metal admin-clusters create - create an Anthos + on bare metal admin cluster + +SYNOPSIS + gcloud beta container bare-metal admin-clusters create + (ADMIN_CLUSTER : --location=LOCATION) --version=VERSION + (--control-plane-load-balancer-port=CONTROL_PLANE_LOAD_BALANCER_PORT + --control-plane-vip=CONTROL_PLANE_VIP : --enable-manual-lb) + ((((--control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + : --control-plane-node-labels=[KEY=VALUE,...] + --control-plane-node-taints=[KEY=VALUE:EFFECT,...]))) + : --api-server-args=[KEY=VALUE,...]) + (--island-mode-pod-address-cidr-blocks=POD_ADDRESS,[POD_ADDRESS,...] + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]) + ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH + --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT)) + [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async] + [--description=DESCRIPTION] [--enable-application-logs] + [--login-user=LOGIN_USER] + [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, + ...]] [--max-pods-per-node=MAX_PODS_PER_NODE] [--validate-only] + [--uri=URI : --no-proxy=[NO_PROXY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Anthos on bare metal admin cluster. + +EXAMPLES + To create a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container bare-metal admin-clusters create \ + my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster 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 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_bare_metal/location. + +REQUIRED FLAGS + --version=VERSION + Anthos cluster on bare metal version for the admin cluster resource. + + Anthos on bare metal admin cluster load balancer configuration. + + This must be specified. + + Control plane load balancer port configuration. + + This must be specified. + + --control-plane-load-balancer-port=CONTROL_PLANE_LOAD_BALANCER_PORT + Control plane load balancer port configuration. + + VIPs used by the load balancer. + + This must be specified. + + --control-plane-vip=CONTROL_PLANE_VIP + VIP for the Kubernetes API of this cluster. + + Manual load balancer configuration. + + --enable-manual-lb + ManualLB typed load balancers configuration. + + Anthos on bare metal cluster control plane configuration. + + At least one of these must be specified: + + --api-server-args=[KEY=VALUE,...] + API Server argument configuration. + + Anthos on bare metal cluster control plane node pool configuration. + + This must be specified. + + Anthos on bare metal node pool configuration for control plane nodes. + + This must be specified. + + Anthos on bare metal node configuration for control plane nodes. + + This must be specified. + + Populate control plane node config. + + Exactly one of these must be specified: + + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + Control plane node configuration. + + --control-plane-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Populate one of the network configs. + + This must be specified. + + Island mode CIDR network configuration. + + --island-mode-pod-address-cidr-blocks=POD_ADDRESS,[POD_ADDRESS,...] + IPv4 address range for all pods in the cluster. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + IPv4 address range for all services in the cluster. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Anthos on bare metal cluster storage configuration. + + This must be specified. + + LVP node mounts class and path used by the storage. + + This must be specified. + + --lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH + Path for the LVP node mounts class. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS + Storage class for LVP node mounts. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + LVP share configuration. + + At least one of these must be specified: + + --shared-path-pv-count=SHARED_PATH_PV_COUNT + Number of subdirectories to create under path. + + LVP share class and path used by the storage. + + This must be specified. + + --lvp-share-path=LVP_SHARE_PATH + Path for the LVP share class. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS + Storage class for LVP share. + + This flag argument must be specified if any of the other + arguments in this group are specified. + +OPTIONAL FLAGS + Anthos on bare metal admin cluster security configuration. + + Admin cluster authorization configurations + + --admin-users=ADMIN_USERS + Users that will be granted the view role on the admin cluster, + providing view only access to the cluster. + + --annotations=[KEY=VALUE,...] + Annotations on the Anthos on bare metal resource. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description for the resource. + + Anthos on bare metal cluster operations configuration. + + --enable-application-logs + Whether collection of application logs/metrics should be enabled (in + addition to system logs/metrics). + + Anthos on bare metal node access related settings for the admin cluster. + + --login-user=LOGIN_USER + User name used to access node machines. + + Anthos on bare metal cluster maintenance configuration. + + --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] + IPv4 addresses to be placed into maintenance mode. + + Anthos on bare metal admin cluster workload node configuration. + + --max-pods-per-node=MAX_PODS_PER_NODE + Maximum number of pods a node can run. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + Anthos on bare metal cluster proxy configuration. + + --uri=URI + Address of the proxy server. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --no-proxy=[NO_PROXY,...] + List of IPs, hostnames, and domains that should skip the proxy. + +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 bare-metal admin-clusters create + diff --git a/gcloud/beta/container/bare-metal/admin-clusters/describe b/gcloud/beta/container/bare-metal/admin-clusters/describe new file mode 100644 index 000000000..b8ff0113a --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/describe @@ -0,0 +1,60 @@ +NAME + gcloud beta container bare-metal admin-clusters describe - describe an + Anthos on bare metal admin cluster + +SYNOPSIS + gcloud beta container bare-metal admin-clusters describe + (ADMIN_CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Anthos on bare metal admin cluster. + +EXAMPLES + To describe an admin cluster named my-cluster managed in location us-west1, + run: + + $ gcloud beta container bare-metal admin-clusters describe \ + my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster 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 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_bare_metal/location. + +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 bare-metal admin-clusters describe + diff --git a/gcloud/beta/container/bare-metal/admin-clusters/enroll b/gcloud/beta/container/bare-metal/admin-clusters/enroll new file mode 100644 index 000000000..e9cffcf73 --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/enroll @@ -0,0 +1,103 @@ +NAME + gcloud beta container bare-metal admin-clusters enroll - enroll an Anthos + on bare metal admin cluster + +SYNOPSIS + gcloud beta container bare-metal admin-clusters enroll + (ADMIN_CLUSTER : --location=LOCATION) + (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global") + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enroll an Anthos on bare metal admin cluster. + +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud beta container bare-metal admin-clusters enroll \ + my-cluster --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster to enroll 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_bare_metal/location. + +REQUIRED FLAGS + Admin cluster membership resource - membership of the admin cluster. + Membership can be the membership ID or the full resource name. 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-membership 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-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier for + the admin_cluster_membership. To set the admin_cluster_membership + attribute: + ▸ provide the argument --admin-cluster-membership on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global" + Google Cloud location for the admin_cluster_membership. To set the + location attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-location on the + command line. + +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. This + variant is also available: + + $ gcloud alpha container bare-metal admin-clusters enroll + diff --git a/gcloud/beta/container/bare-metal/admin-clusters/help b/gcloud/beta/container/bare-metal/admin-clusters/help new file mode 100644 index 000000000..f280dcdef --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/help @@ -0,0 +1,44 @@ +NAME + gcloud beta container bare-metal admin-clusters - create and manage admin + clusters in Anthos on bare metal + +SYNOPSIS + gcloud beta container bare-metal admin-clusters COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage admin clusters in Anthos on bare metal. + +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 an Anthos on bare metal admin cluster. + + describe + (BETA) Describe an Anthos on bare metal admin cluster. + + enroll + (BETA) Enroll an Anthos on bare metal admin cluster. + + list + (BETA) List Anthos on bare metal admin clusters. + + query-version-config + (BETA) Query versions for creating or upgrading an Anthos on bare metal + admin cluster. + + update + (BETA) Update an Anthos on bare metal admin cluster. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container bare-metal admin-clusters + diff --git a/gcloud/beta/container/bare-metal/admin-clusters/list b/gcloud/beta/container/bare-metal/admin-clusters/list new file mode 100644 index 000000000..250b6e140 --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/list @@ -0,0 +1,82 @@ +NAME + gcloud beta container bare-metal admin-clusters list - list Anthos on bare + metal admin clusters + +SYNOPSIS + gcloud beta container bare-metal admin-clusters list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Anthos on bare metal admin clusters. + +EXAMPLES + To list all admin clusters managed in location us-west1, run: + + $ gcloud beta container bare-metal admin-clusters list \ + --location=us-west1 + +FLAGS + Location resource - Google Cloud location to list Anthos on bare metal + admin clusters. This represents a Cloud resource. (NOTE) Some attributes + are not given arguments in this group but can be set in other ways. To set + the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_bare_metal/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal admin-clusters list + diff --git a/gcloud/beta/container/bare-metal/admin-clusters/query-version-config b/gcloud/beta/container/bare-metal/admin-clusters/query-version-config new file mode 100644 index 000000000..2ee7ea7e6 --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/query-version-config @@ -0,0 +1,82 @@ +NAME + gcloud beta container bare-metal admin-clusters query-version-config - + query versions for creating or upgrading an Anthos on bare metal admin + cluster + +SYNOPSIS + gcloud beta container bare-metal admin-clusters query-version-config + [--admin-cluster=ADMIN_CLUSTER] [--location=LOCATION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Query versions for creating or upgrading an Anthos on bare metal + admin cluster. + +EXAMPLES + To query versions for creating an admin cluster in location us-west1, run: + + $ gcloud beta container bare-metal admin-clusters \ + query-version-config --location=us-west1 + + To query versions for upgrading an admin cluster named my-admin-cluster in + location us-west1, run: + + $ gcloud beta container bare-metal admin-clusters \ + query-version-config --location=us-west1 \ + --admin-cluster=my-admin-cluster + +FLAGS + Use cases for querying versions. + + Upgrade an Anthos on bare metal admin cluster use case. + + Admin cluster resource - Admin cluster to query versions for upgrade. + 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 --admin-cluster 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 --admin-cluster on the command line with a + fully specified name; + ▫ provide the argument --location on the command line; + ▫ set the property container_bare_metal/location. + + --admin-cluster=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. + + Location resource - Google Cloud location to query versions. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_bare_metal/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal admin-clusters \ + query-version-config + diff --git a/gcloud/beta/container/bare-metal/admin-clusters/update b/gcloud/beta/container/bare-metal/admin-clusters/update new file mode 100644 index 000000000..f3d9f8ada --- /dev/null +++ b/gcloud/beta/container/bare-metal/admin-clusters/update @@ -0,0 +1,145 @@ +NAME + gcloud beta container bare-metal admin-clusters update - update an Anthos + on bare metal admin cluster + +SYNOPSIS + gcloud beta container bare-metal admin-clusters update + (ADMIN_CLUSTER : --location=LOCATION) [--async] + [--description=DESCRIPTION] [--enable-application-logs] + [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]] + [--login-user=LOGIN_USER] + [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, + ...]] [--max-pods-per-node=MAX_PODS_PER_NODE] [--validate-only] + [--version=VERSION] + [--api-server-args=[KEY=VALUE,...] + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + --control-plane-node-labels=[KEY=VALUE,...] + --control-plane-node-taints=[KEY=VALUE:EFFECT,...]] + [--no-proxy=[NO_PROXY,...] --uri=URI] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Anthos on bare metal admin cluster. + +EXAMPLES + To update a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container bare-metal admin-clusters update \ + my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster 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 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_bare_metal/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description for the resource. + + Anthos on bare metal cluster operations configuration. + + --enable-application-logs + Whether collection of application logs/metrics should be enabled (in + addition to system logs/metrics). + + Populate one of the network configs. + + Island mode CIDR network configuration. + + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + IPv4 address range for all services in the cluster. + + Anthos on bare metal node access related settings for the admin cluster. + + --login-user=LOGIN_USER + User name used to access node machines. + + Anthos on bare metal cluster maintenance configuration. + + --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] + IPv4 addresses to be placed into maintenance mode. + + Anthos on bare metal admin cluster workload node configuration. + + --max-pods-per-node=MAX_PODS_PER_NODE + Maximum number of pods a node can run. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + --version=VERSION + Anthos cluster on bare metal version for the admin cluster resource. + + Anthos on bare metal cluster control plane configuration. + + --api-server-args=[KEY=VALUE,...] + API Server argument configuration. + + Anthos on bare metal cluster control plane node pool configuration. + + Anthos on bare metal node pool configuration for control plane nodes. + + Anthos on bare metal node configuration for control plane nodes. + + Populate control plane node config. + + At most one of these can be specified: + + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + Control plane node configuration. + + --control-plane-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Anthos on bare metal cluster proxy configuration. + + --no-proxy=[NO_PROXY,...] + List of IPs, hostnames, and domains that should skip the proxy. + + --uri=URI + Address of the proxy server. + +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 bare-metal admin-clusters update + diff --git a/gcloud/beta/container/bare-metal/clusters/create b/gcloud/beta/container/bare-metal/clusters/create new file mode 100644 index 000000000..69a489019 --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/create @@ -0,0 +1,492 @@ +NAME + gcloud beta container bare-metal clusters create - create an Anthos cluster + on bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters create + (CLUSTER : --location=LOCATION) --version=VERSION + (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT) + (--control-plane-load-balancer-port=CONTROL_PLANE_LOAD_BALANCER_PORT + (--control-plane-vip=CONTROL_PLANE_VIP + --ingress-vip=INGRESS_VIP) (--enable-manual-lb + | [--bgp-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] --bgp-asn=BGP_ASN + --bgp-peer-configs=[asn=ASN, + ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + : [--bgp-load-balancer-node-configs=[node-ip=IP, + labels=KEY1=VALUE1;KEY2=VALUE2,...] + : --bgp-load-balancer-node-labels=[KEY=VALUE,...] + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS --disable-bgp-load-balancer-serialize-image-pulls]] | [--metal-lb-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] + : --metal-lb-load-balancer-node-configs=[labels=LABELS], + [node-ip=NODE-IP] + --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] + --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --disable-metal-lb-load-balancer-serialize-image-pulls + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS])) + ((((--control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + : --control-plane-node-labels=[KEY=VALUE,...] + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + --disable-control-plane-serialize-image-pulls))) + : --api-server-args=[KEY=VALUE,...]) + ((--lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH + --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS) ((--lvp-share-path=LVP_SHARE_PATH --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS) : --shared-path-pv-count=SHARED_PATH_PV_COUNT)) + [--admin-users=ADMIN_USERS] [--annotations=[KEY=VALUE,...]] [--async] + [--description=DESCRIPTION] [--enable-application-logs] + [--login-user=LOGIN_USER] + [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, + ...]] [--validate-only] + [--container-runtime=CONTAINER_RUNTIME + --max-pods-per-node=MAX_PODS_PER_NODE] + [[(--island-mode-pod-address-cidr-blocks=POD_ADDRESS,[POD_ADDRESS,...] + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...]) + : --enable-advanced-networking + --enable-multi-nic-config --enable-sr-iov-config]] + [--uri=URI : --no-proxy=[NO_PROXY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Anthos cluster on bare metal. + +EXAMPLES + To create a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container bare-metal clusters create my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +REQUIRED FLAGS + --version=VERSION + Anthos cluster on bare metal version for the user cluster resource. + + Admin cluster membership resource - membership of the admin cluster. + Membership can be the membership ID or the full resource name. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier for + the admin_cluster_membership. To set the admin_cluster_membership + attribute: + ▸ provide the argument --admin-cluster-membership on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION + Google Cloud location for the admin_cluster_membership. To set the + location attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-location on the + command line. + + --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT + Google Cloud project for the admin_cluster_membership. To set the + project attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-project on the + command line. + + Anthos on bare metal cluster load balancer configuration. + + This must be specified. + + Control plane load balancer port configuration. + + This must be specified. + + --control-plane-load-balancer-port=CONTROL_PLANE_LOAD_BALANCER_PORT + Control plane load balancer port configuration. + + VIPs used by the load balancer. + + This must be specified. + + --control-plane-vip=CONTROL_PLANE_VIP + VIP for the Kubernetes API of this cluster. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --ingress-vip=INGRESS_VIP + VIP for ingress traffic into this cluster. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Populate one of the load balancers. + + Exactly one of these must be specified: + + Manual load balancer configuration. + + --enable-manual-lb + ManualLB typed load balancers configuration. + + BGP load balancer configuration. + + --bgp-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + BGP load balancer address pools configurations. + + Examples: + + To specify configurations for two address pools pool1 and pool2, + + $ gcloud beta container bare-metal clusters create example_cluster + --bgp-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --bgp-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-asn=BGP_ASN + BGP autonomous system number (ASN) of the cluster. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-peer-configs=[asn=ASN,ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + List of BGP peers that the cluster will connect to. At least one + peer must be configured for each control plane node. + + Examples: + + To specify configurations for two peers of BGP autonomous system + number (ASN) 10000 and 20000, + + $ gcloud beta container bare-metal clusters create example_cluster + --bgp-peer-configs 'asn=10000,ip=192.168.1.1,control-plane-nodes=192.168.1.2;192.168.1.3' + --bgp-peer-configs 'asn=20000,ip=192.168.2.1,control-plane-nodes=192.168.2.2;192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-load-balancer-node-configs=[node-ip=IP,labels=KEY1=VALUE1;KEY2=VALUE2,...] + BGP load balancer data plane node configurations. + + Examples: + + To specify configurations for two nodes of IP 192.168.0.1 and + 192.168.1.1, + + $ gcloud beta container bare-metal clusters create example_cluster + --bgp-load-balancer-node-configs 'node-ip=192.168.0.1,labels=KEY1=VALUE1;KEY2=VALUE2' + --bgp-load-balancer-node-configs 'node-ip=192.168.1.1,labels=KEY3=VALUE3' + + Use quote around the flag value to escape semicolon in the + terminal. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --bgp-load-balancer-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a BGP node pool. + + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to burst + to this number, while still not exceeding registry_pull_qps. + + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + --disable-bgp-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + + MetalLB load balancer configuration. + + MetalLB address pools configuration. + + Exactly one of these must be specified: + + --metal-lb-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + MetalLB load balancer configurations. + + Examples: + + To specify MetalLB load balancer configurations for two address + pools pool1 and pool2, + + $ gcloud beta container bare-metal clusters create example_cluster + --metal-lb-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --metal-lb-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + Anthos on bare metal node pool configuration for MetalLB load + balancer nodes. + + MetalLB Node Pool configuration. + + Populate MetalLB load balancer node config. + + At most one of these can be specified: + + --metal-lb-load-balancer-node-configs=[labels=LABELS],[node-ip=NODE-IP] + MetalLB load balancer node configuration. + + --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a MetalLB node pool. + + --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every node in a MetalLB node pool. + + Modifiable kubelet configurations for bare metal machines. + + --disable-metal-lb-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at + a time. + + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + Anthos on bare metal cluster control plane configuration. + + At least one of these must be specified: + + --api-server-args=[KEY=VALUE,...] + API Server argument configuration. + + Anthos on bare metal cluster control plane node pool configuration. + + This must be specified. + + Anthos on bare metal node pool configuration for control plane nodes. + + This must be specified. + + Anthos on bare metal node configuration for control plane nodes. + + This must be specified. + + Populate control plane node config. + + Exactly one of these must be specified: + + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + Control plane node configuration. + + --control-plane-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + --disable-control-plane-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + + Anthos on bare metal cluster storage configuration. + + This must be specified. + + LVP node mounts class and path used by the storage. + + This must be specified. + + --lvp-node-mounts-config-path=LVP_NODE_MOUNTS_CONFIG_PATH + Path for the LVP node mounts class. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --lvp-node-mounts-config-storage-class=LVP_NODE_MOUNTS_CONFIG_STORAGE_CLASS + Storage class for LVP node mounts. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + LVP share configuration. + + At least one of these must be specified: + + --shared-path-pv-count=SHARED_PATH_PV_COUNT + Number of subdirectories to create under path. + + LVP share class and path used by the storage. + + This must be specified. + + --lvp-share-path=LVP_SHARE_PATH + Path for the LVP share class. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --lvp-share-storage-class=LVP_SHARE_STORAGE_CLASS + Storage class for LVP share. + + This flag argument must be specified if any of the other + arguments in this group are specified. + +OPTIONAL FLAGS + Anthos on bare metal cluster security configuration. + + User cluster authorization configurations to bootstrap onto the admin + cluster + + --admin-users=ADMIN_USERS + Users that will be granted the cluster-admin role on the cluster, + providing full access to the cluster. + + --annotations=[KEY=VALUE,...] + Annotations on the Anthos on bare metal resource. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description for the resource. + + Anthos on bare metal cluster operations configuration. + + --enable-application-logs + Whether collection of application logs/metrics should be enabled (in + addition to system logs/metrics). + + Anthos on bare metal node access related settings for the user cluster. + + --login-user=LOGIN_USER + User name used to access node machines. + + Anthos on bare metal cluster maintenance configuration. + + --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] + IPv4 addresses to be placed into maintenance mode. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + Anthos on bare metal cluster workload node configuration. + + --container-runtime=CONTAINER_RUNTIME + Container runtime which will be used in the bare metal user cluster. + + --max-pods-per-node=MAX_PODS_PER_NODE + Maximum number of pods a node can run. + + Anthos on bare metal cluster network configurations. + + --enable-advanced-networking + Enables the use of advanced Anthos networking features, such as + Bundled Load Balancing with BGP or the egress NAT gateway. + + Multiple networking interfaces cluster configurations. + + --enable-multi-nic-config + If set, enable multiple network interfaces for your pods. + + SR-IOV networking operator configurations. + + --enable-sr-iov-config + If set, install the SR-IOV operator. + + Populate one of the network configs. + + This must be specified. + + Island mode CIDR network configuration. + + --island-mode-pod-address-cidr-blocks=POD_ADDRESS,[POD_ADDRESS,...] + IPv4 address range for all pods in the cluster. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + IPv4 address range for all services in the cluster. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + Anthos on bare metal cluster proxy configuration. + + --uri=URI + Address of the proxy server. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --no-proxy=[NO_PROXY,...] + List of IPs, hostnames, and domains that should skip the proxy. + +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 bare-metal clusters create + diff --git a/gcloud/beta/container/bare-metal/clusters/delete b/gcloud/beta/container/bare-metal/clusters/delete new file mode 100644 index 000000000..684c0b46b --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/delete @@ -0,0 +1,80 @@ +NAME + gcloud beta container bare-metal clusters delete - delete an Anthos cluster + on bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters delete + (CLUSTER : --location=LOCATION) [--allow-missing] [--async] [--force] + [--ignore-errors] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an Anthos cluster on bare metal. + +EXAMPLES + To delete a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container bare-metal clusters delete my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +FLAGS + --allow-missing + If set, and the Bare Metal cluster is not found, the request will + succeed but no action will be taken. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + If set, the operation will also apply to the child node pools. This + flag is required if the cluster has any associated node pools. + + --ignore-errors + If set, the deletion of a bare metal user cluster resource will succeed + even if errors occur during deletion. + + --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 bare-metal clusters delete + diff --git a/gcloud/beta/container/bare-metal/clusters/describe b/gcloud/beta/container/bare-metal/clusters/describe new file mode 100644 index 000000000..1ceace246 --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/describe @@ -0,0 +1,58 @@ +NAME + gcloud beta container bare-metal clusters describe - describe an Anthos + cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters describe + (CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Anthos cluster on bare metal. + +EXAMPLES + To describe a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container bare-metal clusters describe my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal clusters describe + diff --git a/gcloud/beta/container/bare-metal/clusters/enroll b/gcloud/beta/container/bare-metal/clusters/enroll new file mode 100644 index 000000000..4fd3f6632 --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/enroll @@ -0,0 +1,105 @@ +NAME + gcloud beta container bare-metal clusters enroll - enroll an Anthos cluster + on bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters enroll + (CLUSTER : --location=LOCATION) + (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT) + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enroll an Anthos cluster on bare metal. + +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud beta container bare-metal clusters enroll my-cluster \ + --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + +POSITIONAL ARGUMENTS + Cluster resource - cluster to enroll 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +REQUIRED FLAGS + Admin cluster membership resource - membership of the admin cluster. + Membership can be the membership ID or the full resource name. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier for + the admin_cluster_membership. To set the admin_cluster_membership + attribute: + ▸ provide the argument --admin-cluster-membership on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION + Google Cloud location for the admin_cluster_membership. To set the + location attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-location on the + command line. + + --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT + Google Cloud project for the admin_cluster_membership. To set the + project attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-project on the + command line. + +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. This + variant is also available: + + $ gcloud alpha container bare-metal clusters enroll + diff --git a/gcloud/beta/container/bare-metal/clusters/help b/gcloud/beta/container/bare-metal/clusters/help new file mode 100644 index 000000000..02dff61b9 --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/help @@ -0,0 +1,46 @@ +NAME + gcloud beta container bare-metal clusters - create and manage Anthos + clusters on bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage Anthos clusters on bare metal. + +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 an Anthos cluster on bare metal. + + delete + (BETA) Delete an Anthos cluster on bare metal. + + describe + (BETA) Describe an Anthos cluster on bare metal. + + enroll + (BETA) Enroll an Anthos cluster on bare metal. + + list + (BETA) List Anthos clusters on bare metal. + + query-version-config + (BETA) Query versions for creating or upgrading an Anthos on bare metal + user cluster. + + update + (BETA) Update an Anthos cluster on bare metal. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container bare-metal clusters + diff --git a/gcloud/beta/container/bare-metal/clusters/list b/gcloud/beta/container/bare-metal/clusters/list new file mode 100644 index 000000000..d80bb7dd1 --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/list @@ -0,0 +1,80 @@ +NAME + gcloud beta container bare-metal clusters list - list Anthos clusters on + bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Anthos clusters on bare metal. + +EXAMPLES + To lists all clusters managed in location us-west1, run: + + $ gcloud beta container bare-metal clusters list --location=us-west1 + +FLAGS + Location resource - Google Cloud location to list. This represents a Cloud + resource. (NOTE) Some attributes are not given arguments in this group but + can be set in other ways. To set the project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_bare_metal/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal clusters list + diff --git a/gcloud/beta/container/bare-metal/clusters/query-version-config b/gcloud/beta/container/bare-metal/clusters/query-version-config new file mode 100644 index 000000000..2dcfddc2b --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/query-version-config @@ -0,0 +1,128 @@ +NAME + gcloud beta container bare-metal clusters query-version-config - query + versions for creating or upgrading an Anthos on bare metal user cluster + +SYNOPSIS + gcloud beta container bare-metal clusters query-version-config + [--location=LOCATION] + [--cluster=CLUSTER + | [--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global" --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Query versions for creating or upgrading an Anthos on bare metal + user cluster. + +EXAMPLES + To query all available versions in location us-west1, run: + + $ gcloud beta container bare-metal clusters query-version-config \ + --location=us-west1 + + To query versions for creating a cluster with an admin cluster membership + named my-admin-cluster-membership managed in project + my-admin-cluster-project and location us-west, run: + + $ gcloud beta container bare-metal clusters query-version-config \ + --location=us-west1 \ + --admin-cluster-membership=my-admin-cluster-membership \ + --admin-cluster-membership-project=my-admin-cluster-project + + To query versions for upgrading a user cluster named my-user-cluster in + location us-west1, run: + + $ gcloud beta container bare-metal clusters query-version-config \ + --location=us-west1 --cluster=my-user-cluster + +FLAGS + Location resource - Google Cloud location to query versions. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_bare_metal/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + + Use cases for querying versions. + + At most one of these can be specified: + + Upgrade an Anthos on bare metal user cluster use case. + + Cluster resource - Cluster to query versions for upgrade. 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 --cluster 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 --cluster on the command line with a fully + specified name; + ▫ provide the argument --location on the command line; + ▫ set the property container_bare_metal/location. + + --cluster=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. + + Create an Anthos on bare metal user cluster use case. + + Admin cluster membership resource - Membership of the admin cluster to + query versions for create. Membership can be the membership ID or the + full resource name. The arguments in this group can be used to specify + the attributes of this resource. + + --admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier + for the admin_cluster_membership. To set the + admin_cluster_membership attribute: + ◇ provide the argument --admin-cluster-membership on the + command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global" + Google Cloud location for the admin_cluster_membership. To set + the location attribute: + ◇ provide the argument --admin-cluster-membership on the + command line with a fully specified name; + ◇ provide the argument --admin-cluster-membership-location on + the command line. + + --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT + Project ID of the Google Cloud project for the + admin_cluster_membership. To set the project attribute: + ◇ provide the argument --admin-cluster-membership on the + command line with a fully specified name; + ◇ provide the argument --admin-cluster-membership-project on + the command line; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + +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 bare-metal clusters query-version-config + diff --git a/gcloud/beta/container/bare-metal/clusters/update b/gcloud/beta/container/bare-metal/clusters/update new file mode 100644 index 000000000..b42721313 --- /dev/null +++ b/gcloud/beta/container/bare-metal/clusters/update @@ -0,0 +1,338 @@ +NAME + gcloud beta container bare-metal clusters update - update an Anthos cluster + on bare metal + +SYNOPSIS + gcloud beta container bare-metal clusters update + (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS] + [--allow-missing] [--async] [--description=DESCRIPTION] + [--enable-application-logs] [--login-user=LOGIN_USER] + [--maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS, + ...]] [--validate-only] [--version=VERSION] + [--api-server-args=[KEY=VALUE,...] + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + --control-plane-node-labels=[KEY=VALUE,...] + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + --disable-control-plane-serialize-image-pulls + | --enable-control-plane-serialize-image-pulls] + [--bgp-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] --bgp-asn=BGP_ASN + --bgp-peer-configs=[asn=ASN, + ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + --bgp-load-balancer-node-configs=[node-ip=IP, + labels=KEY1=VALUE1;KEY2=VALUE2,...] + --bgp-load-balancer-node-labels=[KEY=VALUE,...] + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS --disable-bgp-load-balancer-serialize-image-pulls | --enable-bgp-load-balancer-serialize-image-pulls | --metal-lb-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] + --metal-lb-load-balancer-node-configs=[labels=LABELS], + [node-ip=NODE-IP] + --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] + --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS --disable-metal-lb-load-balancer-serialize-image-pulls | --enable-metal-lb-load-balancer-serialize-image-pulls] + [--island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + --disable-sr-iov-config | --enable-sr-iov-config] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Anthos cluster on bare metal. + +EXAMPLES + To update a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container bare-metal clusters update my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +FLAGS + Anthos on bare metal cluster security configuration. + + User cluster authorization configurations to bootstrap onto the admin + cluster + + --admin-users=ADMIN_USERS + Users that will be granted the cluster-admin role on the cluster, + providing full access to the cluster. + + --allow-missing + If set, and the Anthos cluster on bare metal is not found, the update + request will try to create a new cluster with the provided + configuration. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description for the resource. + + Anthos on bare metal cluster operations configuration. + + --enable-application-logs + Whether collection of application logs/metrics should be enabled (in + addition to system logs/metrics). + + Anthos on bare metal node access related settings for the user cluster. + + --login-user=LOGIN_USER + User name used to access node machines. + + Anthos on bare metal cluster maintenance configuration. + + --maintenance-address-cidr-blocks=[MAINTENANCE_ADDRESS_CIDR_BLOCKS,...] + IPv4 addresses to be placed into maintenance mode. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + --version=VERSION + Anthos cluster on bare metal version for the user cluster resource. + + Anthos on bare metal cluster control plane configuration. + + --api-server-args=[KEY=VALUE,...] + API Server argument configuration. + + Anthos on bare metal cluster control plane node pool configuration. + + Anthos on bare metal node pool configuration for control plane nodes. + + Anthos on bare metal node configuration for control plane nodes. + + Populate control plane node config. + + At most one of these can be specified: + + --control-plane-node-configs=[labels=LABELS],[node-ip=NODE-IP] + Control plane node configuration. + + --control-plane-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --control-plane-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --control-plane-registry-burst=CONTROL_PLANE_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --control-plane-registry-pull-qps=CONTROL_PLANE_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + At most one of these can be specified: + + --disable-control-plane-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at + a time. + + --enable-control-plane-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a + time. + + Anthos on bare metal cluster load balancer configuration. + + Populate one of the load balancers. + + At most one of these can be specified: + + BGP load balancer configuration. + + --bgp-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + BGP load balancer address pools configurations. + + Examples: + + To specify configurations for two address pools pool1 and pool2, + + $ gcloud beta container bare-metal clusters update example_cluster + --bgp-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --bgp-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + --bgp-asn=BGP_ASN + BGP autonomous system number (ASN) of the cluster. + + --bgp-peer-configs=[asn=ASN,ip=IP,control-plane-nodes=NODE_IP_1;NODE_IP_2,...] + List of BGP peers that the cluster will connect to. At least one + peer must be configured for each control plane node. + + Examples: + + To specify configurations for two peers of BGP autonomous system + number (ASN) 10000 and 20000, + + $ gcloud beta container bare-metal clusters update example_cluster + --bgp-peer-configs 'asn=10000,ip=192.168.1.1,control-plane-nodes=192.168.1.2;192.168.1.3' + --bgp-peer-configs 'asn=20000,ip=192.168.2.1,control-plane-nodes=192.168.2.2;192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + --bgp-load-balancer-node-configs=[node-ip=IP,labels=KEY1=VALUE1;KEY2=VALUE2,...] + BGP load balancer data plane node configurations. + + Examples: + + To specify configurations for two nodes of IP 192.168.0.1 and + 192.168.1.1, + + $ gcloud beta container bare-metal clusters update example_cluster + --bgp-load-balancer-node-configs 'node-ip=192.168.0.1,labels=KEY1=VALUE1;KEY2=VALUE2' + --bgp-load-balancer-node-configs 'node-ip=192.168.1.1,labels=KEY3=VALUE3' + + Use quote around the flag value to escape semicolon in the + terminal. + + --bgp-load-balancer-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a BGP node pool. + + --bgp-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --bgp-load-balancer-registry-burst=BGP_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to burst + to this number, while still not exceeding registry_pull_qps. + + --bgp-load-balancer-registry-pull-qps=BGP_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + At most one of these can be specified: + + --disable-bgp-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + + --enable-bgp-load-balancer-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a time. + + MetalLB load balancer configuration. + + MetalLB address pools configuration. + + At most one of these can be specified: + + --metal-lb-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + MetalLB load balancer configurations. + + Examples: + + To specify MetalLB load balancer configurations for two address + pools pool1 and pool2, + + $ gcloud beta container bare-metal clusters update example_cluster + --metal-lb-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --metal-lb-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + Anthos on bare metal node pool configuration for MetalLB load + balancer nodes. + + MetalLB Node Pool configuration. + + Populate MetalLB load balancer node config. + + At most one of these can be specified: + + --metal-lb-load-balancer-node-configs=[labels=LABELS],[node-ip=NODE-IP] + MetalLB load balancer node configuration. + + --metal-lb-load-balancer-node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a MetalLB node pool. + + --metal-lb-load-balancer-node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every node in a MetalLB node pool. + + Modifiable kubelet configurations for bare metal machines. + + --metal-lb-load-balancer-registry-burst=METAL_LB_LOAD_BALANCER_REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to + burst to this number, while still not exceeding + registry_pull_qps. + + --metal-lb-load-balancer-registry-pull-qps=METAL_LB_LOAD_BALANCER_REGISTRY_PULL_QPS + Limit of registry pulls per second. + + At most one of these can be specified: + + --disable-metal-lb-load-balancer-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images + at a time. + + --enable-metal-lb-load-balancer-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a + time. + + Anthos on bare metal cluster network configurations. + + Populate one of the network configs. + + Island mode CIDR network configuration. + + --island-mode-service-address-cidr-blocks=SERVICE_ADDRESS,[...] + IPv4 address range for all services in the cluster. + + SR-IOV networking operator configurations. + + At most one of these can be specified: + + --disable-sr-iov-config + If set, the SR-IOV operator won't be installed. + + --enable-sr-iov-config + If set, install the SR-IOV operator. + +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 bare-metal clusters update + diff --git a/gcloud/beta/container/bare-metal/help b/gcloud/beta/container/bare-metal/help new file mode 100644 index 000000000..f7eba6258 --- /dev/null +++ b/gcloud/beta/container/bare-metal/help @@ -0,0 +1,37 @@ +NAME + gcloud beta container bare-metal - deploy and manage Anthos clusters on + bare metal for running containers + +SYNOPSIS + gcloud beta container bare-metal GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deploy and manage Anthos clusters on bare metal for running + containers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + admin-clusters + (BETA) Create and manage admin clusters in Anthos on bare metal. + + clusters + (BETA) Create and manage Anthos clusters on bare metal. + + node-pools + (BETA) Create and manage node pools in an Anthos cluster on bare metal. + + operations + (BETA) Manage Anthos on bare metal long running operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container bare-metal + diff --git a/gcloud/beta/container/bare-metal/node-pools/create b/gcloud/beta/container/bare-metal/node-pools/create new file mode 100644 index 000000000..a9d3a3255 --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/create @@ -0,0 +1,117 @@ +NAME + gcloud beta container bare-metal node-pools create - create a node pool in + an Anthos cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools create + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + (--node-configs=[labels=LABELS],[node-ip=NODE-IP] + : --node-labels=[KEY=VALUE,...] --node-taints=[KEY=VALUE:EFFECT,...] + --disable-serialize-image-pulls --registry-burst=REGISTRY_BURST + --registry-pull-qps=REGISTRY_PULL_QPS) + [--annotations=[KEY=VALUE,...]] [--async] [--display-name=DISPLAY_NAME] + [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a node pool in an Anthos cluster on bare metal. + +EXAMPLES + To create a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container bare-metal node-pools create my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +REQUIRED FLAGS + Anthos on bare metal node pool configuration. + + This must be specified. + + Populate Bare Metal Node Pool node config. + + Exactly one of these must be specified: + + --node-configs=[labels=LABELS],[node-ip=NODE-IP] + Bare Metal Node Pool node configuration. + + --node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --disable-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a time. + + --registry-burst=REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to burst to + this number, while still not exceeding registry_pull_qps. + + --registry-pull-qps=REGISTRY_PULL_QPS + Limit of registry pulls per second. + +OPTIONAL FLAGS + --annotations=[KEY=VALUE,...] + Annotations on the node pool. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name for the resource. + + --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 bare-metal node-pools create + diff --git a/gcloud/beta/container/bare-metal/node-pools/delete b/gcloud/beta/container/bare-metal/node-pools/delete new file mode 100644 index 000000000..c18fe1c73 --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/delete @@ -0,0 +1,84 @@ +NAME + gcloud beta container bare-metal node-pools delete - delete a node pool in + an Anthos cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools delete + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--allow-missing] + [--async] [--ignore-errors] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a node pool in an Anthos cluster on bare metal. + +EXAMPLES + To delete a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container bare-metal node-pools delete my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +FLAGS + --allow-missing + If set, and the Bare Metal Node Pool is not found, the request will + succeed but no action will be taken. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ignore-errors + If set, the deletion of a Bare Metal Node Pool resource will succeed + even if errors occur during deletion. + + --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 bare-metal node-pools delete + diff --git a/gcloud/beta/container/bare-metal/node-pools/describe b/gcloud/beta/container/bare-metal/node-pools/describe new file mode 100644 index 000000000..8a9a98743 --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta container bare-metal node-pools describe - describe a node pool + in an Anthos cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools describe + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a node pool in an Anthos cluster on bare metal. + +EXAMPLES + To describe a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container bare-metal node-pools describe \ + my-node-pool --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal node-pools describe + diff --git a/gcloud/beta/container/bare-metal/node-pools/enroll b/gcloud/beta/container/bare-metal/node-pools/enroll new file mode 100644 index 000000000..9fbd58874 --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/enroll @@ -0,0 +1,76 @@ +NAME + gcloud beta container bare-metal node-pools enroll - enroll a node pool of + a user cluster in Anthos on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools enroll + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enroll a node pool of a user cluster in Anthos on bare metal. + +EXAMPLES + To enroll a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container bare-metal node-pools enroll my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool to enroll 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +FLAGS + --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 bare-metal node-pools enroll + diff --git a/gcloud/beta/container/bare-metal/node-pools/help b/gcloud/beta/container/bare-metal/node-pools/help new file mode 100644 index 000000000..c7087523b --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/help @@ -0,0 +1,42 @@ +NAME + gcloud beta container bare-metal node-pools - create and manage node pools + in an Anthos cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage node pools in an Anthos cluster on bare metal. + +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 node pool in an Anthos cluster on bare metal. + + delete + (BETA) Delete a node pool in an Anthos cluster on bare metal. + + describe + (BETA) Describe a node pool in an Anthos cluster on bare metal. + + enroll + (BETA) Enroll a node pool of a user cluster in Anthos on bare metal. + + list + (BETA) List node pools in an Anthos cluster on bare metal. + + update + (BETA) Update a node pool in an Anthos cluster on bare metal. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container bare-metal node-pools + diff --git a/gcloud/beta/container/bare-metal/node-pools/list b/gcloud/beta/container/bare-metal/node-pools/list new file mode 100644 index 000000000..78c865682 --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/list @@ -0,0 +1,93 @@ +NAME + gcloud beta container bare-metal node-pools list - list node pools in an + Anthos cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools list + (--cluster=CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List node pools in an Anthos cluster on bare metal. + +EXAMPLES + To list all node pools in a cluster named my-cluster managed in location + us-west1, run: + + $ gcloud beta container bare-metal node-pools list \ + --cluster=my-cluster --location=us-west1 + +REQUIRED FLAGS + Cluster resource - cluster to list 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=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 flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal node-pools list + diff --git a/gcloud/beta/container/bare-metal/node-pools/update b/gcloud/beta/container/bare-metal/node-pools/update new file mode 100644 index 000000000..74c292f6c --- /dev/null +++ b/gcloud/beta/container/bare-metal/node-pools/update @@ -0,0 +1,122 @@ +NAME + gcloud beta container bare-metal node-pools update - update a node pool in + an Anthos cluster on bare metal + +SYNOPSIS + gcloud beta container bare-metal node-pools update + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--allow-missing] + [--async] [--display-name=DISPLAY_NAME] [--validate-only] + [--node-configs=[labels=LABELS],[node-ip=NODE-IP] + --node-labels=[KEY=VALUE,...] --node-taints=[KEY=VALUE:EFFECT,...] + --registry-burst=REGISTRY_BURST + --registry-pull-qps=REGISTRY_PULL_QPS --disable-serialize-image-pulls + | --enable-serialize-image-pulls] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a node pool in an Anthos cluster on bare metal. + +EXAMPLES + To update a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container bare-metal node-pools update my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +FLAGS + --allow-missing + If set, and the Anthos cluster on bare metal is not found, the update + request will try to create a new cluster with the provided + configuration. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name for the resource. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + Anthos on bare metal node pool configuration. + + Populate Bare Metal Node Pool node config. + + At most one of these can be specified: + + --node-configs=[labels=LABELS],[node-ip=NODE-IP] + Bare Metal Node Pool node configuration. + + --node-labels=[KEY=VALUE,...] + Labels assigned to nodes of a node pool. + + --node-taints=[KEY=VALUE:EFFECT,...] + Node taint applied to every Kubernetes node in a node pool. + + Modifiable kubelet configurations for bare metal machines. + + --registry-burst=REGISTRY_BURST + Maximum size of bursty pulls, temporarily allow pulls to burst to + this number, while still not exceeding registry_pull_qps. + + --registry-pull-qps=REGISTRY_PULL_QPS + Limit of registry pulls per second. + + At most one of these can be specified: + + --disable-serialize-image-pulls + If set, prevent the Kubelet from pulling multiple images at a + time. + + --enable-serialize-image-pulls + If set, enable the Kubelet to pull multiple images at a time. + +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 bare-metal node-pools update + diff --git a/gcloud/beta/container/bare-metal/operations/describe b/gcloud/beta/container/bare-metal/operations/describe new file mode 100644 index 000000000..abe83d762 --- /dev/null +++ b/gcloud/beta/container/bare-metal/operations/describe @@ -0,0 +1,59 @@ +NAME + gcloud beta container bare-metal operations describe - describe an + operation + +SYNOPSIS + gcloud beta container bare-metal operations describe + (OPERATION_ID : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an operation. + +EXAMPLES + To describe an operation in location us-west1, run: + + $ gcloud beta container bare-metal operations describe \ + OPERATION_ID --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation 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 operation_id 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. + + OPERATION_ID + ID of the operation or fully qualified identifier for the operation. + To set the name attribute: + ▸ provide the argument operation_id 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 operation. To set the location + attribute: + ▸ provide the argument operation_id on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal operations describe + diff --git a/gcloud/beta/container/bare-metal/operations/help b/gcloud/beta/container/bare-metal/operations/help new file mode 100644 index 000000000..2ea65e23f --- /dev/null +++ b/gcloud/beta/container/bare-metal/operations/help @@ -0,0 +1,33 @@ +NAME + gcloud beta container bare-metal operations - manage Anthos on bare metal + long running operations + +SYNOPSIS + gcloud beta container bare-metal operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Anthos on bare metal long running operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe an operation. + + list + (BETA) List operations. + + wait + (BETA) Poll an operation for completion. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container bare-metal operations + diff --git a/gcloud/beta/container/bare-metal/operations/list b/gcloud/beta/container/bare-metal/operations/list new file mode 100644 index 000000000..6e2264f30 --- /dev/null +++ b/gcloud/beta/container/bare-metal/operations/list @@ -0,0 +1,81 @@ +NAME + gcloud beta container bare-metal operations list - list operations + +SYNOPSIS + gcloud beta container bare-metal operations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List operations. + +EXAMPLES + To list all operations in location us-west1, run: + + $ gcloud beta container bare-metal operations list \ + --location=us-west1 + +FLAGS + Location resource - Google Cloud location to list operations. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_bare_metal/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal operations list + diff --git a/gcloud/beta/container/bare-metal/operations/wait b/gcloud/beta/container/bare-metal/operations/wait new file mode 100644 index 000000000..42aa89fa2 --- /dev/null +++ b/gcloud/beta/container/bare-metal/operations/wait @@ -0,0 +1,59 @@ +NAME + gcloud beta container bare-metal operations wait - poll an operation for + completion + +SYNOPSIS + gcloud beta container bare-metal operations wait + (OPERATION_ID : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Poll an operation for completion. + +EXAMPLES + To wait for an operation in location us-west1 to complete, run: + + $ gcloud beta container bare-metal operations wait OPERATION_ID \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation to wait for completion. 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 operation_id 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. + + OPERATION_ID + ID of the operation or fully qualified identifier for the operation. + To set the name attribute: + ▸ provide the argument operation_id 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 operation. To set the location + attribute: + ▸ provide the argument operation_id on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_bare_metal/location. + +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 bare-metal operations wait + diff --git a/gcloud/beta/container/clusters/create b/gcloud/beta/container/clusters/create index 7717160a9..257fc741e 100644 --- a/gcloud/beta/container/clusters/create +++ b/gcloud/beta/container/clusters/create @@ -1010,12 +1010,16 @@ FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal to - 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 and + less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/beta/container/help b/gcloud/beta/container/help index 7ba8c5bb7..2e3377d21 100644 --- a/gcloud/beta/container/help +++ b/gcloud/beta/container/help @@ -19,6 +19,10 @@ GROUPS backup-restore (BETA) Backup for GKE Services. + bare-metal + (BETA) Deploy and manage Anthos clusters on bare metal for running + containers. + binauthz (BETA) Manage attestations for Binary Authorization on Google Cloud Platform. @@ -47,6 +51,10 @@ GROUPS subnets (BETA) Manage subnets to be used by Google Kubernetes Engine clusters. + vmware + (BETA) Deploy and manage Anthos clusters on VMware for running + containers. + COMMANDS COMMAND is one of the following: diff --git a/gcloud/beta/container/node-pools/create b/gcloud/beta/container/node-pools/create index b4f86fc3a..21a8193bf 100644 --- a/gcloud/beta/container/node-pools/create +++ b/gcloud/beta/container/node-pools/create @@ -507,12 +507,16 @@ FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal to - 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 and + less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/beta/container/node-pools/update b/gcloud/beta/container/node-pools/update index 7ed8dca04..b61c455dc 100644 --- a/gcloud/beta/container/node-pools/update +++ b/gcloud/beta/container/node-pools/update @@ -159,12 +159,16 @@ REQUIRED FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal - to 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 + and less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/beta/container/vmware/admin-clusters/describe b/gcloud/beta/container/vmware/admin-clusters/describe new file mode 100644 index 000000000..78ef4fead --- /dev/null +++ b/gcloud/beta/container/vmware/admin-clusters/describe @@ -0,0 +1,60 @@ +NAME + gcloud beta container vmware admin-clusters describe - describe an Anthos + on VMware admin cluster + +SYNOPSIS + gcloud beta container vmware admin-clusters describe + (ADMIN_CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Anthos on VMware admin cluster. + +EXAMPLES + To describe an admin cluster named my-cluster managed in location us-west1, + run: + + $ gcloud beta container vmware admin-clusters describe my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster 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 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. + +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 describe + diff --git a/gcloud/beta/container/vmware/admin-clusters/enroll b/gcloud/beta/container/vmware/admin-clusters/enroll new file mode 100644 index 000000000..379b90f88 --- /dev/null +++ b/gcloud/beta/container/vmware/admin-clusters/enroll @@ -0,0 +1,103 @@ +NAME + gcloud beta container vmware admin-clusters enroll - enroll an Anthos on + VMware admin cluster + +SYNOPSIS + gcloud beta container vmware admin-clusters enroll + (ADMIN_CLUSTER : --location=LOCATION) + (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global") + [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enroll an Anthos on VMware admin cluster. + +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud beta container vmware admin-clusters enroll my-cluster \ + --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster to enroll 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. + +REQUIRED FLAGS + Admin cluster membership resource - membership of the admin cluster. + Membership can be the membership ID or the full resource name. 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-membership 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-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier for + the admin_cluster_membership. To set the admin_cluster_membership + attribute: + ▸ provide the argument --admin-cluster-membership on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global" + Google Cloud location for the admin_cluster_membership. To set the + location attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-location on the + command line. + +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. This + variant is also available: + + $ gcloud alpha container vmware admin-clusters enroll + diff --git a/gcloud/beta/container/vmware/admin-clusters/help b/gcloud/beta/container/vmware/admin-clusters/help new file mode 100644 index 000000000..f0474f7e8 --- /dev/null +++ b/gcloud/beta/container/vmware/admin-clusters/help @@ -0,0 +1,36 @@ +NAME + gcloud beta container vmware admin-clusters - create and manage admin + clusters in Anthos on VMware + +SYNOPSIS + gcloud beta container vmware admin-clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage admin clusters in Anthos on VMware. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe an Anthos on VMware admin cluster. + + enroll + (BETA) Enroll an Anthos on VMware admin cluster. + + list + (BETA) List Anthos on VMware admin clusters. + + update + (BETA) Update an Anthos on VMware admin cluster. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware admin-clusters + diff --git a/gcloud/beta/container/vmware/admin-clusters/list b/gcloud/beta/container/vmware/admin-clusters/list new file mode 100644 index 000000000..005c4a771 --- /dev/null +++ b/gcloud/beta/container/vmware/admin-clusters/list @@ -0,0 +1,82 @@ +NAME + gcloud beta container vmware admin-clusters list - list Anthos on VMware + admin clusters + +SYNOPSIS + gcloud beta container vmware admin-clusters list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Anthos on VMware admin clusters. + +EXAMPLES + To list all admin clusters managed in location us-west1, run: + + $ gcloud beta container vmware admin-clusters list \ + --location=us-west1 + +FLAGS + Location resource - Google Cloud location to list Anthos on VMware admin + clusters. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. To set the + project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_vmware/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 vmware admin-clusters list + diff --git a/gcloud/beta/container/vmware/admin-clusters/update b/gcloud/beta/container/vmware/admin-clusters/update new file mode 100644 index 000000000..77cce56ef --- /dev/null +++ b/gcloud/beta/container/vmware/admin-clusters/update @@ -0,0 +1,72 @@ +NAME + gcloud beta container vmware admin-clusters update - update an Anthos on + VMware admin cluster + +SYNOPSIS + gcloud beta container vmware admin-clusters update + (ADMIN_CLUSTER : --location=LOCATION) [--async] + [--required-platform-version=REQUIRED_PLATFORM_VERSION] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Anthos on VMware admin cluster. + +EXAMPLES + To update a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container vmware admin-clusters update my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Admin cluster resource - admin cluster 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 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 + --async + Return immediately, without waiting for the operation in progress to + complete. + + --required-platform-version=REQUIRED_PLATFORM_VERSION + Platform version required for upgrading a user cluster. If the current + platform version is lower than the required version, the platform + version will be updated to the required version. If it is not installed + in the platform, download the required version bundle. + +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 update + diff --git a/gcloud/beta/container/vmware/clusters/create b/gcloud/beta/container/vmware/clusters/create new file mode 100644 index 000000000..b7eae3e93 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/create @@ -0,0 +1,341 @@ +NAME + gcloud beta container vmware clusters create - create an Anthos cluster on + VMware + +SYNOPSIS + gcloud beta container vmware clusters create + (CLUSTER : --location=LOCATION) + (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT) + ((--control-plane-vip=CONTROL_PLANE_VIP --ingress-vip=INGRESS_VIP) + (--metal-lb-config-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL] + | --control-plane-node-port=CONTROL_PLANE_NODE_PORT + --ingress-http-node-port=INGRESS_HTTP_NODE_PORT + --ingress-https-node-port=INGRESS_HTTPS_NODE_PORT + --konnectivity-server-node-port=KONNECTIVITY_SERVER_NODE_PORT + | [--f5-config-address=F5_CONFIG_ADDRESS + --f5-config-partition=F5_CONFIG_PARTITION + : --f5-config-snat-pool=F5_CONFIG_SNAT_POOL])) + (--pod-address-cidr-blocks=POD_ADDRESS + --service-address-cidr-blocks=SERVICE_ADDRESS + : --control-plane-ip-block=[gateway=GATEWAY], + [ips=IPS],[netmask=NETMASK] + --dns-search-domains=[DNS_SEARCH_DOMAINS,...] + --dns-servers=[DNS_SERVERS,...] + --ntp-servers=[NTP_SERVERS,...] --enable-dhcp + | --static-ip-config-ip-blocks=[gateway=GATEWAY], + [ips=IPS],[netmask=NETMASK]) [--admin-users=ADMIN_USERS] + [--annotations=[KEY=VALUE,...]] [--async] [--description=DESCRIPTION] + [--disable-aag-config] [--disable-vsphere-csi] [--enable-auto-repair] + [--enable-control-plane-v2] [--enable-vm-tracking] [--validate-only] + [--version=VERSION] + [--cpus=CPUS --enable-auto-resize --memory=MEMORY --replicas=REPLICAS] + [--enable-advanced-networking --enable-dataplane-v2] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create an Anthos cluster on VMware. + +EXAMPLES + To create a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container vmware clusters create my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +REQUIRED FLAGS + Admin cluster membership resource - membership of the admin cluster. + Membership can be the membership ID or the full resource name. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier for + the admin_cluster_membership. To set the admin_cluster_membership + attribute: + ▸ provide the argument --admin-cluster-membership on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION + Google Cloud location for the admin_cluster_membership. To set the + location attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-location on the + command line. + + --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT + Google Cloud project for the admin_cluster_membership. To set the + project attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-project on the + command line. + + Anthos on VMware cluster load balancer configurations + + This must be specified. + + VIPs used by the load balancer + + This must be specified. + + --control-plane-vip=CONTROL_PLANE_VIP + VIP for the Kubernetes API of this cluster. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + --ingress-vip=INGRESS_VIP + VIP for ingress traffic into this cluster. + + This flag argument must be specified if any of the other arguments + in this group are specified. + + Populate one of the load balancers. + + Exactly one of these must be specified: + + MetalLB Configuration + + At most one of these can be specified: + + --metal-lb-config-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + MetalLB load balancer configurations. + + Examples: + + To specify MetalLB load balancer configurations for two address + pools pool1 and pool2, + + $ gcloud gcloud beta container vmware clusters create + --metal-lb-config-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --metal-lb-config-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + Manual load balancer configuration + + --control-plane-node-port=CONTROL_PLANE_NODE_PORT + NodePort for control plane service. + + --ingress-http-node-port=INGRESS_HTTP_NODE_PORT + NodePort for ingress service's http. + + --ingress-https-node-port=INGRESS_HTTPS_NODE_PORT + NodePort for ingress service's https. + + --konnectivity-server-node-port=KONNECTIVITY_SERVER_NODE_PORT + NodePort for konnectivity service running as a sidecar in each + kube-apiserver pod. + + F5 Big IP Configuration + + --f5-config-address=F5_CONFIG_ADDRESS + F5 Big IP load balancer address. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --f5-config-partition=F5_CONFIG_PARTITION + F5 Big IP load balancer partition. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --f5-config-snat-pool=F5_CONFIG_SNAT_POOL + F5 Big IP load balancer pool name if using SNAT. + + VMware User Cluster network configurations + + This must be specified. + + --pod-address-cidr-blocks=POD_ADDRESS + IPv4 address range for all pods in the cluster. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --service-address-cidr-blocks=SERVICE_ADDRESS + IPv4 address range for all services in the cluster. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + Control plane v2 mode configurations. + + --control-plane-ip-block=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK] + Static IP addresses for the control plane nodes. The number of IP + addresses should match the number of replicas for the control plane + nodes, specified by --replicas. + + To specify the control plane IP block, + + $ gcloud gcloud beta container vmware clusters create + --control-plane-ip-block 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;' + + Common parameters for all hosts irrespective of their IP address + + --dns-search-domains=[DNS_SEARCH_DOMAINS,...] + DNS search domains. + + --dns-servers=[DNS_SERVERS,...] + DNS server IP address. + + --ntp-servers=[NTP_SERVERS,...] + NTP server IP address. + + IP configuration used by the VMware User Cluster + + At most one of these can be specified: + + DHCP configuration group. + + --enable-dhcp + Enable DHCP IP allocation for VMware user clusters. + + Static IP configuration group + + At most one of these can be specified: + + --static-ip-config-ip-blocks=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK] + Static IP configurations. + + Expect an individual IP address, an individual IP address with an + optional hostname, or a CIDR block. + + Example: + + To specify two Static IP blocks, + + $ gcloud gcloud beta container vmware clusters create + --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;192.168.1.2/16' + --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=8.8.8.8;4.4.4.4' + + Use quote around the flag value to escape semicolon in the + terminal. + +OPTIONAL FLAGS + User cluster authorization configurations to bootstrap onto the admin + cluster + + --admin-users=ADMIN_USERS + Users that will be granted the cluster-admin role on the cluster, + providing full access to the cluster. + + --annotations=[KEY=VALUE,...] + Annotations on the VMware user cluster. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description for the resource. + + Anti-affinity group configurations + + --disable-aag-config + If set, spread nodes across at least three physical hosts (requires + at least three hosts). Enabled by default. + + Storage configurations + + --disable-vsphere-csi + If set, vSphere CSI components are not deployed in the VMware User + Cluster. Enabled by default. + + Auto-repair configurations + + --enable-auto-repair + If set, deploy the cluster-health-controller. + + --enable-control-plane-v2 + If set, enable control plane v2. + + --enable-vm-tracking + If set, enable VM tracking. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + --version=VERSION + Anthos Cluster on VMware version for the user cluster resource + + Control plane node configurations + + --cpus=CPUS + Number of CPUs for each admin cluster node that serve as control + planes for this VMware user cluster. (default: 4 CPUs) + + Auto resize configurations + + --enable-auto-resize + Enable controle plane node auto resize. + + --memory=MEMORY + Megabytes of memory for each admin cluster node that serves as a + control plane for this VMware User Cluster (default: 8192 MB memory). + + --replicas=REPLICAS + Number of control plane nodes for this VMware user cluster. (default: + 1 replica). + + Dataplane V2 configurations + + --enable-advanced-networking + If set, enable advanced networking. Requires dataplane_v2_enabled to + be set true. + + --enable-dataplane-v2 + If set, enables Dataplane V2. + +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 clusters create + diff --git a/gcloud/beta/container/vmware/clusters/delete b/gcloud/beta/container/vmware/clusters/delete new file mode 100644 index 000000000..e7c984ba4 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/delete @@ -0,0 +1,80 @@ +NAME + gcloud beta container vmware clusters delete - delete an Anthos cluster on + VMware + +SYNOPSIS + gcloud beta container vmware clusters delete + (CLUSTER : --location=LOCATION) [--allow-missing] [--async] [--force] + [--ignore-errors] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete an Anthos cluster on VMware. + +EXAMPLES + To delete a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container vmware clusters delete my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument 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 Anthos cluster on VMware is not found, the request will + succeed but no action will be taken. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --force + If set, any node pools from the cluster will also be deleted. This flag + is required if the cluster has any associated node pools. + + --ignore-errors + If set, the deletion of a VMware user cluster resource will succeed + even if errors occur during deletion. + + --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 clusters delete + diff --git a/gcloud/beta/container/vmware/clusters/describe b/gcloud/beta/container/vmware/clusters/describe new file mode 100644 index 000000000..e064cf306 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/describe @@ -0,0 +1,58 @@ +NAME + gcloud beta container vmware clusters describe - describe an Anthos cluster + on VMware + +SYNOPSIS + gcloud beta container vmware clusters describe + (CLUSTER : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an Anthos cluster on VMware. + +EXAMPLES + To describe a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container vmware clusters describe my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 clusters describe + diff --git a/gcloud/beta/container/vmware/clusters/enroll b/gcloud/beta/container/vmware/clusters/enroll new file mode 100644 index 000000000..9e3dc665e --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/enroll @@ -0,0 +1,119 @@ +NAME + gcloud beta container vmware clusters enroll - enroll an Anthos cluster on + VMware + +SYNOPSIS + gcloud beta container vmware clusters enroll + (CLUSTER : --location=LOCATION) + (--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT) + [--async] [--local-name=LOCAL_NAME] [--validate-only] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enroll an Anthos cluster on VMware. + +EXAMPLES + To enroll a cluster named my-cluster managed in location us-west1 with + admin cluster membership of + projects/my-project/locations/us-west1/memberships/my-admin-cluster-membership, + run: + + $ gcloud beta container vmware clusters enroll my-cluster \ + --location=us-west1 \ + --admin-cluster-membership=projects/my-project/locations/\ + us-west1/memberships/my-admin-cluster-membership + +POSITIONAL ARGUMENTS + Cluster resource - cluster to enroll 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +REQUIRED FLAGS + Admin cluster membership resource - membership of the admin cluster. + Membership can be the membership ID or the full resource name. The + arguments in this group can be used to specify the attributes of this + resource. + + This must be specified. + + --admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier for + the admin_cluster_membership. To set the admin_cluster_membership + attribute: + ▸ provide the argument --admin-cluster-membership on the command + line. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION + Google Cloud location for the admin_cluster_membership. To set the + location attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-location on the + command line. + + --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT + Google Cloud project for the admin_cluster_membership. To set the + project attribute: + ▸ provide the argument --admin-cluster-membership on the command + line with a fully specified name; + ▸ provide the argument --admin-cluster-membership-project on the + command line. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --local-name=LOCAL_NAME + The object name of the VMware OnPremUserCluster custom resource on the + associated admin cluster. This field is used to support conflicting + resource names when enrolling existing clusters to the API. When not + provided, this field will resolve to the vmware_cluster_id. Otherwise, + it must match the object name of the VMware OnPremUserCluster custom + resource. It is not modifiable outside / beyond the enrollment + operation. + + --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 clusters enroll + diff --git a/gcloud/beta/container/vmware/clusters/help b/gcloud/beta/container/vmware/clusters/help new file mode 100644 index 000000000..87e2da3f5 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/help @@ -0,0 +1,49 @@ +NAME + gcloud beta container vmware clusters - create and manage Anthos clusters + on VMware + +SYNOPSIS + gcloud beta container vmware clusters COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage Anthos clusters on VMware. + +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 an Anthos cluster on VMware. + + delete + (BETA) Delete an Anthos cluster on VMware. + + describe + (BETA) Describe an Anthos cluster on VMware. + + enroll + (BETA) Enroll an Anthos cluster on VMware. + + list + (BETA) List Anthos clusters on VMware. + + query-version-config + (BETA) Query versions for creating or upgrading an Anthos on VMware + user cluster. + + update + (BETA) Update an Anthos cluster on VMware. + + upgrade + (BETA) Centrally upgrade an Anthos cluster on VMware. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware clusters + diff --git a/gcloud/beta/container/vmware/clusters/list b/gcloud/beta/container/vmware/clusters/list new file mode 100644 index 000000000..941bcf2d0 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/list @@ -0,0 +1,80 @@ +NAME + gcloud beta container vmware clusters list - list Anthos clusters on VMware + +SYNOPSIS + gcloud beta container vmware clusters list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List Anthos clusters on VMware. + +EXAMPLES + To lists all clusters managed in location us-west1, run: + + $ gcloud beta container vmware clusters list --location=us-west1 + +FLAGS + Location resource - Google Cloud location to list Anthos on VMware + clusters. This represents a Cloud resource. (NOTE) Some attributes are not + given arguments in this group but can be set in other ways. To set the + project attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_vmware/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 vmware clusters list + diff --git a/gcloud/beta/container/vmware/clusters/query-version-config b/gcloud/beta/container/vmware/clusters/query-version-config new file mode 100644 index 000000000..1188e62cf --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/query-version-config @@ -0,0 +1,128 @@ +NAME + gcloud beta container vmware clusters query-version-config - query versions + for creating or upgrading an Anthos on VMware user cluster + +SYNOPSIS + gcloud beta container vmware clusters query-version-config + [--location=LOCATION] + [--cluster=CLUSTER + | [--admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + : --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global" --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT]] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Query versions for creating or upgrading an Anthos on VMware user + cluster. + +EXAMPLES + To query all available versions in location us-west1, run: + + $ gcloud beta container vmware clusters query-version-config \ + --location=us-west1 + + To query versions for creating a cluster with an admin cluster membership + named my-admin-cluster-membership managed in project + my-admin-cluster-project and location us-west, run: + + $ gcloud beta container vmware clusters query-version-config \ + --location=us-west1 \ + --admin-cluster-membership=my-admin-cluster-membership \ + --admin-cluster-membership-project=my-admin-cluster-project + + To query versions for upgrading a user cluster named my-user-cluster in + location us-west1, run: + + $ gcloud beta container vmware clusters query-version-config \ + --location=us-west1 --cluster=my-user-cluster + +FLAGS + Location resource - Google Cloud location to query versions. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_vmware/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + + Use cases for querying versions. + + At most one of these can be specified: + + Upgrade an Anthos on VMware user cluster use case. + + Cluster resource - Cluster to query versions for upgrade. 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 --cluster 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 --cluster on the command line with a fully + specified name; + ▫ provide the argument --location on the command line; + ▫ set the property container_vmware/location. + + --cluster=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. + + Create an Anthos on VMware user cluster use case. + + Admin cluster membership resource - Membership of the admin cluster to + query versions for create. Membership can be the membership ID or the + full resource name. The arguments in this group can be used to specify + the attributes of this resource. + + --admin-cluster-membership=ADMIN_CLUSTER_MEMBERSHIP + ID of the admin_cluster_membership or fully qualified identifier + for the admin_cluster_membership. To set the + admin_cluster_membership attribute: + ◇ provide the argument --admin-cluster-membership on the + command line. + + This flag argument must be specified if any of the other + arguments in this group are specified. + + --admin-cluster-membership-location=ADMIN_CLUSTER_MEMBERSHIP_LOCATION; default="global" + Google Cloud location for the admin_cluster_membership. To set + the location attribute: + ◇ provide the argument --admin-cluster-membership on the + command line with a fully specified name; + ◇ provide the argument --admin-cluster-membership-location on + the command line. + + --admin-cluster-membership-project=ADMIN_CLUSTER_MEMBERSHIP_PROJECT + Project ID of the Google Cloud project for the + admin_cluster_membership. To set the project attribute: + ◇ provide the argument --admin-cluster-membership on the + command line with a fully specified name; + ◇ provide the argument --admin-cluster-membership-project on + the command line; + ◇ provide the argument --project on the command line; + ◇ set the property core/project. + +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 clusters query-version-config + diff --git a/gcloud/beta/container/vmware/clusters/update b/gcloud/beta/container/vmware/clusters/update new file mode 100644 index 000000000..c81dc5b70 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/update @@ -0,0 +1,202 @@ +NAME + gcloud beta container vmware clusters update - update an Anthos cluster on + VMware + +SYNOPSIS + gcloud beta container vmware clusters update + (CLUSTER : --location=LOCATION) [--admin-users=ADMIN_USERS] [--async] + [--description=DESCRIPTION] + [--metal-lb-config-address-pools=[addresses=ADDRESSES], + [avoid-buggy-ips=AVOID-BUGGY-IPS], + [manual-assign=MANUAL-ASSIGN],[pool=POOL]] + [--static-ip-config-ip-blocks=[gateway=GATEWAY], + [ips=IPS],[netmask=NETMASK]] [--validate-only] [--version=VERSION] + [--add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...] + | --remove-annotations=[KEY1,KEY2,...]] + [--cpus=CPUS --memory=MEMORY --disable-auto-resize + | --enable-auto-resize] [--disable-aag-config | --enable-aag-config] + [--disable-auto-repair | --enable-auto-repair] + [--disable-vsphere-csi | --enable-vsphere-csi] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an Anthos cluster on VMware. + +EXAMPLES + To update a cluster named my-cluster managed in location us-west1, run: + + $ gcloud beta container vmware clusters update my-cluster \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Cluster resource - cluster 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument 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 + User cluster authorization configurations to bootstrap onto the admin + cluster + + --admin-users=ADMIN_USERS + Users that will be granted the cluster-admin role on the cluster, + providing full access to the cluster. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description for the resource. + + Anthos on VMware cluster load balancer configurations + + Populate one of the load balancers. + + MetalLB Configuration + + At most one of these can be specified: + + --metal-lb-config-address-pools=[addresses=ADDRESSES],[avoid-buggy-ips=AVOID-BUGGY-IPS],[manual-assign=MANUAL-ASSIGN],[pool=POOL] + MetalLB load balancer configurations. + + Examples: + + To specify MetalLB load balancer configurations for two address + pools pool1 and pool2, + + $ gcloud gcloud beta container vmware clusters update + --metal-lb-config-address-pools 'pool=pool1,avoid-buggy-ips=True,manual-assign=True,addresses=192.168.1.1/32;192.168.1.2-192.168.1.3' + --metal-lb-config-address-pools 'pool=pool2,avoid-buggy-ips=False,manual-assign=False,addresses=192.168.2.1/32;192.168.2.2-192.168.2.3' + + Use quote around the flag value to escape semicolon in the + terminal. + + VMware User Cluster network configurations + + IP configuration used by the VMware User Cluster + + Static IP configuration group + + At most one of these can be specified: + + --static-ip-config-ip-blocks=[gateway=GATEWAY],[ips=IPS],[netmask=NETMASK] + Static IP configurations. + + Expect an individual IP address, an individual IP address with an + optional hostname, or a CIDR block. + + Example: + + To specify two Static IP blocks, + + $ gcloud gcloud beta container vmware clusters update + --static-ip-config-ip-blocks 'gateway=192.168.0.1,netmask=255.255.255.0,ips=192.168.1.1;0.0.0.0 localhost;192.168.1.2/16' + --static-ip-config-ip-blocks 'gateway=192.168.1.1,netmask=255.255.0.0,ips=8.8.8.8;4.4.4.4' + + Use quote around the flag value to escape semicolon in the + terminal. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + --version=VERSION + Anthos Cluster on VMware version for the user cluster resource + + At most one of these can be specified: + + --add-annotations=[KEY1=VALUE1,KEY2=VALUE2,...] + Add the given key-value pairs to the current annotations, or update + its value if the key already exists. + + --remove-annotations=[KEY1,KEY2,...] + Remove annotations of the given keys. + + Control plane node configurations + + --cpus=CPUS + Number of CPUs for each admin cluster node that serve as control + planes for this VMware user cluster. (default: 4 CPUs) + + --memory=MEMORY + Megabytes of memory for each admin cluster node that serves as a + control plane for this VMware User Cluster (default: 8192 MB memory). + + Auto resize configurations + + At most one of these can be specified: + + --disable-auto-resize + Disable controle plane node auto resize. + + --enable-auto-resize + Enable controle plane node auto resize. + + Anti-affinity group configurations + + At most one of these can be specified: + + --disable-aag-config + If set, spread nodes across at least three physical hosts (requires + at least three hosts). Enabled by default. + + --enable-aag-config + If set, enable anti-affinity group config. + + Auto-repair configurations + + At most one of these can be specified: + + --disable-auto-repair + If set, disables auto repair. + + --enable-auto-repair + If set, deploy the cluster-health-controller. + + Storage configurations + + At most one of these can be specified: + + --disable-vsphere-csi + If set, vSphere CSI components are not deployed in the VMware User + Cluster. Enabled by default. + + --enable-vsphere-csi + If set, vSphere CSI components are deployed in the VMware User + 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. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware clusters update + diff --git a/gcloud/beta/container/vmware/clusters/upgrade b/gcloud/beta/container/vmware/clusters/upgrade new file mode 100644 index 000000000..37918de45 --- /dev/null +++ b/gcloud/beta/container/vmware/clusters/upgrade @@ -0,0 +1,64 @@ +NAME + gcloud beta container vmware clusters upgrade - centrally upgrade an Anthos + cluster on VMware + +SYNOPSIS + gcloud beta container vmware clusters upgrade + (CLUSTER : --location=LOCATION) --version=VERSION + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Centrally upgrade an Anthos cluster on VMware. + +EXAMPLES + To upgrade a cluster named my-cluster managed in location us-west1 to + version 1.13.0-gke.1000, run: + + $ gcloud beta container vmware clusters upgrade my-cluster \ + --location=us-west1 --version=1.13.0-gke.1000 + +POSITIONAL ARGUMENTS + Cluster resource - cluster to upgrade 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. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +REQUIRED FLAGS + --version=VERSION + Anthos Cluster on VMware version for the user cluster resource + +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 clusters upgrade + diff --git a/gcloud/beta/container/vmware/help b/gcloud/beta/container/vmware/help new file mode 100644 index 000000000..9f28065f2 --- /dev/null +++ b/gcloud/beta/container/vmware/help @@ -0,0 +1,36 @@ +NAME + gcloud beta container vmware - deploy and manage Anthos clusters on VMware + for running containers + +SYNOPSIS + gcloud beta container vmware GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deploy and manage Anthos clusters on VMware for running containers. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + admin-clusters + (BETA) Create and manage admin clusters in Anthos on VMware. + + clusters + (BETA) Create and manage Anthos clusters on VMware. + + node-pools + (BETA) Create and manage node pools in an Anthos cluster on VMware. + + operations + (BETA) Manage Anthos on VMware long running operations. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware + diff --git a/gcloud/beta/container/vmware/node-pools/create b/gcloud/beta/container/vmware/node-pools/create new file mode 100644 index 000000000..2a0062a42 --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/create @@ -0,0 +1,145 @@ +NAME + gcloud beta container vmware node-pools create - create a node pool in an + Anthos cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools create + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + (--image-type=IMAGE_TYPE : --boot-disk-size=BOOT_DISK_SIZE --cpus=CPUS + --enable-load-balancer --image=IMAGE --memory=MEMORY + --node-labels=[KEY=VALUE,...] + --node-taints=[KEY=VALUE:EFFECT,...] --replicas=REPLICAS) + [--annotations=[KEY=VALUE,...]] [--async] [--display-name=DISPLAY_NAME] + [--validate-only] + [--max-replicas=MAX_REPLICAS --min-replicas=MIN_REPLICAS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create a node pool in an Anthos cluster on VMware. + +EXAMPLES + To create a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container vmware node-pools create my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +REQUIRED FLAGS + Configuration of the node pool + + This must be specified. + + --image-type=IMAGE_TYPE + OS image type to use on node pool instances. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --boot-disk-size=BOOT_DISK_SIZE + Size of VMware disk to be used during creation in GB. + + --cpus=CPUS + Number of CPUs for each node in the node pool. + + --enable-load-balancer + If set, enable the use of load balancer on the node pool instances. + + --image=IMAGE + OS image name in vCenter. + + --memory=MEMORY + Size of memory for each node in the node pool in MB. + + --node-labels=[KEY=VALUE,...] + Kubernetes labels (key/value pairs) to be applied to each node. + + --node-taints=[KEY=VALUE:EFFECT,...] + Applies the given kubernetes taints on all nodes in the new node + pool, which can be used with tolerations for pod scheduling. + + Examples: + + $ gcloud beta container vmware node-pools create node-pool-1 \ + --cluster=example-cluster \ + --node-taints=key1=val1:NoSchedule,key2=val2:PreferNoSchedule + + --replicas=REPLICAS + Number of replicas to use on node pool instances. + +OPTIONAL FLAGS + --annotations=[KEY=VALUE,...] + Annotations on the node pool. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name for the resource. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + Node pool autoscaling + + --max-replicas=MAX_REPLICAS + Maximum number of replicas in the node pool. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --min-replicas=MIN_REPLICAS + Minimum number of replicas in the node pool. + + This flag argument must be specified if any of the other arguments in + this group are specified. + +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 node-pools create + diff --git a/gcloud/beta/container/vmware/node-pools/delete b/gcloud/beta/container/vmware/node-pools/delete new file mode 100644 index 000000000..78ddd0201 --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/delete @@ -0,0 +1,84 @@ +NAME + gcloud beta container vmware node-pools delete - delete a node pool in an + Anthos cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools delete + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--allow-missing] + [--async] [--ignore-errors] [--validate-only] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Delete a node pool in an Anthos cluster on VMware. + +EXAMPLES + To delete a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container vmware node-pools delete my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool 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 Node Pool is not found, the request will succeed + but no action will be taken. + + --async + Return immediately, without waiting for the operation in progress to + complete. + + --ignore-errors + If set, the deletion of a VMware node pool resource will succeed even + if errors occur during deletion. + + --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 node-pools delete + diff --git a/gcloud/beta/container/vmware/node-pools/describe b/gcloud/beta/container/vmware/node-pools/describe new file mode 100644 index 000000000..4b08c7aca --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/describe @@ -0,0 +1,67 @@ +NAME + gcloud beta container vmware node-pools describe - describe a node pool in + an Anthos cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools describe + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a node pool in an Anthos cluster on VMware. + +EXAMPLES + To describe a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container vmware node-pools describe my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 node-pools describe + diff --git a/gcloud/beta/container/vmware/node-pools/enroll b/gcloud/beta/container/vmware/node-pools/enroll new file mode 100644 index 000000000..ba780aa82 --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/enroll @@ -0,0 +1,72 @@ +NAME + gcloud beta container vmware node-pools enroll - enroll a node pool in an + Anthos cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools enroll + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enroll a node pool in an Anthos cluster on VMware. + +EXAMPLES + To enroll a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container vmware node-pools enroll my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool to enroll 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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. This + variant is also available: + + $ gcloud alpha container vmware node-pools enroll + diff --git a/gcloud/beta/container/vmware/node-pools/help b/gcloud/beta/container/vmware/node-pools/help new file mode 100644 index 000000000..30b02d43a --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/help @@ -0,0 +1,42 @@ +NAME + gcloud beta container vmware node-pools - create and manage node pools in + an Anthos cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Create and manage node pools in an Anthos cluster on VMware. + +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 node pool in an Anthos cluster on VMware. + + delete + (BETA) Delete a node pool in an Anthos cluster on VMware. + + describe + (BETA) Describe a node pool in an Anthos cluster on VMware. + + enroll + (BETA) Enroll a node pool in an Anthos cluster on VMware. + + list + (BETA) List node pools in an Anthos cluster on VMware. + + update + (BETA) Update a node pool in an Anthos cluster on VMware. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware node-pools + diff --git a/gcloud/beta/container/vmware/node-pools/list b/gcloud/beta/container/vmware/node-pools/list new file mode 100644 index 000000000..92f759af6 --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/list @@ -0,0 +1,93 @@ +NAME + gcloud beta container vmware node-pools list - list node pools in an Anthos + cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools list + (--cluster=CLUSTER : --location=LOCATION) [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List node pools in an Anthos cluster on VMware. + +EXAMPLES + To list all node pools in a cluster named my-cluster managed in location + us-west1, run: + + $ gcloud beta container vmware node-pools list \ + --cluster=my-cluster --location=us-west1 + +REQUIRED FLAGS + Cluster resource - cluster to list 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=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 flag argument must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + Google Cloud location for the cluster. To set the location attribute: + ▸ provide the argument --cluster on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 vmware node-pools list + diff --git a/gcloud/beta/container/vmware/node-pools/update b/gcloud/beta/container/vmware/node-pools/update new file mode 100644 index 000000000..0f67350b5 --- /dev/null +++ b/gcloud/beta/container/vmware/node-pools/update @@ -0,0 +1,135 @@ +NAME + gcloud beta container vmware node-pools update - update a node pool in an + Anthos cluster on VMware + +SYNOPSIS + gcloud beta container vmware node-pools update + (NODE_POOL : --cluster=CLUSTER --location=LOCATION) [--async] + [--display-name=DISPLAY_NAME] [--validate-only] + [--boot-disk-size=BOOT_DISK_SIZE --cpus=CPUS --image=IMAGE + --image-type=IMAGE_TYPE --memory=MEMORY --node-labels=[KEY=VALUE,...] + --node-taints=[KEY=VALUE:EFFECT,...] + --replicas=REPLICAS --disable-load-balancer | --enable-load-balancer] + [--max-replicas=MAX_REPLICAS --min-replicas=MIN_REPLICAS] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a node pool in an Anthos cluster on VMware. + +EXAMPLES + To update a node pool named my-node-pool in a cluster named my-cluster + managed in location us-west1, run: + + $ gcloud beta container vmware node-pools update my-node-pool \ + --cluster=my-cluster --location=us-west1 + +POSITIONAL ARGUMENTS + Node pool resource - node pool 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 node_pool 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. + + NODE_POOL + ID of the node_pool or fully qualified identifier for the node_pool. + To set the node_pool attribute: + ▸ provide the argument node_pool on the command line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --cluster=CLUSTER + cluster of the node_pool. To set the cluster attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --cluster on the command line. + + --location=LOCATION + Google Cloud location for the node_pool. To set the location + attribute: + ▸ provide the argument node_pool on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --display-name=DISPLAY_NAME + Display name for the resource. + + --validate-only + If set, only validate the request, but do not actually perform the + operation. + + Configuration of the node pool + + --boot-disk-size=BOOT_DISK_SIZE + Size of VMware disk to be used during creation in GB. + + --cpus=CPUS + Number of CPUs for each node in the node pool. + + --image=IMAGE + OS image name in vCenter. + + --image-type=IMAGE_TYPE + OS image type to use on node pool instances. + + --memory=MEMORY + Size of memory for each node in the node pool in MB. + + --node-labels=[KEY=VALUE,...] + Kubernetes labels (key/value pairs) to be applied to each node. + + --node-taints=[KEY=VALUE:EFFECT,...] + Applies the given kubernetes taints on all nodes in the new node + pool, which can be used with tolerations for pod scheduling. + + Examples: + + $ gcloud beta container vmware node-pools update node-pool-1 \ + --cluster=example-cluster \ + --node-taints=key1=val1:NoSchedule,key2=val2:PreferNoSchedule + + --replicas=REPLICAS + Number of replicas to use on node pool instances. + + At most one of these can be specified: + + --disable-load-balancer + If set, disable the use of load balancer on the node pool + instances. + + --enable-load-balancer + If set, enable the use of load balancer on the node pool instances. + + Node pool autoscaling + + --max-replicas=MAX_REPLICAS + Maximum number of replicas in the node pool. + + --min-replicas=MIN_REPLICAS + Minimum number of replicas in the node pool. + +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 node-pools update + diff --git a/gcloud/beta/container/vmware/operations/describe b/gcloud/beta/container/vmware/operations/describe new file mode 100644 index 000000000..fd13d23c2 --- /dev/null +++ b/gcloud/beta/container/vmware/operations/describe @@ -0,0 +1,58 @@ +NAME + gcloud beta container vmware operations describe - describe an operation + +SYNOPSIS + gcloud beta container vmware operations describe + (OPERATION_ID : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe an operation. + +EXAMPLES + To describe an operation in location us-west1, run: + + $ gcloud beta container vmware operations describe OPERATION_ID \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation 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 operation_id 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. + + OPERATION_ID + ID of the operation or fully qualified identifier for the operation. + To set the name attribute: + ▸ provide the argument operation_id 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 operation. To set the location + attribute: + ▸ provide the argument operation_id on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 operations describe + diff --git a/gcloud/beta/container/vmware/operations/help b/gcloud/beta/container/vmware/operations/help new file mode 100644 index 000000000..a5025ba2c --- /dev/null +++ b/gcloud/beta/container/vmware/operations/help @@ -0,0 +1,33 @@ +NAME + gcloud beta container vmware operations - manage Anthos on VMware long + running operations + +SYNOPSIS + gcloud beta container vmware operations COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Anthos on VMware long running operations. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (BETA) Describe an operation. + + list + (BETA) List operations. + + wait + (BETA) Poll an operation for completion. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container vmware operations + diff --git a/gcloud/beta/container/vmware/operations/list b/gcloud/beta/container/vmware/operations/list new file mode 100644 index 000000000..e264bc809 --- /dev/null +++ b/gcloud/beta/container/vmware/operations/list @@ -0,0 +1,80 @@ +NAME + gcloud beta container vmware operations list - list operations + +SYNOPSIS + gcloud beta container vmware operations list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List operations. + +EXAMPLES + To list all operations in location us-west1, run: + + $ gcloud beta container vmware operations list --location=us-west1 + +FLAGS + Location resource - Google Cloud location to list operations. This + represents a Cloud resource. (NOTE) Some attributes are not given + arguments in this group but can be set in other ways. To set the project + attribute: + ◆ provide the argument --location on the command line with a fully + specified name; + ◆ set the property container_vmware/location with a fully specified + name; + ◆ provide the argument --project on the command line; + ◆ set the property core/project. + + --location=LOCATION + ID of the location or fully qualified identifier for the location. To + set the location attribute: + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 vmware operations list + diff --git a/gcloud/beta/container/vmware/operations/wait b/gcloud/beta/container/vmware/operations/wait new file mode 100644 index 000000000..2ac6c0709 --- /dev/null +++ b/gcloud/beta/container/vmware/operations/wait @@ -0,0 +1,59 @@ +NAME + gcloud beta container vmware operations wait - poll an operation for + completion + +SYNOPSIS + gcloud beta container vmware operations wait + (OPERATION_ID : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Poll an operation for completion. + +EXAMPLES + To wait for an operation in location us-west1 to complete, run: + + $ gcloud beta container vmware operations wait OPERATION_ID \ + --location=us-west1 + +POSITIONAL ARGUMENTS + Operation resource - operation to wait for completion. 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 operation_id 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. + + OPERATION_ID + ID of the operation or fully qualified identifier for the operation. + To set the name attribute: + ▸ provide the argument operation_id 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 operation. To set the location + attribute: + ▸ provide the argument operation_id on the command line with a + fully specified name; + ▸ provide the argument --location on the command line; + ▸ set the property container_vmware/location. + +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 operations wait + diff --git a/gcloud/beta/filestore/instances/revert b/gcloud/beta/filestore/instances/revert index bf076a89b..9bb6fa66e 100644 --- a/gcloud/beta/filestore/instances/revert +++ b/gcloud/beta/filestore/instances/revert @@ -72,5 +72,8 @@ API REFERENCE can be found at: https://cloud.google.com/filestore/ 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 filestore instances revert diff --git a/gcloud/beta/functions/deploy b/gcloud/beta/functions/deploy index 52c5dcb92..59e046c52 100644 --- a/gcloud/beta/functions/deploy +++ b/gcloud/beta/functions/deploy @@ -128,7 +128,9 @@ FLAGS If enabled, this command will use Cloud Functions (Second generation). If disabled with --no-gen2, Cloud Functions (First generation) will be used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/beta/iam/workforce-pools/providers/create-oidc b/gcloud/beta/iam/workforce-pools/providers/create-oidc index 65f52e89e..be6646b31 100644 --- a/gcloud/beta/iam/workforce-pools/providers/create-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/create-oidc @@ -174,9 +174,10 @@ OPTIONAL FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/beta/iam/workforce-pools/providers/update-oidc b/gcloud/beta/iam/workforce-pools/providers/update-oidc index 1f35b24e7..14a06896a 100644 --- a/gcloud/beta/iam/workforce-pools/providers/update-oidc +++ b/gcloud/beta/iam/workforce-pools/providers/update-oidc @@ -170,9 +170,10 @@ FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/beta/iam/workforce-pools/update b/gcloud/beta/iam/workforce-pools/update index db33317d1..45af2fe56 100644 --- a/gcloud/beta/iam/workforce-pools/update +++ b/gcloud/beta/iam/workforce-pools/update @@ -49,9 +49,9 @@ FLAGS length. --disabled - Whether or not the workforce pool is disabled. You cannot use a - disabled workforce pool to perform new token exchanges or sign-ins - using any provider in the workforce pool. + Disables the workforce pool. You cannot use a disabled workforce pool + to perform new token exchanges or sign-ins using any provider in the + workforce pool. Specify --no-disabled to enable a disabled pool. --display-name=DISPLAY_NAME A display name for the workforce pool. Cannot exceed 32 characters in diff --git a/gcloud/beta/redis/instances/update b/gcloud/beta/redis/instances/update index 5bd633987..83c59e553 100644 --- a/gcloud/beta/redis/instances/update +++ b/gcloud/beta/redis/instances/update @@ -82,10 +82,10 @@ FLAGS Specifies which maintenance version to apply to your instance during self-service maintenance. To view the available maintenance versions for your instance, run gcloud redis instances describe [INSTANCE_ID]. - Acceptable values for this flag are either latest or one of the - specific versions listed by the describe command. If you pass the value - latest, the Memorystore updates to the most recent available - maintenance version during self service maintenance. + Acceptable values for this flag are either current_default or one of + the specific versions listed by the describe command. If you pass the + value current_default, the Memorystore updates to the most recent + available maintenance version during self service maintenance. --persistence-mode=PERSISTENCE_MODE Operation mode for automated persistence. PERSISTENCE_MODE must be one diff --git a/gcloud/bigtable/app-profiles/update b/gcloud/bigtable/app-profiles/update index 72eafff54..9924866b2 100644 --- a/gcloud/bigtable/app-profiles/update +++ b/gcloud/bigtable/app-profiles/update @@ -92,6 +92,10 @@ FLAGS --transactional-writes Allow transactional writes with a Single Cluster Routing policy. + If your app profile has single row transactions enabled, you must + specify this flag when updating that app profile. If you do not + specify this flag, then single row transactions are disabled. + 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/builds/triggers/create/bitbucketserver b/gcloud/builds/triggers/create/bitbucketserver index 371b75ab7..6ac516644 100644 --- a/gcloud/builds/triggers/create/bitbucketserver +++ b/gcloud/builds/triggers/create/bitbucketserver @@ -11,7 +11,7 @@ SYNOPSIS default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -92,8 +92,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/builds/triggers/create/cloud-source-repositories b/gcloud/builds/triggers/create/cloud-source-repositories index c5c76dc92..d43664316 100644 --- a/gcloud/builds/triggers/create/cloud-source-repositories +++ b/gcloud/builds/triggers/create/cloud-source-repositories @@ -10,7 +10,7 @@ SYNOPSIS default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -71,8 +71,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/builds/triggers/create/github b/gcloud/builds/triggers/create/github index 3c99be2ee..e7c517589 100644 --- a/gcloud/builds/triggers/create/github +++ b/gcloud/builds/triggers/create/github @@ -14,7 +14,7 @@ SYNOPSIS : --enterprise-config=ENTERPRISE_CONFIG]) : --description=DESCRIPTION --ignored-files=[GLOB,...] --include-logs-with-status --included-files=[GLOB,...] --name=NAME --region=REGION - --require-approval + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -83,8 +83,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/builds/triggers/create/gitlab-enterprise b/gcloud/builds/triggers/create/gitlab-enterprise index 24c87d6c3..c13a9cd9c 100644 --- a/gcloud/builds/triggers/create/gitlab-enterprise +++ b/gcloud/builds/triggers/create/gitlab-enterprise @@ -13,7 +13,7 @@ SYNOPSIS (--gitlab-config-resource=GITLAB_CONFIG_RESOURCE --project-namespace=PROJECT_NAMESPACE) : --description=DESCRIPTION --ignored-files=[GLOB,...] --included-files=[GLOB,...] --name=NAME - --region=REGION --require-approval + --region=REGION --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...]]) [GCLOUD_WIDE_FLAG ...] @@ -73,8 +73,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations diff --git a/gcloud/builds/triggers/create/manual b/gcloud/builds/triggers/create/manual index 22f8f2315..814907f46 100644 --- a/gcloud/builds/triggers/create/manual +++ b/gcloud/builds/triggers/create/manual @@ -8,10 +8,9 @@ SYNOPSIS | [--dockerfile=DOCKERFILE : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -58,8 +57,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -145,10 +145,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/builds/triggers/create/pubsub b/gcloud/builds/triggers/create/pubsub index 7518e2de1..bbcd2531b 100644 --- a/gcloud/builds/triggers/create/pubsub +++ b/gcloud/builds/triggers/create/pubsub @@ -9,11 +9,10 @@ SYNOPSIS : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --subscription-filter=SUBSCRIPTION_FILTER --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -69,8 +68,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -161,10 +161,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/builds/triggers/create/webhook b/gcloud/builds/triggers/create/webhook index 0080aaedd..8481aedb6 100644 --- a/gcloud/builds/triggers/create/webhook +++ b/gcloud/builds/triggers/create/webhook @@ -9,11 +9,10 @@ SYNOPSIS : --dockerfile-dir=DOCKERFILE_DIR; default="/" --dockerfile-image=DOCKERFILE_IMAGE]) : --description=DESCRIPTION --name=NAME --region=REGION - --require-approval --service-account=SERVICE_ACCOUNT + --[no-]require-approval --service-account=SERVICE_ACCOUNT --subscription-filter=SUBSCRIPTION_FILTER --substitutions=[KEY=VALUE,...] (--branch=BRANCH - | --tag=TAG) (--repository=REPOSITORY - | [--repo=REPO --repo-type=REPO_TYPE + | --tag=TAG) ([--repo=REPO --repo-type=REPO_TYPE : --github-enterprise-config=GITHUB_ENTERPRISE_CONFIG])]) [GCLOUD_WIDE_FLAG ...] @@ -75,8 +74,9 @@ REQUIRED FLAGS resources, is used. If builds/region is unset, region is set to global. - --require-approval - Require manual approval for triggered builds. + --[no-]require-approval + Require manual approval for triggered builds. Use + --require-approval to enable and --no-require-approval to disable. --service-account=SERVICE_ACCOUNT The service account used for all user-controlled operations @@ -167,10 +167,6 @@ REQUIRED FLAGS Exactly one of these must be specified: - --repository=REPOSITORY - Repository resource (2nd gen) to use, in the format - "projects/*/locations/*/connections/*/repositories/". - 1st-gen repository settings. --repo=REPO diff --git a/gcloud/compute/images/import b/gcloud/compute/images/import index 90967db29..9d2132f51 100644 --- a/gcloud/compute/images/import +++ b/gcloud/compute/images/import @@ -3,13 +3,13 @@ NAME SYNOPSIS gcloud compute images import IMAGE_NAME - (--aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION + (--source-file=SOURCE_FILE | --source-image=SOURCE_IMAGE + | --aws-access-key-id=AWS_ACCESS_KEY_ID --aws-region=AWS_REGION --aws-secret-access-key=AWS_SECRET_ACCESS_KEY --aws-session-token=AWS_SESSION_TOKEN (--aws-source-ami-file-path=AWS_SOURCE_AMI_FILE_PATH | --aws-ami-export-location=AWS_AMI_EXPORT_LOCATION - --aws-ami-id=AWS_AMI_ID) | --source-file=SOURCE_FILE - | --source-image=SOURCE_IMAGE) [--no-address] [--async] + --aws-ami-id=AWS_AMI_ID)) [--no-address] [--async] [--compute-service-account=COMPUTE_SERVICE_ACCOUNT] [--description=DESCRIPTION] [--family=FAMILY] [--no-guest-environment] [--guest-os-features=[GUEST_OS_FEATURE,...]] @@ -59,6 +59,20 @@ POSITIONAL ARGUMENTS REQUIRED FLAGS Exactly one of these must be specified: + Image import from local file, Cloud Storage or Compute Engine image. + + At most one of these can be specified: + + --source-file=SOURCE_FILE + A local file, or the Cloud Storage URI of the virtual disk file to + import. For example: gs://my-bucket/my-image.vmdk or + ./my-local-image.vmdk. For more information about Cloud Storage + URIs, see + https://cloud.google.com/storage/docs/request-endpoints#json-api. + + --source-image=SOURCE_IMAGE + An existing Compute Engine image from which to import. + Image import from AWS. --aws-access-key-id=AWS_ACCESS_KEY_ID @@ -113,20 +127,6 @@ REQUIRED FLAGS This flag argument must be specified if any of the other arguments in this group are specified. - Image import from local file, Cloud Storage or Compute Engine image. - - At most one of these can be specified: - - --source-file=SOURCE_FILE - A local file, or the Cloud Storage URI of the virtual disk file to - import. For example: gs://my-bucket/my-image.vmdk or - ./my-local-image.vmdk. For more information about Cloud Storage - URIs, see - https://cloud.google.com/storage/docs/request-endpoints#json-api. - - --source-image=SOURCE_IMAGE - An existing Compute Engine image from which to import. - OPTIONAL FLAGS --no-address Temporary VMs are created in your project during image import. Set this diff --git a/gcloud/container/clusters/create b/gcloud/container/clusters/create index 82324aee0..0a78bc24d 100644 --- a/gcloud/container/clusters/create +++ b/gcloud/container/clusters/create @@ -957,12 +957,16 @@ FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal to - 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 and + less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/container/node-pools/create b/gcloud/container/node-pools/create index 8529c5720..7076e861f 100644 --- a/gcloud/container/node-pools/create +++ b/gcloud/container/node-pools/create @@ -502,12 +502,16 @@ FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal to - 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 and + less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/container/node-pools/update b/gcloud/container/node-pools/update index 84ad7a71e..74c8af9fb 100644 --- a/gcloud/container/node-pools/update +++ b/gcloud/container/node-pools/update @@ -159,12 +159,16 @@ REQUIRED FLAGS List of supported kubelet configs in 'kubeletConfig'. - KEY VALUE - cpuManagerPolicy either 'static' or 'none' - cpuCFSQuota true or false (enabled by default) - cpuCFSQuotaPeriod interval (e.g., '100ms') - podPidsLimit integer (The value must be greater than or equal - to 1024 and less than 4194304.) + KEY VALUE + cpuManagerPolicy either 'static' or 'none' + cpuCFSQuota true or false (enabled by + default) + cpuCFSQuotaPeriod interval (e.g., '100ms') + podPidsLimit integer (The value must be + greater than or equal to 1024 + and less than 4194304.) + insecureKubeletReadonlyPortEnabled true or false (enabled by + default) List of supported sysctls in 'linuxConfig'. diff --git a/gcloud/edge-cloud/container/vpn-connections/create b/gcloud/edge-cloud/container/vpn-connections/create index 7a9de3eb1..ecff28534 100644 --- a/gcloud/edge-cloud/container/vpn-connections/create +++ b/gcloud/edge-cloud/container/vpn-connections/create @@ -3,11 +3,11 @@ NAME connection between an Edge Container cluster and a VPC network SYNOPSIS - gcloud edge-cloud container vpn-connections create - (VPN_CONNECTION : --location=LOCATION) --cluster=CLUSTER - --vpc-network=VPC_NETWORK [--async] [--high-availability] - [--labels=[KEY=VALUE,...]] [--nat-gateway-ip=NAT_GATEWAY_IP] - [--vpc-project=VPC_PROJECT] [GCLOUD_WIDE_FLAG ...] + gcloud edge-cloud container vpn-connections create VPN_CONNECTION + --cluster=CLUSTER --vpc-network=VPC_NETWORK [--async] + [--high-availability] [--labels=[KEY=VALUE,...]] [--location=LOCATION] + [--nat-gateway-ip=NAT_GATEWAY_IP] [--vpc-project=VPC_PROJECT] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Creates a new VPN connection. @@ -24,14 +24,18 @@ EXAMPLES Here VPC network and cluster should be under the same project. POSITIONAL ARGUMENTS - Vpn connection resource - VPN connection 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: + Vpn connection resource - VPN connection to create. 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 vpn_connection on the command line with a fully specified name; ◆ set the property core/project; - ◆ provide the argument --project on the command line. + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument vpn_connection on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property edge_container/location. This must be specified. @@ -40,19 +44,27 @@ POSITIONAL ARGUMENTS connection. To set the vpn_connection attribute: ▸ provide the argument vpn_connection on the command line. - This positional argument must be specified if any of the other - arguments in this group are specified. - - --location=LOCATION - The global location name. To set the location attribute: - ▸ provide the argument vpn_connection on the command line with a - fully specified name; - ▸ provide the argument --location on the command line; - ▸ set the property edge_container/location. - REQUIRED FLAGS - --cluster=CLUSTER - The name of the cluster to be connected under current project. + Cluster resource - The name of the cluster to be connected under current + project. 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 --cluster on the command line with a fully + specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. To set the + location attribute: + ◆ provide the argument --cluster on the command line with a fully + specified name; + ◆ provide the argument --location on the command line; + ◆ set the property edge_container/location. + + This must be specified. + + --cluster=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. --vpc-network=VPC_NETWORK The name of the VPC network to be connected. By default it is assumed @@ -77,6 +89,11 @@ OPTIONAL FLAGS contain only hyphens (-), underscores (_), lowercase characters, and numbers. + --location=LOCATION + For resources [vpn connection, cluster], provides fallback value for + resource location attribute. When the resource's full URI path is not + provided, location will fallback to this flag value. + --nat-gateway-ip=NAT_GATEWAY_IP The NAT gateway IP for the gateway floating IPs. Required if cluster sits behind NAT. diff --git a/gcloud/filestore/instances/help b/gcloud/filestore/instances/help index 993d4f1e5..18d19393a 100644 --- a/gcloud/filestore/instances/help +++ b/gcloud/filestore/instances/help @@ -36,6 +36,9 @@ COMMANDS restore Restore a Filestore instance from a backup. + revert + Revert a Filestore instance. + update Update a Filestore instance. diff --git a/gcloud/filestore/instances/revert b/gcloud/filestore/instances/revert new file mode 100644 index 000000000..6e19def58 --- /dev/null +++ b/gcloud/filestore/instances/revert @@ -0,0 +1,78 @@ +NAME + gcloud filestore instances revert - revert a Filestore instance + +SYNOPSIS + gcloud filestore instances revert (INSTANCE : --location=LOCATION) + --target-snapshot=TARGET_SNAPSHOT [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Revert a Filestore instance to the target snapshot. + + This command can fail for the following reasons: + ▪ The target snapshot does not exist. + ▪ The active account does not have permission to revert the instance. + ▪ The service tier of the instance does not support the operation. + +EXAMPLES + To revert an instance with the name my-instance that's located in + us-central1 to the target snapshot named my-snapshot , run: + + $ gcloud filestore instances revert my-instance \ + --target-snapshot=my-snapshot --location=us-central1 + +POSITIONAL ARGUMENTS + Instance resource - Arguments and flags that specify the Filestore + instance to revert. 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 instance 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. + + INSTANCE + ID of the instance or fully qualified identifier for the instance. To + set the instance attribute: + ▸ provide the argument instance 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 of the Filestore instance. + + To set the location attribute: + ▸ provide the argument instance on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ set the property filestore/location. + +REQUIRED FLAGS + --target-snapshot=TARGET_SNAPSHOT + Name of the Filestore snapshot to revert to. + +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. + +API REFERENCE + This command uses the file/v1 API. The full documentation for this API can + be found at: https://cloud.google.com/filestore/ + +NOTES + This variant is also available: + + $ gcloud beta filestore instances revert + diff --git a/gcloud/firestore/databases/create b/gcloud/firestore/databases/create index 33fd87c5a..b40cf984f 100644 --- a/gcloud/firestore/databases/create +++ b/gcloud/firestore/databases/create @@ -3,7 +3,8 @@ NAME database SYNOPSIS - gcloud firestore databases create [--region=REGION] [GCLOUD_WIDE_FLAG ...] + gcloud firestore databases create [--location=LOCATION] [--region=REGION] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Create a Google Cloud Firestore Native database. @@ -15,16 +16,23 @@ EXAMPLES To create an app in the nam5 region (multi-region), run: - $ gcloud firestore databases create --region=nam5 + $ gcloud firestore databases create --location=nam5 To create an app in the us-east1 region, run: - $ gcloud firestore databases create --region=us-east1 + $ gcloud firestore databases create --location=us-east1 FLAGS + --location=LOCATION + The location to create the Google Cloud Firestore Native database + within. Available locations are listed at + https://cloud.google.com/firestore/docs/locations. + --region=REGION - The region to create the Google Cloud Firestore Native database within. - Use gcloud app regions list to list available regions. + (DEPRECATED) The region to create the Google Cloud Firestore Native + database within. Use gcloud app regions list to list available regions. + + The --region option is deprecated; use --location instead. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/functions/deploy b/gcloud/functions/deploy index c0a065ebf..5b2e674f9 100644 --- a/gcloud/functions/deploy +++ b/gcloud/functions/deploy @@ -121,7 +121,9 @@ FLAGS If enabled, this command will use Cloud Functions (Second generation). If disabled with --no-gen2, Cloud Functions (First generation) will be used. If not specified, the value of this flag will be taken from the - functions/gen2 configuration property. + functions/gen2 configuration property. If the functions/gen2 + configuration property is not set, defaults to looking up the given + function and using its generation. --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/iam/workforce-pools/providers/create-oidc b/gcloud/iam/workforce-pools/providers/create-oidc index c8952b7ed..f1d7dc608 100644 --- a/gcloud/iam/workforce-pools/providers/create-oidc +++ b/gcloud/iam/workforce-pools/providers/create-oidc @@ -174,9 +174,10 @@ OPTIONAL FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/iam/workforce-pools/providers/create-saml b/gcloud/iam/workforce-pools/providers/create-saml index 9a6f76c7d..590731a2a 100644 --- a/gcloud/iam/workforce-pools/providers/create-saml +++ b/gcloud/iam/workforce-pools/providers/create-saml @@ -172,9 +172,10 @@ OPTIONAL FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/iam/workforce-pools/providers/update-oidc b/gcloud/iam/workforce-pools/providers/update-oidc index f82bfe8af..a96b5fee2 100644 --- a/gcloud/iam/workforce-pools/providers/update-oidc +++ b/gcloud/iam/workforce-pools/providers/update-oidc @@ -170,9 +170,10 @@ FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/iam/workforce-pools/providers/update-saml b/gcloud/iam/workforce-pools/providers/update-saml index bfda1f0dc..6b268074a 100644 --- a/gcloud/iam/workforce-pools/providers/update-saml +++ b/gcloud/iam/workforce-pools/providers/update-saml @@ -166,9 +166,10 @@ FLAGS characters in length. --disabled - Whether the workforce pool provider is disabled. You cannot use a - disabled provider to perform new token exchanges or sign-ins. However, - existing tokens still grant access. + Disables the workforce pool provider. You cannot use a disabled + provider to perform new token exchanges or sign-ins. However, existing + tokens still grant access. Specify --no-disabled to enable a disabled + pool. --display-name=DISPLAY_NAME A display name for the workforce pool provider. Cannot exceed 32 diff --git a/gcloud/iam/workforce-pools/update b/gcloud/iam/workforce-pools/update index a8edf143f..752f9b30d 100644 --- a/gcloud/iam/workforce-pools/update +++ b/gcloud/iam/workforce-pools/update @@ -49,9 +49,9 @@ FLAGS length. --disabled - Whether or not the workforce pool is disabled. You cannot use a - disabled workforce pool to perform new token exchanges or sign-ins - using any provider in the workforce pool. + Disables the workforce pool. You cannot use a disabled workforce pool + to perform new token exchanges or sign-ins using any provider in the + workforce pool. Specify --no-disabled to enable a disabled pool. --display-name=DISPLAY_NAME A display name for the workforce pool. Cannot exceed 32 characters in diff --git a/gcloud/network-connectivity/help b/gcloud/network-connectivity/help index 45224f9dd..3d3013a96 100644 --- a/gcloud/network-connectivity/help +++ b/gcloud/network-connectivity/help @@ -30,6 +30,9 @@ GROUPS policy-based-routes Manage Policy Based Routes. + service-connection-policies + Manage Service Connection Policies. + spokes Manage Network Connectivity Center spokes. diff --git a/gcloud/network-connectivity/service-connection-policies/create b/gcloud/network-connectivity/service-connection-policies/create new file mode 100644 index 000000000..7b53657b3 --- /dev/null +++ b/gcloud/network-connectivity/service-connection-policies/create @@ -0,0 +1,99 @@ +NAME + gcloud network-connectivity service-connection-policies create - create a + new Service Connection Policy + +SYNOPSIS + gcloud network-connectivity service-connection-policies create + (SERVICE_CONNECTION_POLICY : --region=REGION) --network=NETWORK + --service-class=SERVICE_CLASS + (--psc-subnetworks=[PSC_SUBNETWORKS,...] + : --psc-connection-limit=PSC_CONNECTION_LIMIT) [--async] + [--description=DESCRIPTION] [--labels=KEY=VALUE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a new Service Connection Policy with the given name. + +EXAMPLES + Create a Service Connection Policy with name my-service-conn-policy for + network projects/my-project/global/networks/net1 and service class + my-service-class-ad32fa4b in region us-central1. + + $ gcloud network-connectivity service-connection-policies create \ + my-service-conn-policy \ + --network="projects/my-project/global/networks/net1" \ + --service-class=my-service-class-ad32fa4b --region=us-central1 + +POSITIONAL ARGUMENTS + Service connection policy resource - Name of the Service Connection Policy + to be created. 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 service_connection_policy on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_CONNECTION_POLICY + ID of the service connection policy or fully qualified identifier for + the service connection policy. To set the service_connection_policy + attribute: + ▸ provide the argument service_connection_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument service_connection_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line. + +REQUIRED FLAGS + --network=NETWORK + Network that this service connection policy applies to. E.g. + projects/my-project/global/networks/net1 + + --service-class=SERVICE_CLASS + Service class that this policy is created for. E.g. + my-service-class-ad32fa4b + + This must be specified. + + --psc-subnetworks=[PSC_SUBNETWORKS,...] + Subnetwork to use for IP address management. + + This flag argument must be specified if any of the other arguments in + this group are specified. + + --psc-connection-limit=PSC_CONNECTION_LIMIT + Max number of PSC connections for this policy. + +OPTIONAL FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --description=DESCRIPTION + Description of the Service Connection Policy to be created. + + --labels=KEY=VALUE + List of label KEY=VALUE pairs to add. + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/service-connection-policies/delete b/gcloud/network-connectivity/service-connection-policies/delete new file mode 100644 index 000000000..3b0b05a8a --- /dev/null +++ b/gcloud/network-connectivity/service-connection-policies/delete @@ -0,0 +1,67 @@ +NAME + gcloud network-connectivity service-connection-policies delete - delete a + service connection policy + +SYNOPSIS + gcloud network-connectivity service-connection-policies delete + (SERVICE_CONNECTION_POLICY : --region=REGION) [--async] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete the specified service connection policy. + +EXAMPLES + To delete a service connection policy with name pol1 in region us-central1, + run: + + $ gcloud network-connectivity service-connection-policies delete \ + pol1 --region=us-central1 + +POSITIONAL ARGUMENTS + Service connection policy resource - Name of the Service Connection Policy + to be deleted. 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 service_connection_policy on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_CONNECTION_POLICY + ID of the service connection policy or fully qualified identifier for + the service connection policy. To set the service_connection_policy + attribute: + ▸ provide the argument service_connection_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument service_connection_policy on the command + line with a fully specified name; + ▸ provide the argument --region on the command line. + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/service-connection-policies/describe b/gcloud/network-connectivity/service-connection-policies/describe new file mode 100644 index 000000000..0214793e8 --- /dev/null +++ b/gcloud/network-connectivity/service-connection-policies/describe @@ -0,0 +1,61 @@ +NAME + gcloud network-connectivity service-connection-policies describe - describe + a service connection policy + +SYNOPSIS + gcloud network-connectivity service-connection-policies describe + (SERVICE_CONNECTION_POLICY : --region=REGION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display details about a service connection policy. + +EXAMPLES + To display details about the service connection policy named pol1 in region + us-central1, run: + + $ gcloud network-connectivity service-connection-policies describe \ + pol1 --region=us-central1 + +POSITIONAL ARGUMENTS + Service connection policy resource - Name of the service connection policy + 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 service_connection_policy on the command line + with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + SERVICE_CONNECTION_POLICY + ID of the service connection policy or fully qualified identifier for + the service connection policy. To set the service_connection_policy + attribute: + ▸ provide the argument service_connection_policy on the command + line. + + This positional argument must be specified if any of the other + arguments in this group are specified. + + --region=REGION + The location Id. + + To set the region attribute: + ▸ provide the argument service_connection_policy on the command + line with a fully specified name; + ▸ provide the argument --region 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. + +API REFERENCE + This command uses the networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/network-connectivity/service-connection-policies/help b/gcloud/network-connectivity/service-connection-policies/help new file mode 100644 index 000000000..6477fd819 --- /dev/null +++ b/gcloud/network-connectivity/service-connection-policies/help @@ -0,0 +1,30 @@ +NAME + gcloud network-connectivity service-connection-policies - manage Service + Connection Policies + +SYNOPSIS + gcloud network-connectivity service-connection-policies COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Service Connection Policies. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a new Service Connection Policy. + + delete + Delete a service connection policy. + + describe + Describe a service connection policy. + + list + List service connection policies. diff --git a/gcloud/network-connectivity/service-connection-policies/list b/gcloud/network-connectivity/service-connection-policies/list new file mode 100644 index 000000000..7a65e3550 --- /dev/null +++ b/gcloud/network-connectivity/service-connection-policies/list @@ -0,0 +1,75 @@ +NAME + gcloud network-connectivity service-connection-policies list - list service + connection policies + +SYNOPSIS + gcloud network-connectivity service-connection-policies list + --region=REGION [--filter=EXPRESSION] [--limit=LIMIT] + [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Retrieve and display a list of all service connection policies in the + specified project. + +EXAMPLES + To list all service connection policies in region us-central1, run: + + $ gcloud network-connectivity service-connection-policies list \ + --region=us-central1 + +REQUIRED FLAGS + Region resource - A Google Cloud region. Use this flag to filter the list + of service connection policies to a specific region or to all regions. Use + ``-`` to specify all regions. 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 core/project; + ◆ provide the argument --project on the command line. + + This must be specified. + + --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. + +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. + +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 networkconnectivity/v1 API. The full documentation + for this API can be found at: + https://cloud.google.com/network-connectivity/docs/reference/networkconnectivity/rest diff --git a/gcloud/org-policies/reset b/gcloud/org-policies/reset index 23551eaee..5ed804418 100644 --- a/gcloud/org-policies/reset +++ b/gcloud/org-policies/reset @@ -5,7 +5,8 @@ NAME SYNOPSIS gcloud org-policies reset CONSTRAINT (--folder=FOLDER_ID | --organization=ORGANIZATION_ID - | --project=PROJECT_ID) [GCLOUD_WIDE_FLAG ...] + | --project=PROJECT_ID) [--update-mask=UPDATE_MASK] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Resets the policy to the default for the constraint. @@ -38,6 +39,15 @@ REQUIRED FLAGS Project ID. Overrides the default core/project property value for this command invocation. +OPTIONAL FLAGS + --update-mask=UPDATE_MASK + Field mask used to specify the fields to be overwritten in the policy + by the set. The fields specified in the update_mask are relative to the + policy, not the full request. The update-mask flag can be empty, or + have values policy.spec, policy.dry_run_spec or *. If the policy does + not contain the dry_run_spec and update-mask flag is not provided, then + it defaults to policy.spec. + 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/org-policies/set-policy b/gcloud/org-policies/set-policy index 1894b214c..c26166542 100644 --- a/gcloud/org-policies/set-policy +++ b/gcloud/org-policies/set-policy @@ -24,7 +24,9 @@ FLAGS Field mask used to specify the fields to be overwritten in the policy by the set. The fields specified in the update_mask are relative to the policy, not the full request. The update-mask flag can be empty, or - have values policy.spec, policy.dry_run_spec or * + have values policy.spec, policy.dry_run_spec or *. If the policy does + not contain the dry_run_spec and update-mask flag is not provided, then + it defaults to policy.spec. GCLOUD WIDE FLAGS These flags are available to all commands: --access-token-file, --account, diff --git a/gcloud/redis/instances/update b/gcloud/redis/instances/update index c55e6f1cf..b6860dbac 100644 --- a/gcloud/redis/instances/update +++ b/gcloud/redis/instances/update @@ -81,10 +81,10 @@ FLAGS Specifies which maintenance version to apply to your instance during self-service maintenance. To view the available maintenance versions for your instance, run gcloud redis instances describe [INSTANCE_ID]. - Acceptable values for this flag are either latest or one of the - specific versions listed by the describe command. If you pass the value - latest, the Memorystore updates to the most recent available - maintenance version during self service maintenance. + Acceptable values for this flag are either current_default or one of + the specific versions listed by the describe command. If you pass the + value current_default, the Memorystore updates to the most recent + available maintenance version during self service maintenance. --persistence-mode=PERSISTENCE_MODE Operation mode for automated persistence. PERSISTENCE_MODE must be one diff --git a/gcloud/run/deploy b/gcloud/run/deploy index 88027d16d..ed429673b 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -22,7 +22,8 @@ SYNOPSIS --update-config-maps=[KEY=VALUE,...]] [--image=IMAGE | --source=SOURCE] [--[no-]allow-unauthenticated --breakglass=JUSTIFICATION - --clear-vpc-connector --[no-]cpu-throttling --description=DESCRIPTION + --clear-vpc-connector --[no-]cpu-boost --[no-]cpu-throttling + --description=DESCRIPTION --execution-environment=EXECUTION_ENVIRONMENT --revision-suffix=REVISION_SUFFIX --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS @@ -377,6 +378,11 @@ FLAGS --clear-vpc-connector Remove the VPC connector for this resource. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup. This can + reduce the perceived latency of a cold start request. Use --cpu-boost + to enable and --no-cpu-boost to disable. + --[no-]cpu-throttling Whether to throttle the CPU when the container is not actively serving requests. Use --cpu-throttling to enable and diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 08929a2a3..3715c0e62 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -11,8 +11,8 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--port=PORT] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--[no-]use-http2] - [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-throttling - --execution-environment=EXECUTION_ENVIRONMENT + [--breakglass=JUSTIFICATION --clear-vpc-connector --[no-]cpu-boost + --[no-]cpu-throttling --execution-environment=EXECUTION_ENVIRONMENT --revision-suffix=REVISION_SUFFIX --vpc-connector=VPC_CONNECTOR --vpc-egress=VPC_EGRESS --add-cloudsql-instances=[CLOUDSQL-INSTANCES,...] @@ -210,6 +210,11 @@ FLAGS --clear-vpc-connector Remove the VPC connector for this resource. + --[no-]cpu-boost + Whether to allocate extra CPU to containers on startup. This can + reduce the perceived latency of a cold start request. Use --cpu-boost + to enable and --no-cpu-boost to disable. + --[no-]cpu-throttling Whether to throttle the CPU when the container is not actively serving requests. Use --cpu-throttling to enable and diff --git a/gcloud/scc/custom-modules/help b/gcloud/scc/custom-modules/help new file mode 100644 index 000000000..2ea080b1b --- /dev/null +++ b/gcloud/scc/custom-modules/help @@ -0,0 +1,26 @@ +NAME + gcloud scc custom-modules - manage Cloud SCC (Security Command Center) + custom modules + +SYNOPSIS + gcloud scc custom-modules GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Cloud SCC (Security Command Center) custom modules. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + sha + Manage Security Health Analytics custom modules. + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules + diff --git a/gcloud/scc/custom-modules/sha/create b/gcloud/scc/custom-modules/sha/create new file mode 100644 index 000000000..687d6b799 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/create @@ -0,0 +1,90 @@ +NAME + gcloud scc custom-modules sha create - create a Security Health Analytics + custom module + +SYNOPSIS + gcloud scc custom-modules sha create + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + --display-name=DISPLAY_NAME --enablement-state=ENABLEMENT_STATE + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Create a Security Health Analytics custom module. + +EXAMPLES + To create a Security Health Analytics custom module for given organization + 123, run: + + $ gcloud scc custom-modules sha create \ + --organization=organizations/123 \ + --display-name="test_display_name" \ + --enablement-state="ENABLED" \ + --custom-config-from-file=custom_config.yaml + + To create a Security Health Analytics custom module for given folder 456, + run: + + $ gcloud scc custom-modules sha create --folder=folders/456 \ + --display-name="test_display_name" \ + --enablement-state="ENABLED" \ + --custom-config-from-file=custom_config.yaml + + To create a Security Health Analytics custom module for given project 789, + run: + + $ gcloud scc custom-modules sha create --project=projects/789 \ + --display-name="test_display_name" \ + --enablement-state="ENABLED" \ + --custom-config-from-file=custom_config.yaml + +REQUIRED FLAGS + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. + + --display-name=DISPLAY_NAME + Sets the display name of the Security Health Analytics custom module. + This display name becomes the finding category for all findings that + are returned by this custom module. The display name must be between 1 + and 128 characters, start with a lowercase letter, and contain + alphanumeric characters or underscores only. + + --enablement-state=ENABLEMENT_STATE + Sets the enablement state of the Security Health Analytics custom + module. From the following list of possible enablement states, specify + either enabled or disabled only. ENABLEMENT_STATE must be one of: + disabled, enabled, enablement-state-unspecified, inherited. + +OPTIONAL FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder where the Security Health Analytics custom module resides. + Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization where the Security Health Analytics custom module + resides. Formatted as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha create + diff --git a/gcloud/scc/custom-modules/sha/delete b/gcloud/scc/custom-modules/sha/delete new file mode 100644 index 000000000..68c40df38 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/delete @@ -0,0 +1,67 @@ +NAME + gcloud scc custom-modules sha delete - delete a Security Health Analytics + custom module + +SYNOPSIS + gcloud scc custom-modules sha delete CUSTOM_MODULE + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Delete a Security Health Analytics custom module. + +EXAMPLES + To delete a Security Health Analytics custom module with ID 123456 for + organization 123, run: + + $ gcloud scc custom-modules sha delete 123456 \ + --organization=organizations/123 + + To delete a Security Health Analytics custom module with ID 123456 for + folder 456, run: + + $ gcloud scc custom-modules sha delete 123456 --folder=folders/456 + + To delete a Security Health Analytics custom module with ID 123456 for + project 789, run: + + $ gcloud scc custom-modules sha delete 123456 --project=projects/789 + +POSITIONAL ARGUMENTS + CUSTOM_MODULE + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder where the Security Health Analytics custom module resides. + Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization where the Security Health Analytics custom module + resides. Formatted as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha delete + diff --git a/gcloud/scc/custom-modules/sha/get b/gcloud/scc/custom-modules/sha/get new file mode 100644 index 000000000..61da16d5e --- /dev/null +++ b/gcloud/scc/custom-modules/sha/get @@ -0,0 +1,72 @@ +NAME + gcloud scc custom-modules sha get - get the details of a Security Health + Analytics custom module + +SYNOPSIS + gcloud scc custom-modules sha get CUSTOM_MODULE + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the details of a Security Health Analytics custom module. It does not + resolve INHERITED enablement states to ENABLED or DISABLED for modules + created at ancestor levels. For example, if the module is enabled at the + ancestor level, modules for all child resources will have the enablement + state set to INHERITED. Use gcloud scc custom-modules sha get-effective to + retrieve a custom module with its effective enablement state. + +EXAMPLES + To get the details of a Security Health Analytics custom module with ID + 123456 for organization 123, run: + + $ gcloud scc custom-modules sha get 123456 \ + --organization=organizations/123 + + To get the details of a Security Health Analytics custom module with ID + 123456 for folder 456, run: + + $ gcloud scc custom-modules sha get 123456 --folder=folders/456 + + To get the details of a Security Health Analytics custom module with ID + 123456 for project 789, run: + + $ gcloud scc custom-modules sha get 123456 --project=projects/789 + +POSITIONAL ARGUMENTS + CUSTOM_MODULE + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder from which to get the custom module details. Formatted as + folders/456 or just 456. + + --organization=ORGANIZATION + Organization from which to get the custom module details. Formatted + as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project from which to get the custom module + details. Formatted as projects/789 or just 789. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha get + diff --git a/gcloud/scc/custom-modules/sha/get-effective b/gcloud/scc/custom-modules/sha/get-effective new file mode 100644 index 000000000..a86eb77e7 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/get-effective @@ -0,0 +1,74 @@ +NAME + gcloud scc custom-modules sha get-effective - get the details of a Security + Health Analytics custom module with effective enablement state + +SYNOPSIS + gcloud scc custom-modules sha get-effective CUSTOM_MODULE + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Get the details of a Security Health Analytics custom module. For inherited + custom modules, the get-effective command resolves INHERITED enablement + states to ENABLED or DISABLED. For example, if an inherited custom module + is enabled at the ancestor level, then the get-effective command displays + the enablement state as ENABLED instead of INHERITED in a child folder or + project. + +EXAMPLES + To get the details of a Security Health Analytics custom module 123456 with + its effective enablement state from organization 123, run: + + $ gcloud scc custom-modules sha get-effective 123456 \ + --organization=organizations/123 + + To get the details of a Security Health Analytics custom module 123456 with + its effective enablement state from folder 456, run: + + $ gcloud scc custom-modules sha get-effective 123456 \ + --folder=folders/456 + + To get the details of a Security Health Analytics custom module 123456 with + its effective enablement state from project 789, run: + + $ gcloud scc custom-modules sha get-effective 123456 \ + --project=projects/789 + +POSITIONAL ARGUMENTS + CUSTOM_MODULE + ID or the full resource name of the effective Security Health Analytics + custom module. If you specify the full resource name, you do not need + to specify the --organization, --folder, or --project flags. + +FLAGS + At most one of these can be specified: + + --folder=FOLDER + Folder from which to get the custom module details. Formatted as + folders/456 or just 456. + + --organization=ORGANIZATION + Organization from which to get the custom module details. Formatted + as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project from which to get the custom module + details. Formatted as projects/789 or just 789. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha get-effective + diff --git a/gcloud/scc/custom-modules/sha/help b/gcloud/scc/custom-modules/sha/help new file mode 100644 index 000000000..7981a7d84 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/help @@ -0,0 +1,50 @@ +NAME + gcloud scc custom-modules sha - manage Security Health Analytics custom + modules + +SYNOPSIS + gcloud scc custom-modules sha COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Security Health Analytics custom modules. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + create + Create a Security Health Analytics custom module. + + delete + Delete a Security Health Analytics custom module. + + get + Get the details of a Security Health Analytics custom module. + + get-effective + Get the details of a Security Health Analytics custom module with + effective enablement state. + + list + List the details of Security Health Analytics custom modules. + + list-descendant + List the details of the resident and descendant Security Health + Analytics custom modules. + + list-effective + List the details of Security Health Analytics custom modules with + effective enablement states. + + update + Update a Security Health Analytics custom module. + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha + diff --git a/gcloud/scc/custom-modules/sha/list b/gcloud/scc/custom-modules/sha/list new file mode 100644 index 000000000..0f800e8b6 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/list @@ -0,0 +1,96 @@ +NAME + gcloud scc custom-modules sha list - list the details of Security Health + Analytics custom modules + +SYNOPSIS + gcloud scc custom-modules sha list + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the details of the resident and inherited Security Health Analytics + custom modules for the specified folder or project. For an organization, + this command lists only the custom modules that are created at the + organization level. Custom modules created in child folders or projects are + not included in the list. To list the resident custom modules and the + modules that are created in child folders or projects, use gcloud scc + custom-modules sha list-descendant. + +EXAMPLES + To list resident and inherited Security Health Analytics custom modules for + organization 123, run: + + $ gcloud scc custom-modules sha list --organization=organizations/123 + + To list resident and inherited Security Health Analytics custom modules for + folder 456, run: + + $ gcloud scc custom-modules sha list --folder=folders/456 + + To list resident and inherited Security Health Analytics custom modules for + project 789, run: + + $ gcloud scc custom-modules sha list --project=projects/789 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER + Folder for listing the Security Health Analytics custom modules + created at the current folder level and inherited modules from CRM + ancestors. Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization for listing the Security Health Analytics custom modules + created at the organization level. Formatted as organizations/123 or + just 123. + + --project=PROJECT + ID or number of the project for listing the Security Health Analytics + custom modules created at current project level and inherited modules + from CRM ancestors. Formatted as projects/789 or just 789. + +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. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha list + diff --git a/gcloud/scc/custom-modules/sha/list-descendant b/gcloud/scc/custom-modules/sha/list-descendant new file mode 100644 index 000000000..82d2b60b3 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/list-descendant @@ -0,0 +1,98 @@ +NAME + gcloud scc custom-modules sha list-descendant - list the details of the + resident and descendant Security Health Analytics custom modules + +SYNOPSIS + gcloud scc custom-modules sha list-descendant + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the details of the resident and descendant Security Health Analytics + custom modules for a specified organization or folder. For a project, this + command lists only the custom modules that are created in the project. + Modules created in a parent organization or folder are excluded from the + list. To list the resident custom modules and the modules that are + inherited from a parent organization and folder, use gcloud scc + custom-modules sha list. + +EXAMPLES + To list resident and descendant Security Health Analytics custom modules + for organization 123, run: + + $ gcloud scc custom-modules sha list-descendant \ + --organization=organizations/123 + + To list resident and descendant Security Health Analytics custom modules + for folder 456, run: + + $ gcloud scc custom-modules sha list-descendant --folder=folders/456 + + To list resident and descendant Security Health Analytics custom modules + for project 789, run: + + $ gcloud scc custom-modules sha list-descendant \ + --project=projects/789 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER + Folder for listing the Security Health Analytics custom modules + created at the current folder level and its child resources. + Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization for listing the Security Health Analytics custom modules + created at the organization level and its child resources. Formatted + as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project for listing the Security Health Analytics + custom modules at current project level. Formatted as projects/789 or + just 789. + +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. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha list-descendant + diff --git a/gcloud/scc/custom-modules/sha/list-effective b/gcloud/scc/custom-modules/sha/list-effective new file mode 100644 index 000000000..543b4966e --- /dev/null +++ b/gcloud/scc/custom-modules/sha/list-effective @@ -0,0 +1,95 @@ +NAME + gcloud scc custom-modules sha list-effective - list the details of Security + Health Analytics custom modules with effective enablement states + +SYNOPSIS + gcloud scc custom-modules sha list-effective + (--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT) + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List the details of resident and inherited Security Health Analytics custom + modules for the specified folder or project with their effective enablement + states. For an organization, this command lists only the custom modules + that are created at the organization level. Custom modules created in child + folders or projects are not included in the list. + +EXAMPLES + To list resident and inherited Security Health Analytics custom modules + with effective enablement states for organization 123, run: + + $ gcloud scc custom-modules sha list-effective \ + --organization=organizations/123 + + To list resident and inherited effective Security Health Analytics custom + modules with effective enablement states for folder 456, run: + + $ gcloud scc custom-modules sha list-effective --folder=folders/456 + + To list resident and inherited effective Security Health Analytics custom + modules with effective enablement states for project 789, run: + + $ gcloud scc custom-modules sha list-effective --project=projects/789 + +REQUIRED FLAGS + Exactly one of these must be specified: + + --folder=FOLDER + Folder for listing the effective Security Health Analytics custom + modules created at the current folder level and inherited modules + from CRM ancestors. Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization for listing the effective Security Health Analytics + custom modules created at the organization level. Formatted as + organizations/123 or just 123. + + --project=PROJECT + ID or number of the project for listing the effective Security Health + Analytics custom modules for the current project level and inherited + modules from CRM ancestors. Formatted as projects/789 or just 789. + +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. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha list-effective + diff --git a/gcloud/scc/custom-modules/sha/update b/gcloud/scc/custom-modules/sha/update new file mode 100644 index 000000000..0ca5a4cf5 --- /dev/null +++ b/gcloud/scc/custom-modules/sha/update @@ -0,0 +1,89 @@ +NAME + gcloud scc custom-modules sha update - update a Security Health Analytics + custom module + +SYNOPSIS + gcloud scc custom-modules sha update CUSTOM_MODULE + [--custom-config-from-file=CUSTOM_CONFIG_FROM_FILE] + [--enablement-state=ENABLEMENT_STATE] [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Security Health Analytics custom module. + +EXAMPLES + To update a Security Health Analytics custom module with ID 123456 for + organization 123, run: + + $ gcloud scc custom-modules sha update 123456 \ + --organization=organizations/123 --enablement-state="ENABLED" \ + --custom-config-from-file=custom_config.yaml + + To update a Security Health Analytics custom module with ID 123456 for + folder 456, run: + + $ gcloud scc custom-modules sha update 123456 --folder=folders/456 \ + --enablement-state="ENABLED" \ + --custom-config-from-file=custom_config.yaml + + To update a Security Health Analytics custom module with ID 123456 for + project 789, run: + + $ gcloud scc custom-modules sha update 123456 \ + --project=projects/789 --enablement-state="ENABLED" \ + --custom-config-from-file=custom_config.yaml + +POSITIONAL ARGUMENTS + CUSTOM_MODULE + ID or the full resource name of the Security Health Analytics custom + module. If you specify the full resource name, you do not need to + specify the --organization, --folder, or --project flags. + +FLAGS + --custom-config-from-file=CUSTOM_CONFIG_FROM_FILE + Path to a YAML file that contains the configuration for the Security + Health Analytics custom module. + + --enablement-state=ENABLEMENT_STATE + Sets the enablement state of the Security Health Analytics custom + module. From the following list of possible enablement states, specify + either enabled, disabled or inherited only. ENABLEMENT_STATE must be + one of: disabled, enabled, enablement-state-unspecified, inherited. + + --update-mask=UPDATE_MASK + Optional: If left unspecified (default), an update-mask is + automatically created using the flags specified in the command and only + those values are updated. + + At most one of these can be specified: + + --folder=FOLDER + Folder where the Security Health Analytics custom module resides. + Formatted as folders/456 or just 456. + + --organization=ORGANIZATION + Organization where the Security Health Analytics custom module + resides. Formatted as organizations/123 or just 123. + + --project=PROJECT + ID or number of the project where the Security Health Analytics + custom module resides. Formatted as projects/789 or just 789. + +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 securitycenter/v1 API. The full documentation for + this API can be found at: https://cloud.google.com/security-command-center + +NOTES + This variant is also available: + + $ gcloud alpha scc custom-modules sha update + diff --git a/gcloud/scc/help b/gcloud/scc/help index 0641c5078..44aa45704 100644 --- a/gcloud/scc/help +++ b/gcloud/scc/help @@ -21,6 +21,9 @@ GROUPS bqexports Manage Cloud SCC (Security Command Center) BigQuery exports. + custom-modules + Manage Cloud SCC (Security Command Center) custom modules. + findings Manage Cloud SCC (Security Command Center) findings. diff --git a/gcloud/workflows/deploy b/gcloud/workflows/deploy index 3b80dd427..5b945e5da 100644 --- a/gcloud/workflows/deploy +++ b/gcloud/workflows/deploy @@ -3,6 +3,7 @@ NAME SYNOPSIS gcloud workflows deploy (WORKFLOW : --location=LOCATION) [--async] + [--call-log-level=CALL_LOG_LEVEL; default="none"] [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] [--service-account=SERVICE_ACCOUNT] [--source=SOURCE] [GCLOUD_WIDE_FLAG ...] @@ -58,6 +59,20 @@ FLAGS Return immediately, without waiting for the operation in progress to complete. + --call-log-level=CALL_LOG_LEVEL; default="none" + Level of call logging to apply by default for the workflow. + CALL_LOG_LEVEL must be one of: + + log-all-calls + Log all calls to subworkflows or library functions and their + results. + log-errors-only + Log when a call is stopped due to an exception. + log-none + Perform no call logging. + none + No logging level specified. + --description=DESCRIPTION The description of the workflow to deploy. diff --git a/gcloud/workflows/execute b/gcloud/workflows/execute index 731c7b4dd..0666b13f4 100644 --- a/gcloud/workflows/execute +++ b/gcloud/workflows/execute @@ -57,9 +57,12 @@ FLAGS log-errors-only Log when a call is stopped due to an exception. - none + log-none Perform no call logging. + none + No call logging level specified. + --data=DATA JSON string with data that will be passed to the workflow as an argument. diff --git a/gcloud/workflows/run b/gcloud/workflows/run index ebdc8e651..f93b51b64 100644 --- a/gcloud/workflows/run +++ b/gcloud/workflows/run @@ -59,8 +59,10 @@ FLAGS results. log-errors-only Log when a call is stopped due to an exception. - none + log-none Perform no call logging. + none + No logging level specified. --data=DATA JSON string with data that will be passed to the workflow as an