diff --git a/gcloud/_version b/gcloud/_version index 5f8bf13e4..b1d2283bf 100644 --- a/gcloud/_version +++ b/gcloud/_version @@ -1,6 +1,6 @@ -Google Cloud SDK 375.0.0 -alpha 2022.02.25 -beta 2022.02.25 +Google Cloud SDK 376.0.0 +alpha 2022.03.04 +beta 2022.03.04 bq 2.0.74 -core 2022.02.25 +core 2022.03.04 gsutil 5.6 diff --git a/gcloud/alpha/anthos/config/controller/delete b/gcloud/alpha/anthos/config/controller/delete index e8c8dd014..9c342d37b 100644 --- a/gcloud/alpha/anthos/config/controller/delete +++ b/gcloud/alpha/anthos/config/controller/delete @@ -58,8 +58,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/controller/describe b/gcloud/alpha/anthos/config/controller/describe index d9f74a540..7ababea67 100644 --- a/gcloud/alpha/anthos/config/controller/describe +++ b/gcloud/alpha/anthos/config/controller/describe @@ -54,8 +54,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/controller/list b/gcloud/alpha/anthos/config/controller/list index d2f0ec6b2..b8148a459 100644 --- a/gcloud/alpha/anthos/config/controller/list +++ b/gcloud/alpha/anthos/config/controller/list @@ -72,8 +72,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/operations/describe b/gcloud/alpha/anthos/config/operations/describe index 7c0ce9133..8fe2f131d 100644 --- a/gcloud/alpha/anthos/config/operations/describe +++ b/gcloud/alpha/anthos/config/operations/describe @@ -54,8 +54,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/operations/list b/gcloud/alpha/anthos/config/operations/list index 387372ec5..f74d45983 100644 --- a/gcloud/alpha/anthos/config/operations/list +++ b/gcloud/alpha/anthos/config/operations/list @@ -72,8 +72,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/sync/help b/gcloud/alpha/anthos/config/sync/help index c613b702f..3d68dae43 100644 --- a/gcloud/alpha/anthos/config/sync/help +++ b/gcloud/alpha/anthos/config/sync/help @@ -18,6 +18,9 @@ GROUPS repo (ALPHA) Anthos config sync repo command group. + resources + (ALPHA) Anthos config sync resources command group. + NOTES This command is currently in alpha and might change without notice. If this command fails with API permission errors despite specifying the correct diff --git a/gcloud/alpha/anthos/config/sync/repo/describe b/gcloud/alpha/anthos/config/sync/repo/describe index 3471c2517..9ab298823 100644 --- a/gcloud/alpha/anthos/config/sync/repo/describe +++ b/gcloud/alpha/anthos/config/sync/repo/describe @@ -75,9 +75,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. PREREQUISITES - Please setup Connect Gateway for the registered clusters in order to use - this command. The instructions can be found at - https://cloud.google.com/anthos/multicluster-management/gateway/setup. + Please setup Connect Gateway if your registered clusters are non-GKE + clusters. The instructions can be found at + https://cloud.google.com/anthos/multicluster-management/gateway/setup. For + registered clusters that are GKE clusters, no need to setup the Connect + Gateway. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/sync/repo/list b/gcloud/alpha/anthos/config/sync/repo/list index 52c067498..b1abe6925 100644 --- a/gcloud/alpha/anthos/config/sync/repo/list +++ b/gcloud/alpha/anthos/config/sync/repo/list @@ -75,9 +75,11 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. PREREQUISITES - Please setup Connect Gateway for the registered clusters in order to use - this command. The instructions can be found at - https://cloud.google.com/anthos/multicluster-management/gateway/setup. + Please setup Connect Gateway if your registered clusters are non-GKE + clusters. The instructions can be found at + https://cloud.google.com/anthos/multicluster-management/gateway/setup. For + registered clusters that are GKE clusters, no need to setup the Connect + Gateway. NOTES This command is currently in alpha and might change without notice. If this diff --git a/gcloud/alpha/anthos/config/sync/resources/help b/gcloud/alpha/anthos/config/sync/resources/help new file mode 100644 index 000000000..6081d2958 --- /dev/null +++ b/gcloud/alpha/anthos/config/sync/resources/help @@ -0,0 +1,27 @@ +NAME + gcloud alpha anthos config sync resources - anthos config sync resources + command group + +SYNOPSIS + gcloud alpha anthos config sync resources COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Anthos config sync resources command group. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List resources and their status that are synced by Config Sync. + +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/anthos/config/sync/resources/list b/gcloud/alpha/anthos/config/sync/resources/list new file mode 100644 index 000000000..7cf3314e4 --- /dev/null +++ b/gcloud/alpha/anthos/config/sync/resources/list @@ -0,0 +1,70 @@ +NAME + gcloud alpha anthos config sync resources list - list resources and their + status that are synced by Config Sync + +SYNOPSIS + gcloud alpha anthos config sync resources list [--cluster=CLUSTER] + [--membership=MEMBERSHIP] [--sync-name=SYNC_NAME] + [--sync-namespace=SYNC_NAMESPACE] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List resources and their status that are synced by Config Sync. + +EXAMPLES + To list all managed resources in the current project, run: + + $ gcloud alpha anthos config sync resources list list + + To list all managed resources in a specific Config Controller cluster, run: + + $ gcloud alpha anthos config sync resources list list \ + --cluster= + + To list managed resources from a Git repo synced by Config Sync across + multiple clusters, run: + + $ gcloud alpha anthos config sync resources list list \ + --sync-name=root-sync --sync-namespace=config-management-system + + To list managed resources from a Git repo synced by Config Sync from a + specific cluster, run: + + $ gcloud alpha anthos config sync resources list list \ + --sync-namespace= --sync-name=repo-sync \ + --cluster= + +FLAGS + --cluster=CLUSTER + The cluster name or the membership name that a repository is synced to. + + --membership=MEMBERSHIP + The membership name that the listed Config Sync repos are synced to. A + membership is for a registered cluster to a fleet. It supports a single + membership or multiple memberships with the format + membership1,membership2 or membership. + + --sync-name=SYNC_NAME + Name of the RootSync or RepoSync CR to sync a repository. + + --sync-namespace=SYNC_NAMESPACE + Namespace of the RootSync or RepoSync CR to sync a repository. + +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. + +PREREQUISITES + Please setup Connect Gateway in order to use this command with non-GKE + registered clusters. The instructions can be found at + https://cloud.google.com/anthos/multicluster-management/gateway/setup. + +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/bms/help b/gcloud/alpha/bms/help index c578f2fcb..c5bfdb2e6 100644 --- a/gcloud/alpha/bms/help +++ b/gcloud/alpha/bms/help @@ -24,13 +24,6 @@ GROUPS nfs-shares (ALPHA) Manage NFS shares in Bare Metal Solution. - serial-console-ssh-keys - (ALPHA) Manage interactive serial console SSH keys in Bare Metal - Solution. - - snapshot-schedule-policies - (ALPHA) Manage snapshot-schedule-policies in Bare Metal Solution. - volumes (ALPHA) Manage bare metal volumes in Bare Metal Solution. diff --git a/gcloud/alpha/bms/instances/disable-serial-console b/gcloud/alpha/bms/instances/disable-serial-console deleted file mode 100644 index 237795490..000000000 --- a/gcloud/alpha/bms/instances/disable-serial-console +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud alpha bms instances disable-serial-console - disable interactive - serial console for a Bare Metal Solution instance - -SYNOPSIS - gcloud alpha bms instances disable-serial-console - (INSTANCE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Disables interactive serial console for a Bare Metal Solution - instance. - -EXAMPLES - To disable interactive serial console for an instance named test-instance, - run: - - $ gcloud alpha bms instances disable-serial-console test-instance - -POSITIONAL ARGUMENTS - Instance resource - Arguments and flags that specify the Bare Metal - Solution instance you want to disable interactive serial console for. 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; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - 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 must be specified if any of the other arguments in - this group are specified. - - --region=REGION - Region of the resource. To set the region attribute: - ▸ provide the argument instance 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 baremetalsolution/v2 API. The full documentation for - this API can be found at: https://cloud.google.com/bare-metal - -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/bms/instances/enable-serial-console b/gcloud/alpha/bms/instances/enable-serial-console deleted file mode 100644 index 506cbf339..000000000 --- a/gcloud/alpha/bms/instances/enable-serial-console +++ /dev/null @@ -1,68 +0,0 @@ -NAME - gcloud alpha bms instances enable-serial-console - enable interactive - serial console for a Bare Metal Solution instance - -SYNOPSIS - gcloud alpha bms instances enable-serial-console - (INSTANCE : --region=REGION) [--async] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Enables interactive serial console for a Bare Metal Solution - instance. - -EXAMPLES - To enable interactive serial console for an instance named test-instance, - run: - - $ gcloud alpha bms instances enable-serial-console test-instance - -POSITIONAL ARGUMENTS - Instance resource - Arguments and flags that specify the Bare Metal - Solution instance you want to enable interactive serial console for. 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; - ◆ set the property core/project; - ◆ provide the argument --project on the command line. - - 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 must be specified if any of the other arguments in - this group are specified. - - --region=REGION - Region of the resource. To set the region attribute: - ▸ provide the argument instance 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 baremetalsolution/v2 API. The full documentation for - this API can be found at: https://cloud.google.com/bare-metal - -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/bms/instances/help b/gcloud/alpha/bms/instances/help index 7d79566a3..e24a97e71 100644 --- a/gcloud/alpha/bms/instances/help +++ b/gcloud/alpha/bms/instances/help @@ -19,14 +19,6 @@ COMMANDS describe (ALPHA) Describe a Bare Metal solution instance. - disable-serial-console - (ALPHA) Disable interactive serial console for a Bare Metal Solution - instance. - - enable-serial-console - (ALPHA) Enable interactive serial console for a Bare Metal Solution - instance. - list (ALPHA) List Bare Metal Solution instances in a project. diff --git a/gcloud/alpha/bms/serial-console-ssh-keys/add b/gcloud/alpha/bms/serial-console-ssh-keys/add deleted file mode 100644 index b46b1fd3d..000000000 --- a/gcloud/alpha/bms/serial-console-ssh-keys/add +++ /dev/null @@ -1,69 +0,0 @@ -NAME - gcloud alpha bms serial-console-ssh-keys add - add a Bare Metal Solution - interactive serial console SSH key - -SYNOPSIS - gcloud alpha bms serial-console-ssh-keys add SERIAL_CONSOLE_SSH_KEY - (--key=KEY | --key-file=KEY_FILE) [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Add a Bare Metal Solution interactive serial console SSH key. - -EXAMPLES - To add an SSH key called my-ssh-key in project my-project with a public key - ABC6695 - - $ gcloud alpha bms serial-console-ssh-keys add my-ssh-key \ - --project=my-project --key=ABC6695 - - To add an SSH key called my-ssh-key in project my-project with a public key - stored in /home/user/.ssh/id_rsa.pub - - $ gcloud alpha bms serial-console-ssh-keys add my-ssh-key \ - --project=my-project --key-file=/home/user/.ssh/id_rsa.pub - -POSITIONAL ARGUMENTS - Serial console ssh key resource - serial_console_ssh_key. 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 serial_console_ssh_key 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 region - attribute: - ◆ provide the argument serial_console_ssh_key on the command line with - a fully specified name; - ◆ global is the only supported location. - - This must be specified. - - SERIAL_CONSOLE_SSH_KEY - ID of the serial_console_ssh_key or fully qualified identifier for - the serial_console_ssh_key. To set the serial_console_ssh_key - attribute: - ▸ provide the argument serial_console_ssh_key on the command line. - -REQUIRED FLAGS - Exactly one of these must be specified: - - --key=KEY - The SSH public key to add for the interactive serial console - - --key-file=KEY_FILE - The path to a file containing an SSH public key to add for the - interactive serial console - -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/bms/serial-console-ssh-keys/help b/gcloud/alpha/bms/serial-console-ssh-keys/help deleted file mode 100644 index 753f54ca4..000000000 --- a/gcloud/alpha/bms/serial-console-ssh-keys/help +++ /dev/null @@ -1,35 +0,0 @@ -NAME - gcloud alpha bms serial-console-ssh-keys - manage interactive serial - console SSH keys in Bare Metal Solution - -SYNOPSIS - gcloud alpha bms serial-console-ssh-keys COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage interactive serial console SSH keys in Bare Metal Solution. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - add - (ALPHA) Add a Bare Metal Solution interactive serial console SSH key. - - list - (ALPHA) List Bare Metal Solution interactive serial console SSH keys in - a project. - - remove - (ALPHA) Remove a Bare Metal solution interactive serial console SSH - key. - -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/bms/serial-console-ssh-keys/list b/gcloud/alpha/bms/serial-console-ssh-keys/list deleted file mode 100644 index 181d89603..000000000 --- a/gcloud/alpha/bms/serial-console-ssh-keys/list +++ /dev/null @@ -1,44 +0,0 @@ -NAME - gcloud alpha bms serial-console-ssh-keys list - list Bare Metal Solution - interactive serial console SSH keys in a project - -SYNOPSIS - gcloud alpha bms serial-console-ssh-keys list [--filter=EXPRESSION] - [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List Bare Metal Solution interactive serial console SSH keys in a - project. - -EXAMPLES - To list all interactive serial console SSH keys within the project, run: - - $ gcloud alpha bms serial-console-ssh-keys list - -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, --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, --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. - -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/bms/serial-console-ssh-keys/remove b/gcloud/alpha/bms/serial-console-ssh-keys/remove deleted file mode 100644 index e1cb30897..000000000 --- a/gcloud/alpha/bms/serial-console-ssh-keys/remove +++ /dev/null @@ -1,51 +0,0 @@ -NAME - gcloud alpha bms serial-console-ssh-keys remove - remove a Bare Metal - solution interactive serial console SSH key - -SYNOPSIS - gcloud alpha bms serial-console-ssh-keys remove SERIAL_CONSOLE_SSH_KEY - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Remove a Bare Metal Solution interactive serial console SSH key. - -EXAMPLES - To remove an SSH key called my-ssh-key run: - - $ gcloud alpha bms serial-console-ssh-keys remove my-ssh-key - -POSITIONAL ARGUMENTS - Serial console ssh key resource - serial_console_ssh_key. 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 serial_console_ssh_key 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 region - attribute: - ◆ provide the argument serial_console_ssh_key on the command line with - a fully specified name; - ◆ global is the only supported location. - - This must be specified. - - SERIAL_CONSOLE_SSH_KEY - ID of the serial_console_ssh_key or fully qualified identifier for - the serial_console_ssh_key. To set the serial_console_ssh_key - attribute: - ▸ provide the argument serial_console_ssh_key on the command line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/bms/snapshot-schedule-policies/create b/gcloud/alpha/bms/snapshot-schedule-policies/create deleted file mode 100644 index e01fd5636..000000000 --- a/gcloud/alpha/bms/snapshot-schedule-policies/create +++ /dev/null @@ -1,89 +0,0 @@ -NAME - gcloud alpha bms snapshot-schedule-policies create - create a Bare Metal - Solution snapshot schedule policy - -SYNOPSIS - gcloud alpha bms snapshot-schedule-policies create SNAPSHOT_SCHEDULE_POLICY - --schedule=[CRONTAB_SPEC,RETENTION_COUNT,PREFIX,...] - [--description=DESCRIPTION] [--labels=[KEY=VALUE,...]] - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Create a Bare Metal Solution snapshot schedule policy. - -EXAMPLES - To create a policy called my-policy in project my-project with description - my-description a schedule that runs every 3 hours and labels 'key1=value1' - and 'key2=value2', run: - - $ gcloud alpha bms snapshot-schedule-policies create my-policy \ - --project=my-project --description=my-description \ - --schedule="crontab_spec=0 */3 * * \ - *,retention_count=10,prefix=example" \ - --labels=key1=value1,key2=value2 - -POSITIONAL ARGUMENTS - Snapshot schedule policy resource - snapshot_schedule_policy. 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 snapshot_schedule_policy 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 region - attribute: - ◆ provide the argument snapshot_schedule_policy on the command line - with a fully specified name; - ◆ global is the only supported location. - - This must be specified. - - SNAPSHOT_SCHEDULE_POLICY - ID of the snapshot_schedule_policy or fully qualified identifier for - the snapshot_schedule_policy. To set the snapshot_schedule_policy - attribute: - ▸ provide the argument snapshot_schedule_policy on the command - line. - -REQUIRED FLAGS - --schedule=[CRONTAB_SPEC,RETENTION_COUNT,PREFIX,...] - Adds a schedule for taking snapshots of volumes under this policy. This - flag may be repeated to specify up to 5 schedules. - - crontab_spec - Specification of the times at which snapshots will be taken. This - should be in Crontab format: - http://en.wikipedia.org/wiki/Cron#Overview - - retention_count - The maximum number of snapshots to retain in this schedule. - - prefix - Value to append to the name of snapshots created by this schedule. - -OPTIONAL FLAGS - --description=DESCRIPTION - Description of the policy. - - --labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to add. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - -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/bms/snapshot-schedule-policies/delete b/gcloud/alpha/bms/snapshot-schedule-policies/delete deleted file mode 100644 index a98feca4c..000000000 --- a/gcloud/alpha/bms/snapshot-schedule-policies/delete +++ /dev/null @@ -1,55 +0,0 @@ -NAME - gcloud alpha bms snapshot-schedule-policies delete - describe a Bare Metal - solution snapshot schedule policy - -SYNOPSIS - gcloud alpha bms snapshot-schedule-policies delete SNAPSHOT_SCHEDULE_POLICY - [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Delete a Bare Metal Solution snapshot schedule policy. - -EXAMPLES - To delete a snapshot schedule policy called my-policy in project - my-project, run: - - $ gcloud alpha bms snapshot-schedule-policies delete my-policy \ - --project=my-project - -POSITIONAL ARGUMENTS - Snapshot schedule policy resource - snapshot_schedule_policy. 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 snapshot_schedule_policy 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 region - attribute: - ◆ provide the argument snapshot_schedule_policy on the command line - with a fully specified name; - ◆ global is the only supported location. - - This must be specified. - - SNAPSHOT_SCHEDULE_POLICY - ID of the snapshot_schedule_policy or fully qualified identifier for - the snapshot_schedule_policy. To set the snapshot_schedule_policy - attribute: - ▸ provide the argument snapshot_schedule_policy on the command - line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/bms/snapshot-schedule-policies/describe b/gcloud/alpha/bms/snapshot-schedule-policies/describe deleted file mode 100644 index 2a7797a5e..000000000 --- a/gcloud/alpha/bms/snapshot-schedule-policies/describe +++ /dev/null @@ -1,55 +0,0 @@ -NAME - gcloud alpha bms snapshot-schedule-policies describe - describe a Bare - Metal solution snapshot schedule policy - -SYNOPSIS - gcloud alpha bms snapshot-schedule-policies describe - SNAPSHOT_SCHEDULE_POLICY [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Describe a Bare Metal Solution snapshot schedule policy. - -EXAMPLES - To get a description of a snapshot schedule policy called my-policy in - project my-project, run: - - $ gcloud alpha bms snapshot-schedule-policies describe my-policy \ - --project=my-project - -POSITIONAL ARGUMENTS - Snapshot schedule policy resource - snapshot_schedule_policy. 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 snapshot_schedule_policy 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 region - attribute: - ◆ provide the argument snapshot_schedule_policy on the command line - with a fully specified name; - ◆ global is the only supported location. - - This must be specified. - - SNAPSHOT_SCHEDULE_POLICY - ID of the snapshot_schedule_policy or fully qualified identifier for - the snapshot_schedule_policy. To set the snapshot_schedule_policy - attribute: - ▸ provide the argument snapshot_schedule_policy on the command - line. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/bms/snapshot-schedule-policies/help b/gcloud/alpha/bms/snapshot-schedule-policies/help deleted file mode 100644 index 016792e98..000000000 --- a/gcloud/alpha/bms/snapshot-schedule-policies/help +++ /dev/null @@ -1,40 +0,0 @@ -NAME - gcloud alpha bms snapshot-schedule-policies - manage - snapshot-schedule-policies in Bare Metal Solution - -SYNOPSIS - gcloud alpha bms snapshot-schedule-policies COMMAND [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Manage snapshot-schedule-policies in Bare Metal Solution. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --help. - - Run $ gcloud help for details. - -COMMANDS - COMMAND is one of the following: - - create - (ALPHA) Create a Bare Metal Solution snapshot schedule policy. - - delete - (ALPHA) Describe a Bare Metal solution snapshot schedule policy. - - describe - (ALPHA) Describe a Bare Metal solution snapshot schedule policy. - - list - (ALPHA) List Bare Metal Solution snapshot schedule policies in a - project. - - update - (ALPHA) Create a Bare Metal Solution snapshot schedule policy. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/bms/snapshot-schedule-policies/list b/gcloud/alpha/bms/snapshot-schedule-policies/list deleted file mode 100644 index 6d1429d09..000000000 --- a/gcloud/alpha/bms/snapshot-schedule-policies/list +++ /dev/null @@ -1,43 +0,0 @@ -NAME - gcloud alpha bms snapshot-schedule-policies list - list Bare Metal Solution - snapshot schedule policies in a project - -SYNOPSIS - gcloud alpha bms snapshot-schedule-policies list [--filter=EXPRESSION] - [--limit=LIMIT] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) List Bare Metal Solution snapshot schedule policies in a project. - -EXAMPLES - To list all snapshot schedule policies within the project, run: - - $ gcloud alpha bms snapshot-schedule-policies list - -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, --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, --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. - -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/bms/snapshot-schedule-policies/update b/gcloud/alpha/bms/snapshot-schedule-policies/update deleted file mode 100644 index 1474505a7..000000000 --- a/gcloud/alpha/bms/snapshot-schedule-policies/update +++ /dev/null @@ -1,119 +0,0 @@ -NAME - gcloud alpha bms snapshot-schedule-policies update - create a Bare Metal - Solution snapshot schedule policy - -SYNOPSIS - gcloud alpha bms snapshot-schedule-policies update SNAPSHOT_SCHEDULE_POLICY - [--description=DESCRIPTION] - [--schedule=[CRONTAB_SPEC,RETENTION_COUNT,PREFIX,...]] - [--update-labels=[KEY=VALUE,...]] - [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] - -DESCRIPTION - (ALPHA) Update a Bare Metal Solution snapshot schedule policy. - -EXAMPLES - To update an existing policy called my-policy with new description - my-description and replace any existing schedules with one that runs every - 12 hours, run: - - $ gcloud alpha bms snapshot-schedule-policies update my-policy \ - --description=my-description \ - --schedule="crontab_spec=0 */12 * * \ - *,retention_count=10,prefix=example" - - To add the label 'key1=value1' to a policy, run: - - $ gcloud alpha bms snapshot-schedule-policies update my-policy \ - --update-labels=key1=value1 - - To clear all labels, run: - - $ gcloud alpha bms snapshot-schedule-policies update my-policy \ - --clear-labels - -POSITIONAL ARGUMENTS - Snapshot schedule policy resource - snapshot_schedule_policy. 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 snapshot_schedule_policy 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 region - attribute: - ◆ provide the argument snapshot_schedule_policy on the command line - with a fully specified name; - ◆ global is the only supported location. - - This must be specified. - - SNAPSHOT_SCHEDULE_POLICY - ID of the snapshot_schedule_policy or fully qualified identifier for - the snapshot_schedule_policy. To set the snapshot_schedule_policy - attribute: - ▸ provide the argument snapshot_schedule_policy on the command - line. - -FLAGS - --description=DESCRIPTION - Textual description of the policy. - - --schedule=[CRONTAB_SPEC,RETENTION_COUNT,PREFIX,...] - Adds a schedule for taking snapshots of volumes under this policy. This - flag may be repeated to specify up to 5 schedules. - - crontab_spec - Specification of the times at which snapshots will be taken. This - should be in Crontab format: - http://en.wikipedia.org/wiki/Cron#Overview - - retention_count - The maximum number of snapshots to retain in this schedule. - - prefix - Value to append to the name of snapshots created by this schedule. - - --update-labels=[KEY=VALUE,...] - List of label KEY=VALUE pairs to update. If a label exists, its value - is modified. Otherwise, a new label is created. - - Keys must start with a lowercase character and contain only hyphens - (-), underscores (_), lowercase characters, and numbers. Values must - contain only hyphens (-), underscores (_), lowercase characters, and - numbers. - - At most one of these can be specified: - - --clear-labels - Remove all labels. If --update-labels is also specified then - --clear-labels is applied first. - - For example, to remove all labels: - - $ gcloud alpha bms snapshot-schedule-policies update --clear-labels - - To remove all existing labels and create two new labels, foo and baz: - - $ gcloud alpha bms snapshot-schedule-policies update \ - --clear-labels --update-labels foo=bar,baz=qux - - --remove-labels=[KEY,...] - List of label keys to remove. If a label does not exist it is - silently ignored. If --update-labels is also specified then - --update-labels is applied first. - -GCLOUD WIDE FLAGS - These flags are available to all commands: --access-token-file, --account, - --billing-project, --configuration, --flags-file, --flatten, --format, - --help, --impersonate-service-account, --log-http, --project, --quiet, - --trace-token, --user-output-enabled, --verbosity. - - Run $ gcloud help for details. - -NOTES - This command is currently in alpha and might change without notice. If this - command fails with API permission errors despite specifying the correct - project, you might be trying to access an API with an invitation-only early - access allowlist. - diff --git a/gcloud/alpha/compute/commitments/create b/gcloud/alpha/compute/commitments/create index 9881d0aa1..53d502ee4 100644 --- a/gcloud/alpha/compute/commitments/create +++ b/gcloud/alpha/compute/commitments/create @@ -5,7 +5,8 @@ SYNOPSIS gcloud alpha compute commitments create COMMITMENT --plan=PLAN (--resources=[local-ssd=LOCAL-SSD],[memory=MEMORY],[vcpu=VCPU] --resources-accelerator=[count=COUNT],[type=TYPE]) [--auto-renew] - [--region=REGION] [--type=TYPE; default="general-purpose"] + [--region=REGION] [--split-source-commitment=SPLIT_SOURCE_COMMITMENT] + [--type=TYPE; default="general-purpose"] [--reservations-from-file=RESERVATIONS_FROM_FILE | [--reservation=RESERVATION : --reservation-zone=RESERVATION_ZONE --accelerator=[count=COUNT],[type=TYPE] @@ -84,6 +85,9 @@ OPTIONAL FLAGS Alternatively, the region can be stored in the environment variable CLOUDSDK_COMPUTE_REGION. + --split-source-commitment=SPLIT_SOURCE_COMMITMENT + Split the resources of previous commitment into a new commitment. + --type=TYPE; default="general-purpose" Type of commitment. memory-optimized indicates that the commitment is for memory-optimized VMs. TYPE must be one of: accelerator-optimized, diff --git a/gcloud/alpha/compute/disks/help b/gcloud/alpha/compute/disks/help index 06b9e94dc..82928ebb3 100644 --- a/gcloud/alpha/compute/disks/help +++ b/gcloud/alpha/compute/disks/help @@ -72,6 +72,10 @@ COMMANDS snapshot (ALPHA) Create snapshots of Compute Engine persistent disks. + start-async-replication + (ALPHA) Start asynchronous replication on a Compute Engine persistent + disk. + stop-async-replication (ALPHA) Stop async replication on a Compute Engine persistent disk. diff --git a/gcloud/alpha/compute/disks/snapshot b/gcloud/alpha/compute/disks/snapshot index 2d702d732..89bc30790 100644 --- a/gcloud/alpha/compute/disks/snapshot +++ b/gcloud/alpha/compute/disks/snapshot @@ -67,8 +67,7 @@ FLAGS --guest-flush Create an application-consistent snapshot by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/alpha/compute/disks/start-async-replication b/gcloud/alpha/compute/disks/start-async-replication new file mode 100644 index 000000000..0c10ffaa9 --- /dev/null +++ b/gcloud/alpha/compute/disks/start-async-replication @@ -0,0 +1,104 @@ +NAME + gcloud alpha compute disks start-async-replication - start asynchronous + replication on a Compute Engine persistent disk + +SYNOPSIS + gcloud alpha compute disks start-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 ...] + +DESCRIPTION + (ALPHA) gcloud alpha compute disks start-async-replication starts async + replication on a Compute Engine persistent disk. This command must be + invoked on the primary disk and --secondary-disk must be provided. + +EXAMPLES + Replication can only be started from the primary scope. To start + replication from the primary disk 'my-disk-1' in zone us-east1-a to the + secondary disk 'my-disk-2' in zone us-west1-a: + + $ gcloud alpha compute disks start-async-replication my-disk-1 \ + --zone=us-east1-a --secondary-disk=my-disk-2 \ + --secondary-disk-zone=us-west1-a + +POSITIONAL ARGUMENTS + DISK_NAME + Name of the disk to operate on. + +REQUIRED FLAGS + --secondary-disk=SECONDARY_DISK + Secondary disk for asynchronous replication. This flag is required when + starting replication. It is also required when stopping replication on + the primary disk. It must not be used when stopping replication on the + secondary disk. + +OPTIONAL FLAGS + At most one of these can be specified: + + --region=REGION + Region of the disk to operate on. If not specified, you might be + prompted to select a region (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/region property: + + $ gcloud config set compute/region REGION + + A list of regions can be fetched by running: + + $ gcloud compute regions list + + To unset the property, run: + + $ gcloud config unset compute/region + + Alternatively, the region can be stored in the environment variable + CLOUDSDK_COMPUTE_REGION. + + --zone=ZONE + Zone of the disk to operate on. If not specified and the compute/zone + property isn't set, you might be prompted to select a zone + (interactive mode only). + + To avoid prompting when this flag is omitted, you can set the + compute/zone property: + + $ gcloud config set compute/zone ZONE + + A list of zones can be fetched by running: + + $ gcloud compute zones list + + To unset the property, run: + + $ gcloud config unset compute/zone + + Alternatively, the zone can be stored in the environment variable + CLOUDSDK_COMPUTE_ZONE. + + At most one of these can be specified: + + --secondary-disk-region=SECONDARY_DISK_REGION + Region of the secondary disk for asynchronous replication. Overrides + the default compute/region property value for this command + invocation. + + --secondary-disk-zone=SECONDARY_DISK_ZONE + Zone of the secondary disk for asynchronous replication. Overrides + the default compute/zone 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/compute/forwarding-rules/create b/gcloud/alpha/compute/forwarding-rules/create index 64a14aca2..9c963e7c7 100644 --- a/gcloud/alpha/compute/forwarding-rules/create +++ b/gcloud/alpha/compute/forwarding-rules/create @@ -14,8 +14,8 @@ SYNOPSIS | --target-ssl-proxy=TARGET_SSL_PROXY | --target-tcp-proxy=TARGET_TCP_PROXY | --target-vpn-gateway=TARGET_VPN_GATEWAY) [--allow-global-access] - [--description=DESCRIPTION] [--ip-protocol=IP_PROTOCOL] - [--is-mirroring-collector] + [--allow-psc-global-access] [--description=DESCRIPTION] + [--ip-protocol=IP_PROTOCOL] [--is-mirroring-collector] [--load-balancing-scheme=LOAD_BALANCING_SCHEME] [--network=NETWORK] [--network-tier=NETWORK_TIER] [--service-directory-registration=SERVICE_DIRECTORY_REGISTRATION] @@ -171,6 +171,12 @@ OPTIONAL FLAGS the LOAD_BALANCING_SCHEME set to INTERNAL and the target must be either a backend service or a target instance. + --allow-psc-global-access + If specified, then clients from all regions can access this Private + Service Connect forwarding rule. This can only be specified if the + forwarding rule's target is a service attachment + (--target-service-attachment). + --description=DESCRIPTION Optional textual description for the forwarding rule. diff --git a/gcloud/alpha/compute/instances/create b/gcloud/alpha/compute/instances/create index 0c564be08..b55db3ab4 100644 --- a/gcloud/alpha/compute/instances/create +++ b/gcloud/alpha/compute/instances/create @@ -58,6 +58,10 @@ SYNOPSIS [--image-family-scope=IMAGE_FAMILY_SCOPE --image-project=IMAGE_PROJECT --image=IMAGE | --image-family=IMAGE_FAMILY | --source-snapshot=SOURCE_SNAPSHOT] + [--instance-kms-key=INSTANCE_KMS_KEY + : --instance-kms-keyring=INSTANCE_KMS_KEYRING + --instance-kms-location=INSTANCE_KMS_LOCATION + --instance-kms-project=INSTANCE_KMS_PROJECT] [--maintenance-policy=MAINTENANCE_POLICY | --on-host-maintenance=MAINTENANCE_POLICY] [--network-interface=[PROPERTY=VALUE,...] @@ -945,6 +949,37 @@ FLAGS ▸ https://compute.googleapis.com/compute/v1/projects/myproject/global/snapshots/snapshot ▸ snapshot + Key resource - The Cloud KMS (Key Management Service) cryptokey that will + be used to protect the instance. The arguments in this group can be used + to specify the attributes of this resource. + + --instance-kms-key=INSTANCE_KMS_KEY + ID of the key or fully qualified identifier for the key. To set the + kms-key attribute: + ▸ provide the argument --instance-kms-key on the command line. + + This flag must be specified if any of the other arguments in this + group are specified. + + --instance-kms-keyring=INSTANCE_KMS_KEYRING + The KMS keyring of the key. To set the kms-keyring attribute: + ▸ provide the argument --instance-kms-key on the command line with + a fully specified name; + ▸ provide the argument --instance-kms-keyring on the command line. + + --instance-kms-location=INSTANCE_KMS_LOCATION + The Cloud location for the key. To set the kms-location attribute: + ▸ provide the argument --instance-kms-key on the command line with + a fully specified name; + ▸ provide the argument --instance-kms-location on the command line. + + --instance-kms-project=INSTANCE_KMS_PROJECT + The Cloud project for the key. To set the kms-project attribute: + ▸ provide the argument --instance-kms-key on the command line with + a fully specified name; + ▸ provide the argument --instance-kms-project on the command line; + ▸ set the property core/project. + Maintenance Behavior. At most one of these can be specified: diff --git a/gcloud/alpha/compute/machine-images/create b/gcloud/alpha/compute/machine-images/create index 97fe6889d..fcdc6adf2 100644 --- a/gcloud/alpha/compute/machine-images/create +++ b/gcloud/alpha/compute/machine-images/create @@ -47,8 +47,7 @@ OPTIONAL FLAGS --guest-flush Create an application-consistent machine image by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --require-csek-key-create Refuse to create machine images not protected by a user managed key in diff --git a/gcloud/alpha/compute/machine-images/import b/gcloud/alpha/compute/machine-images/import index 3c2e49a28..d7e42ff2c 100644 --- a/gcloud/alpha/compute/machine-images/import +++ b/gcloud/alpha/compute/machine-images/import @@ -118,8 +118,7 @@ OPTIONAL FLAGS --guest-flush Create an application-consistent machine image by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --guest-os-features=[GUEST_OS_FEATURE,...] This parameter enables one or more features for VM instances that use diff --git a/gcloud/alpha/config/help b/gcloud/alpha/config/help index 4f00791a4..d16730673 100644 --- a/gcloud/alpha/config/help +++ b/gcloud/alpha/config/help @@ -104,6 +104,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/alpha/config/list b/gcloud/alpha/config/list index 80bd08bbb..edb808c32 100644 --- a/gcloud/alpha/config/list +++ b/gcloud/alpha/config/list @@ -109,6 +109,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/alpha/config/set b/gcloud/alpha/config/set index 19030c768..3c24ac016 100644 --- a/gcloud/alpha/config/set +++ b/gcloud/alpha/config/set @@ -122,6 +122,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/alpha/config/unset b/gcloud/alpha/config/unset index 988c3a95a..285890047 100644 --- a/gcloud/alpha/config/unset +++ b/gcloud/alpha/config/unset @@ -83,6 +83,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/alpha/container/binauthz/attestors/public-keys/add b/gcloud/alpha/container/binauthz/attestors/public-keys/add index c34cc4ac3..0c11aa52e 100644 --- a/gcloud/alpha/container/binauthz/attestors/public-keys/add +++ b/gcloud/alpha/container/binauthz/attestors/public-keys/add @@ -112,7 +112,9 @@ REQUIRED FLAGS ecdsa-p384-sha384, ecdsa-p521-sha512, rsa-pss-2048-sha256, rsa-pss-3072-sha256, rsa-pss-4096-sha256, rsa-pss-4096-sha512, rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512. + rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, + rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, + rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512. This flag must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/alpha/container/fleet/cloudrun/apply b/gcloud/alpha/container/fleet/cloudrun/apply new file mode 100644 index 000000000..40fe7ebd2 --- /dev/null +++ b/gcloud/alpha/container/fleet/cloudrun/apply @@ -0,0 +1,76 @@ +NAME + gcloud alpha container fleet cloudrun apply - deploy or update the CloudRun + feature + +SYNOPSIS + gcloud alpha container fleet cloudrun apply + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [--config=CONFIG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Deploy or update a user-specified config file of the CloudRun + custom resource. The config file should be a YAML file. + +EXAMPLES + To apply the CloudRun YAML file, run: + + $ gcloud alpha container fleet cloudrun apply \ + --kubeconfig=/path/to/kubeconfig \ + --config=/path/to/cloud-run-cr.yaml + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + +OPTIONAL FLAGS + --config=CONFIG + The path to CloudRun custom resource config file. + +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. These variants are also available: + + $ gcloud container fleet cloudrun apply + + $ gcloud beta container fleet cloudrun apply + diff --git a/gcloud/alpha/container/fleet/cloudrun/describe b/gcloud/alpha/container/fleet/cloudrun/describe new file mode 100644 index 000000000..35f53d5c5 --- /dev/null +++ b/gcloud/alpha/container/fleet/cloudrun/describe @@ -0,0 +1,31 @@ +NAME + gcloud alpha container fleet cloudrun describe - describe the status of the + CloudRun feature + +SYNOPSIS + gcloud alpha container fleet cloudrun describe [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To get the detailed current status of the CloudRun Feature in Anthos + clusters, run: + + $ gcloud alpha container fleet cloudrun describe + +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. These variants are also available: + + $ gcloud container fleet cloudrun describe + + $ gcloud beta container fleet cloudrun describe + diff --git a/gcloud/alpha/container/fleet/cloudrun/disable b/gcloud/alpha/container/fleet/cloudrun/disable new file mode 100644 index 000000000..ae57dac41 --- /dev/null +++ b/gcloud/alpha/container/fleet/cloudrun/disable @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet cloudrun disable - disable the CloudRun + feature + +SYNOPSIS + gcloud alpha container fleet cloudrun disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command disables the CloudRun feature in Anthos clusters. + +EXAMPLES + To disable the CloudRun Feature, run: + + $ gcloud alpha container fleet cloudrun disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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. These variants are also available: + + $ gcloud container fleet cloudrun disable + + $ gcloud beta container fleet cloudrun disable + diff --git a/gcloud/alpha/container/fleet/cloudrun/enable b/gcloud/alpha/container/fleet/cloudrun/enable new file mode 100644 index 000000000..c01bd6df9 --- /dev/null +++ b/gcloud/alpha/container/fleet/cloudrun/enable @@ -0,0 +1,32 @@ +NAME + gcloud alpha container fleet cloudrun enable - enable the CloudRun feature + +SYNOPSIS + gcloud alpha container fleet cloudrun enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command enables the CloudRun feature in Anthos clusters. + +EXAMPLES + To enable the CloudRun Feature, run: + + $ gcloud alpha container fleet cloudrun enable + +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. These variants are also available: + + $ gcloud container fleet cloudrun enable + + $ gcloud beta container fleet cloudrun enable + diff --git a/gcloud/alpha/container/fleet/cloudrun/help b/gcloud/alpha/container/fleet/cloudrun/help new file mode 100644 index 000000000..25b6c8b3a --- /dev/null +++ b/gcloud/alpha/container/fleet/cloudrun/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet cloudrun - manage the CloudRun feature + +SYNOPSIS + gcloud alpha container fleet cloudrun COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage the CloudRun feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + (ALPHA) Deploy or update the CloudRun feature. + + describe + (ALPHA) Describe the status of the CloudRun feature. + + disable + (ALPHA) Disable the CloudRun feature. + + enable + (ALPHA) Enable the CloudRun feature. + +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. These variants are also available: + + $ gcloud container fleet cloudrun + + $ gcloud beta container fleet cloudrun + diff --git a/gcloud/alpha/container/fleet/config-management/apply b/gcloud/alpha/container/fleet/config-management/apply new file mode 100644 index 000000000..77fc48f1e --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/apply @@ -0,0 +1,50 @@ +NAME + gcloud alpha container fleet config-management apply - update a Config + Management Feature Spec + +SYNOPSIS + gcloud alpha container fleet config-management apply --config=CONFIG + [--membership=MEMBERSHIP] [--version=VERSION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update a user-specified config file to a ConfigManagement Custom + Resource. The config file should be a .yaml file, all eligible fields are + listed in + https://cloud.google.com/anthos-config-management/docs/reference/gcloud-apply-fields + +EXAMPLES + To apply a YAML config file to a membership, prepare apply-spec.yaml + (https://cloud.google.com/anthos-config-management/docs/reference/gcloud-apply-fields#example_gcloud_apply_spec) + then run: + + $ gcloud alpha container fleet config-management apply \ + --membership=CLUSTER_NAME --config=APPLY-SPEC.YAML \ + --version=VERSION + +REQUIRED FLAGS + --config=CONFIG + The path to config-management.yaml. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + + --version=VERSION + The version of ACM to install. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management apply + diff --git a/gcloud/alpha/container/fleet/config-management/delete b/gcloud/alpha/container/fleet/config-management/delete new file mode 100644 index 000000000..e451aa488 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/delete @@ -0,0 +1,41 @@ +NAME + gcloud alpha container fleet config-management delete - remove the Config + Management Feature Spec for the given membership + +SYNOPSIS + gcloud alpha container fleet config-management delete + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) (DEPRECATED) Remove the Config Management Feature Spec for the + given membership. + + This command has been deprecated. Please use unmanage instead. + + Remove the Config Management Feature Spec for the given membership. The + existing ConfigManagement resources in the clusters will become unmanaged. + +EXAMPLES + To remove the Config Management Feature spec for a Membership, run: + + $ gcloud alpha container fleet config-management delete \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +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/container/fleet/config-management/disable b/gcloud/alpha/container/fleet/config-management/disable new file mode 100644 index 000000000..ec379a668 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/disable @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet config-management disable - disable Config + Management Feature + +SYNOPSIS + gcloud alpha container fleet config-management disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disable the Config Management Feature in a fleet. + +EXAMPLES + To disable the Config Management Feature, run: + + $ gcloud alpha container fleet config-management disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management disable + diff --git a/gcloud/alpha/container/fleet/config-management/enable b/gcloud/alpha/container/fleet/config-management/enable new file mode 100644 index 000000000..fe738a2c3 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/enable @@ -0,0 +1,32 @@ +NAME + gcloud alpha container fleet config-management enable - enable Config + Management Feature + +SYNOPSIS + gcloud alpha container fleet config-management enable + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enables the Config Management Feature in a fleet. + +EXAMPLES + To enable the Config Management Feature, run: + + $ gcloud alpha container fleet config-management enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management enable + diff --git a/gcloud/alpha/container/fleet/config-management/fetch-for-apply b/gcloud/alpha/container/fleet/config-management/fetch-for-apply new file mode 100644 index 000000000..6f531fe1e --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/fetch-for-apply @@ -0,0 +1,35 @@ +NAME + gcloud alpha container fleet config-management fetch-for-apply - prints the + Config Management configuration applied to the given membership + +SYNOPSIS + gcloud alpha container fleet config-management fetch-for-apply + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The output is in the format that is used by the apply subcommand. + The fields that have not been configured will be shown with default values. + +EXAMPLES + To fetch the applied Config Management configuration, run: + + $ gcloud alpha container fleet config-management fetch-for-apply + +FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +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/container/fleet/config-management/help b/gcloud/alpha/container/fleet/config-management/help new file mode 100644 index 000000000..0e331a654 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/help @@ -0,0 +1,59 @@ +NAME + gcloud alpha container fleet config-management - manage Config Management + Feature + +SYNOPSIS + gcloud alpha container fleet config-management COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Config Management Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + (ALPHA) Update a Config Management Feature Spec. + + delete + (ALPHA) (DEPRECATED) Remove the Config Management Feature Spec for the + given membership. + + disable + (ALPHA) Disable Config Management Feature. + + enable + (ALPHA) Enable Config Management Feature. + + fetch-for-apply + (ALPHA) Prints the Config Management configuration applied to the given + membership. + + status + (ALPHA) Print the status of all clusters with Config Management + enabled. + + unmanage + (ALPHA) Remove the Config Management Feature Spec for the given + membership. + + upgrade + (ALPHA) Upgrade the version of the Config Management Feature. + + version + (ALPHA) Print the version of all clusters with Config Management + enabled. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management + diff --git a/gcloud/alpha/container/fleet/config-management/status b/gcloud/alpha/container/fleet/config-management/status new file mode 100644 index 000000000..b41b8d8e7 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/status @@ -0,0 +1,91 @@ +NAME + gcloud alpha container fleet config-management status - print the status of + all clusters with Config Management enabled + +SYNOPSIS + gcloud alpha container fleet config-management status [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Print the status of all clusters with Config Management enabled. + +EXAMPLES + Print the status of the Config Management Feature: + + $ gcloud alpha container fleet config-management status + + Name Status Last_Synced_Token Sync_Branch Last_Synced_Time Hierarchy_Controller + managed-cluster SYNCED 2945500b7f acme 2020-03-23 + 11:12:31 -0700 PDT INSTALLED + + View the status for the cluster named managed-cluster-a: + + $ gcloud alpha container fleet config-management status \ + --filter="acm_status.name:managed-cluster-a" + + Use a regular expression to list status for multiple clusters: + + $ gcloud alpha container fleet config-management status \ + --filter="acm_status.name ~ managed-cluster.*" + + List all clusters where current status is SYNCED: + + $ gcloud alpha container fleet config-management status \ + --filter="acm_status.config_sync:SYNCED" + + List all the clusters where sync_branch is v1 and current Config Sync + status is not SYNCED: + + $ gcloud alpha container fleet config-management status \ + --filter="acm_status.sync_branch:v1 AND \ + -acm_status.config_sync:SYNCED" + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management status + diff --git a/gcloud/alpha/container/fleet/config-management/unmanage b/gcloud/alpha/container/fleet/config-management/unmanage new file mode 100644 index 000000000..270156aee --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/unmanage @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet config-management unmanage - remove the Config + Management Feature Spec for the given membership + +SYNOPSIS + gcloud alpha container fleet config-management unmanage + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Remove the Config Management Feature Spec for the given membership. + The existing ConfigManagement resources in the clusters will become + unmanaged. + +EXAMPLES + To remove the Config Management Feature spec for a Membership, run: + + $ gcloud alpha container fleet config-management unmanage \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management unmanage + diff --git a/gcloud/alpha/container/fleet/config-management/upgrade b/gcloud/alpha/container/fleet/config-management/upgrade new file mode 100644 index 000000000..4e46bb215 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/upgrade @@ -0,0 +1,42 @@ +NAME + gcloud alpha container fleet config-management upgrade - upgrade the + version of the Config Management Feature + +SYNOPSIS + gcloud alpha container fleet config-management upgrade --version=VERSION + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Upgrade a specified membership to any supported version of the + Config Management Feature. + +EXAMPLES + To upgrade a membership named CLUSTER_NAME, run: + + $ gcloud alpha container fleet config-management upgrade \ + --membership=CLUSTER_NAME --version=VERSION + +REQUIRED FLAGS + --version=VERSION + The version of ACM to change to. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management upgrade + diff --git a/gcloud/alpha/container/fleet/config-management/version b/gcloud/alpha/container/fleet/config-management/version new file mode 100644 index 000000000..d43dacd45 --- /dev/null +++ b/gcloud/alpha/container/fleet/config-management/version @@ -0,0 +1,62 @@ +NAME + gcloud alpha container fleet config-management version - print the version + of all clusters with Config Management enabled + +SYNOPSIS + gcloud alpha container fleet config-management version + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To print the version of all clusters with Config Management enabled, run: + + $ gcloud alpha container fleet config-management version + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet config-management version + diff --git a/gcloud/alpha/container/fleet/features/help b/gcloud/alpha/container/fleet/features/help new file mode 100644 index 000000000..1fefdd5d0 --- /dev/null +++ b/gcloud/alpha/container/fleet/features/help @@ -0,0 +1,32 @@ +NAME + gcloud alpha container fleet features - manage Hub Feature resources + +SYNOPSIS + gcloud alpha container fleet features COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) These commands manage Features generically. Most Features offer + specialized commands under dedicated sub-groups that may be more effective + for that specific Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (ALPHA) List enabled features. + +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. These variants are also available: + + $ gcloud container fleet features + + $ gcloud beta container fleet features + diff --git a/gcloud/alpha/container/fleet/features/list b/gcloud/alpha/container/fleet/features/list new file mode 100644 index 000000000..ee8750063 --- /dev/null +++ b/gcloud/alpha/container/fleet/features/list @@ -0,0 +1,89 @@ +NAME + gcloud alpha container fleet features list - list enabled features + +SYNOPSIS + gcloud alpha container fleet features list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List enabled Hub features in a project. + +EXAMPLES + To list all enabled Hub features in a project, run: + + $ gcloud alpha container fleet features list + +FLAGS + Location resource - The location to list Features under. + + 'global' is the only supported value. 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; + ◆ global is the only supported location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --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; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1alpha API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-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. These variants are also available: + + $ gcloud container fleet features list + + $ gcloud beta container fleet features list + diff --git a/gcloud/alpha/container/fleet/help b/gcloud/alpha/container/fleet/help new file mode 100644 index 000000000..260584ae0 --- /dev/null +++ b/gcloud/alpha/container/fleet/help @@ -0,0 +1,85 @@ +NAME + gcloud alpha container fleet - centrally manage features and services on + all your Kubernetes clusters with fleet + +SYNOPSIS + gcloud alpha container fleet GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) The command group to register GKE or other Kubernetes clusters + running in a variety of environments, including Google cloud, on premises + in customer datacenters, or other third party clouds with fleet. Fleet + provides a centralized control-plane to managed features and services on + all registered clusters. + + A registered cluster is always associated with a Membership, a resource + within fleet. + +EXAMPLES + Manage memberships of all your GKE and other Kubernetes clusters with + fleet: + + $ gcloud alpha container fleet memberships --help + + Manage Config Management feature on all memberships: + + $ gcloud alpha container fleet config-management --help + + Manage Multi-cluster Ingress feature on all memberships: + + $ gcloud alpha container fleet ingress --help + + Manage Multi-cluster Services feature on all memberships: + + $ gcloud alpha container fleet multi-cluster-services --help + + Manage CloudRun feature on all memberships: + + $ gcloud alpha container fleet cloudrun --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + cloudrun + (ALPHA) Manage the CloudRun feature. + + config-management + (ALPHA) Manage Config Management Feature. + + features + (ALPHA) Manage Hub Feature resources. + + identity-service + (ALPHA) Manage Identity Service Feature. + + ingress + (ALPHA) Manage Multi-cluster Ingress Feature. + + memberships + (ALPHA) Manage memberships of all your GKE and other Kubernetes cluster + with Fleet. + + mesh + (ALPHA) Manage Service Mesh Feature. + + multi-cluster-services + (ALPHA) Manage Multi-cluster Services Feature. + + service-directory + (ALPHA) Manage the Service Directory Feature. + +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. These variants are also available: + + $ gcloud container fleet + + $ gcloud beta container fleet + diff --git a/gcloud/alpha/container/fleet/identity-service/apply b/gcloud/alpha/container/fleet/identity-service/apply new file mode 100644 index 000000000..72a5cac7a --- /dev/null +++ b/gcloud/alpha/container/fleet/identity-service/apply @@ -0,0 +1,47 @@ +NAME + gcloud alpha container fleet identity-service apply - update an Identity + Service Feature Spec + +SYNOPSIS + gcloud alpha container fleet identity-service apply --config=CONFIG + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Applies the authentication configuration to the Identity Service + feature spec for this membership. This configuration is now the "source of + truth" for the cluster and can only be updated by using this command or the + Cloud Console. Any local authentication configuration on the cluster is + overwritten by this configuration, including any local updates made after + you run this command. + +EXAMPLES + To apply an Identity Service configuration for a membership, run: + + $ gcloud alpha container fleet identity-service apply \ + --membership=CLUSTER_NAME \ + --config=/path/to/identity-service.yaml + +REQUIRED FLAGS + --config=CONFIG + The path to the identity-service.yaml config file. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet identity-service apply + diff --git a/gcloud/alpha/container/fleet/identity-service/delete b/gcloud/alpha/container/fleet/identity-service/delete new file mode 100644 index 000000000..4382822eb --- /dev/null +++ b/gcloud/alpha/container/fleet/identity-service/delete @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet identity-service delete - remove the Identity + Service Feature Spec for the given membership + +SYNOPSIS + gcloud alpha container fleet identity-service delete + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Removes the Identity Service Feature Spec for the given membership. + +EXAMPLES + To delete an Identity Service configuration for a membership, run: + + $ gcloud alpha container fleet identity-service delete \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + Membership name provided during registration. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet identity-service delete + diff --git a/gcloud/alpha/container/fleet/identity-service/describe b/gcloud/alpha/container/fleet/identity-service/describe new file mode 100644 index 000000000..3df5396cb --- /dev/null +++ b/gcloud/alpha/container/fleet/identity-service/describe @@ -0,0 +1,66 @@ +NAME + gcloud alpha container fleet identity-service describe - prints the status + of all clusters with Identity Service installed + +SYNOPSIS + gcloud alpha container fleet identity-service describe + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Prints the status of the Identity Service Feature resource in a + fleet. + +EXAMPLES + To describe the status of the Identity Service configuration, run: + + $ gcloud alpha container fleet identity-service describe + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet identity-service describe + diff --git a/gcloud/alpha/container/fleet/identity-service/disable b/gcloud/alpha/container/fleet/identity-service/disable new file mode 100644 index 000000000..cc23e6c00 --- /dev/null +++ b/gcloud/alpha/container/fleet/identity-service/disable @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet identity-service disable - disable Identity + Service Feature + +SYNOPSIS + gcloud alpha container fleet identity-service disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command disables the Identity Service Feature in a fleet. + +EXAMPLES + To disable the Identity Service Feature, run: + + $ gcloud alpha container fleet identity-service disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet identity-service disable + diff --git a/gcloud/alpha/container/fleet/identity-service/enable b/gcloud/alpha/container/fleet/identity-service/enable new file mode 100644 index 000000000..09130999c --- /dev/null +++ b/gcloud/alpha/container/fleet/identity-service/enable @@ -0,0 +1,31 @@ +NAME + gcloud alpha container fleet identity-service enable - enable Identity + Service Feature + +SYNOPSIS + gcloud alpha container fleet identity-service enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command enables the Identity Service Feature in a fleet. + +EXAMPLES + To enable the Identity Service Feature, run: + + $ gcloud alpha container fleet identity-service enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet identity-service enable + diff --git a/gcloud/alpha/container/fleet/identity-service/help b/gcloud/alpha/container/fleet/identity-service/help new file mode 100644 index 000000000..2bef7cf1c --- /dev/null +++ b/gcloud/alpha/container/fleet/identity-service/help @@ -0,0 +1,44 @@ +NAME + gcloud alpha container fleet identity-service - manage Identity Service + Feature + +SYNOPSIS + gcloud alpha container fleet identity-service COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Identity Service Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + (ALPHA) Update an Identity Service Feature Spec. + + delete + (ALPHA) Remove the Identity Service Feature Spec for the given + membership. + + describe + (ALPHA) Prints the status of all clusters with Identity Service + installed. + + disable + (ALPHA) Disable Identity Service Feature. + + enable + (ALPHA) Enable Identity Service Feature. + +NOTES + This command is currently in alpha and might change without notice. If this + command fails with API permission errors despite specifying the correct + project, you might be trying to access an API with an invitation-only early + access allowlist. This variant is also available: + + $ gcloud beta container fleet identity-service + diff --git a/gcloud/alpha/container/fleet/ingress/describe b/gcloud/alpha/container/fleet/ingress/describe new file mode 100644 index 000000000..fab6d2c5b --- /dev/null +++ b/gcloud/alpha/container/fleet/ingress/describe @@ -0,0 +1,34 @@ +NAME + gcloud alpha container fleet ingress describe - describe the status of + Multi-cluster Ingress Feature resource + +SYNOPSIS + gcloud alpha container fleet ingress describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command describes the status of Multi-cluster Ingress Feature + resource in fleet. + +EXAMPLES + To describe the Ingress Feature, run: + + $ gcloud alpha container fleet ingress describe + +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. These variants are also available: + + $ gcloud container fleet ingress describe + + $ gcloud beta container fleet ingress describe + diff --git a/gcloud/alpha/container/fleet/ingress/disable b/gcloud/alpha/container/fleet/ingress/disable new file mode 100644 index 000000000..005f1dacc --- /dev/null +++ b/gcloud/alpha/container/fleet/ingress/disable @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet ingress disable - disable Multi-cluster + Ingress Feature + +SYNOPSIS + gcloud alpha container fleet ingress disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command disables Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To disable the Ingress Feature, run: + + $ gcloud alpha container fleet ingress disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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. These variants are also available: + + $ gcloud container fleet ingress disable + + $ gcloud beta container fleet ingress disable + diff --git a/gcloud/alpha/container/fleet/ingress/enable b/gcloud/alpha/container/fleet/ingress/enable new file mode 100644 index 000000000..1519a8048 --- /dev/null +++ b/gcloud/alpha/container/fleet/ingress/enable @@ -0,0 +1,40 @@ +NAME + gcloud alpha container fleet ingress enable - enable Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud alpha container fleet ingress enable + [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command enables Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To enable the Ingress Feature, run: + + $ gcloud alpha container fleet ingress enable \ + --config-membership=CONFIG_MEMBERSHIP + +FLAGS + --config-membership=CONFIG_MEMBERSHIP + Membership resource representing the cluster which hosts the + MultiClusterIngress and MultiClusterService CustomResourceDefinitions. + +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. These variants are also available: + + $ gcloud container fleet ingress enable + + $ gcloud beta container fleet ingress enable + diff --git a/gcloud/alpha/container/fleet/ingress/help b/gcloud/alpha/container/fleet/ingress/help new file mode 100644 index 000000000..0d2e31196 --- /dev/null +++ b/gcloud/alpha/container/fleet/ingress/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet ingress - manage Multi-cluster Ingress Feature + +SYNOPSIS + gcloud alpha container fleet ingress COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Multi-cluster Ingress Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe the status of Multi-cluster Ingress Feature resource. + + disable + (ALPHA) Disable Multi-cluster Ingress Feature. + + enable + (ALPHA) Enable Multi-cluster Ingress Feature. + + update + (ALPHA) Update Multi-cluster Ingress Feature. + +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. These variants are also available: + + $ gcloud container fleet ingress + + $ gcloud beta container fleet ingress + diff --git a/gcloud/alpha/container/fleet/ingress/update b/gcloud/alpha/container/fleet/ingress/update new file mode 100644 index 000000000..331587c86 --- /dev/null +++ b/gcloud/alpha/container/fleet/ingress/update @@ -0,0 +1,40 @@ +NAME + gcloud alpha container fleet ingress update - update Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud alpha container fleet ingress update + [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command updates Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To update the Ingress Feature, run: + + $ gcloud alpha container fleet ingress update \ + --config-membership=CONFIG_MEMBERSHIP + +FLAGS + --config-membership=CONFIG_MEMBERSHIP + Membership resource representing the cluster which hosts the + MultiClusterIngress and MultiClusterService CustomResourceDefinitions. + +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. These variants are also available: + + $ gcloud container fleet ingress update + + $ gcloud beta container fleet ingress update + diff --git a/gcloud/alpha/container/fleet/memberships/delete b/gcloud/alpha/container/fleet/memberships/delete new file mode 100644 index 000000000..43cc8d021 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/delete @@ -0,0 +1,77 @@ +NAME + gcloud alpha container fleet memberships delete - delete a membership + +SYNOPSIS + gcloud alpha container fleet memberships delete + (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command deletes the Fleet membership resource corresponding to + the cluster. + + This command is intended to delete stale Fleet Membership resources as + doing so on a fully registered cluster will skip uninstalling the Connect + Agent and and orphan in-cluster resources and agent connections to Google. + To completely unregister the cluster, consider using the command: gcloud + alpha container fleet memberships unregister. + +EXAMPLES + Delete a membership from Fleet: + + $ gcloud alpha container fleet memberships delete a-membership + +POSITIONAL ARGUMENTS + Membership resource - The cluster membership 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1alpha2 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-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. These variants are also available: + + $ gcloud container fleet memberships delete + + $ gcloud beta container fleet memberships delete + diff --git a/gcloud/alpha/container/fleet/memberships/describe b/gcloud/alpha/container/fleet/memberships/describe new file mode 100644 index 000000000..a1e4f832b --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/describe @@ -0,0 +1,65 @@ +NAME + gcloud alpha container fleet memberships describe - describe a membership + +SYNOPSIS + gcloud alpha container fleet memberships describe + (MEMBERSHIP : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe a membership in Fleet. + +EXAMPLES + Describe a membership in Fleet: + + $ gcloud alpha container fleet memberships describe a-membership + +POSITIONAL ARGUMENTS + Membership resource - The cluster membership 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1alpha2 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-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. These variants are also available: + + $ gcloud container fleet memberships describe + + $ gcloud beta container fleet memberships describe + diff --git a/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac b/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac new file mode 100644 index 000000000..1524b4ceb --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/generate-gateway-rbac @@ -0,0 +1,118 @@ +NAME + gcloud alpha container fleet memberships generate-gateway-rbac - generate + RBAC policy files for connected clusters by the user + +SYNOPSIS + gcloud alpha container fleet memberships generate-gateway-rbac + [--anthos-support] [--apply] [--context=CONTEXT] + [--kubeconfig=KUBECONFIG] [--membership=MEMBERSHIP] + [--rbac-output-file=RBAC_OUTPUT_FILE] [--revoke] [--role=ROLE] + [--users=USERS] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha container fleet memberships generate-gateway-rbac + generates RBAC policies to be used by Connect Gateway API. + + Upon success, this command will write the output RBAC policy to the + designated local file in dry run mode. + + Override RBAC policy: Y to override previous RBAC policy, N to stop. If + overriding the --role, Y will clean up the previous RBAC policy and then + apply the new one. + +EXAMPLES + The current implementation supports multiple modes: + + Dry run mode to generate the RBAC policy file, and write to local + directory: + + $ gcloud alpha container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --rbac-output-file=./rbac.yaml + + Dry run mode to generate the RBAC policy, and print on screen: + + $ gcloud alpha container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin + + Anthos support mode, generate the RBAC policy file with read-only + permission for TSE/Eng to debug customers' clusters: + + $ gcloud alpha container fleet memberships generate-gateway-rbac \ + --membership=my-cluster --anthos-support + + Apply mode, generate the RBAC policy and apply it to the specified cluster: + + $ gcloud alpha container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --apply + + Revoke mode, revoke the RBAC policy for the specified users: + + $ gcloud alpha container fleet memberships generate-gateway-rbac \ + --membership=my-cluster \ + --users=foo@example.com,\ + test-acct@test-project.iam.gserviceaccount.com \ + --role=clusterrole/cluster-admin --context=my-cluster-contex \ + --kubeconfig=/home/user/custom_kubeconfig --apply + +FLAGS + --anthos-support + If specified, this command will generate RBAC policy file for anthos + support. + + --apply + If specified, this command will generate RBAC policy and apply to the + specified cluster. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can get + this value from the command line by running command: kubectl config + current-context. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults to + $KUBECONFIG if it is set in the environment, otherwise defaults to + $HOME/.kube/config. + + --membership=MEMBERSHIP + Membership name to assign RBAC policy with. + + --rbac-output-file=RBAC_OUTPUT_FILE + If specified, this command will execute in dry run mode and write to + the file specified with this flag: the generated RBAC policy will not + be applied to Kubernetes clusters,instead it will be written to the + designated local file. + + --revoke + If specified, this command will revoke the RBAC policy for the + specified users. + + --role=ROLE + Namespace scoped role or cluster role. + + --users=USERS + User's email address or service account email address. + +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/container/fleet/memberships/get-credentials b/gcloud/alpha/container/fleet/memberships/get-credentials new file mode 100644 index 000000000..b53448805 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/get-credentials @@ -0,0 +1,50 @@ +NAME + gcloud alpha container fleet memberships get-credentials - fetch + credentials for a Fleet-registered cluster to be used in Connect + Gateway + +SYNOPSIS + gcloud alpha container fleet memberships get-credentials MEMBERSHIP + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) gcloud alpha container fleet memberships get-credentials updates + the kubeconfig file with the appropriate credentials and endpoint + information to send kubectl commands to a Fleet-registered and connected + cluster through Connect Gateway Service. + + It takes a project, passed through by set defaults or flags. By default, + credentials are written to $HOME/.kube/config. You can provide an alternate + path by setting the KUBECONFIG environment variable. If KUBECONFIG contains + multiple paths, the first one is used. + + Upon success, this command will switch current context to the target + cluster, when working with multiple clusters. + +EXAMPLES + Get gateway kubeconfig for a registered cluster: + + $ gcloud alpha container fleet memberships get-credentials my-cluster + +POSITIONAL ARGUMENTS + MEMBERSHIP + The membership name used to locate a cluster in your 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 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. These variants are also available: + + $ gcloud container fleet memberships get-credentials + + $ gcloud beta container fleet memberships get-credentials + diff --git a/gcloud/alpha/container/fleet/memberships/help b/gcloud/alpha/container/fleet/memberships/help new file mode 100644 index 000000000..30e9e8a64 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/help @@ -0,0 +1,54 @@ +NAME + gcloud alpha container fleet memberships - manage memberships of all your + GKE and other Kubernetes cluster with Fleet + +SYNOPSIS + gcloud alpha container fleet memberships COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage memberships of all your GKE and other Kubernetes cluster + with Fleet. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (ALPHA) Delete a membership. + + describe + (ALPHA) Describe a membership. + + generate-gateway-rbac + (ALPHA) Generate RBAC policy files for connected clusters by the user. + + get-credentials + (ALPHA) Fetch credentials for a Fleet-registered cluster to be used in + Connect Gateway. + + list + (ALPHA) List memberships. + + register + (ALPHA) Register a cluster with Fleet. + + unregister + (ALPHA) Unregister a cluster from Fleet. + + update + (ALPHA) Update a membership. + +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. These variants are also available: + + $ gcloud container fleet memberships + + $ gcloud beta container fleet memberships + diff --git a/gcloud/alpha/container/fleet/memberships/list b/gcloud/alpha/container/fleet/memberships/list new file mode 100644 index 000000000..26a5c83c2 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/list @@ -0,0 +1,71 @@ +NAME + gcloud alpha container fleet memberships list - list memberships + +SYNOPSIS + gcloud alpha container fleet memberships list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) List memberships in Fleet. + +EXAMPLES + List memberships in Fleet: + + $ gcloud alpha container fleet memberships list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1alpha2 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-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. These variants are also available: + + $ gcloud container fleet memberships list + + $ gcloud beta container fleet memberships list + diff --git a/gcloud/alpha/container/fleet/memberships/register b/gcloud/alpha/container/fleet/memberships/register new file mode 100644 index 000000000..7520ee6bf --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/register @@ -0,0 +1,247 @@ +NAME + gcloud alpha container fleet memberships register - register a cluster with + Fleet + +SYNOPSIS + gcloud alpha container fleet memberships register CLUSTER_NAME + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) + (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE + | [--enable-workload-identity : --has-private-issuer + | --public-issuer-url=PUBLIC_ISSUER_URL]) [--internal-ip] + [--manifest-output-file=MANIFEST_OUTPUT_FILE] [--proxy=PROXY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command registers a cluster with the Fleet by: + + 1. Creating a Fleet Membership resource corresponding to the cluster. + 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive + to one Fleet. + 3. Installing the Connect Agent into this cluster. + + A successful registration implies that the cluster is now exclusive to a + single Fleet. + + For more information about Connect Agent, go to: + https://cloud.google.com/anthos/multicluster-management/connect/overview/ + + To register a non-GKE or GKE On-Prem cluster use --context flag (with an + optional --kubeconfig flag). + + To register a GKE cluster use --gke-cluster or --gke-uri flag (no + --kubeconfig flag is required). + + In all cases, the Connect Agent that is installed in the target cluster + must authenticate to Google using a --service-account-key-file that + corresponds to a service account that has been granted gkehub.connect + permissions. + + If the cluster is already registered to another Fleet, the registration is + not successful. + + Rerunning this command against the same cluster with the same CLUSTER_NAME + and target GKEFleet is successful and upgrades the Connect Agent if a new + agent is available. + +EXAMPLES + Register a non-GKE or GKE On-Prem cluster referenced from a specific + kubeconfig file, and install the Connect Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster referenced from the default + kubeconfig file, and install the Connect Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster, and install a specific version + of the Connect Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster and output a manifest that can be + used to install the Connect Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster referenced from a GKE URI, and install the Connect + Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster referenced from a GKE Cluster location and name, and + install the Connect Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster, and install a specific version of the Connect + Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster and output a manifest that can be used to install + the Connect Agent: + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + + $ gcloud alpha container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + +POSITIONAL ARGUMENTS + CLUSTER_NAME + The membership name that you choose to uniquely represents the cluster + being registered on the Fleet. + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + + Exactly one of these must be specified: + + --service-account-key-file=SERVICE_ACCOUNT_KEY_FILE + The JSON file of a Google Cloud service account private key. This + service account key is stored as a secret named creds-gcp in + gke-connect namespace. To update the creds-gcp secret in gke-connect + namespace with a new service account key file, run the following + command: + + kubectl delete secret creds-gcp -n gke-connect + + kubectl create secret generic creds-gcp -n gke-connect + --from-file=creds-gcp.json=/path/to/file + + Workload Identity + + --enable-workload-identity + Enable Workload Identity when registering the cluster with Fleet. + Ensure that GKE Workload Identity is enabled on your GKE cluster, + it is a requirement for using Workload Identity with memberships. + Refer to the Registering a cluster using Workload Identity section + in + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster#register_cluster + --service_account_key_file flag should not be set if this is set. + + This flag must be specified if any of the other arguments in this + group are specified. + + At most one of these can be specified: + + --has-private-issuer + Set to true for clusters where no publicly-routable OIDC + discovery endpoint for the Kubernetes service account token + issuer exists. + + When set to true, the gcloud command-line tool will read the + private issuer URL and JSON Web Key Set (JWKS) (public keys) for + validating service account tokens from the cluster's API server + and upload both when creating the Membership. Google Cloud + Platform will then use the JWKS, instead of a public OIDC + endpoint, to validate service account tokens issued by this + cluster. Note the JWKS establishes the uniqueness of issuers in + this configuration, but issuer claims in tokens are still + compared to the issuer URL associated with the Membership when + validating tokens. + + Note the cluster's OIDC discovery endpoints (KUBE-API-ADDRESS + (https://)/.well-known/openid-configuration and KUBE-API-ADDRESS + (https://)/openid/v1/jwks) must still be network-accessible to + the gcloud client running this command. + + --public-issuer-url=PUBLIC_ISSUER_URL + Skip auto-discovery and register the cluster with this issuer + URL. Use this option when the OpenID Provider Configuration and + associated JSON Web Key Set for validating the cluster's service + account JWTs are served at a public endpoint different from the + cluster API server. Requires --enable-workload-identity. + +OPTIONAL FLAGS + --internal-ip + Whether to use the internal IP address of the cluster endpoint. + + --manifest-output-file=MANIFEST_OUTPUT_FILE + The full path of the file into which the Connect Agent installation + manifest should be stored. If this option is provided, then the + manifest will be written to this file and will not be deployed into the + cluster by gcloud, and it will need to be deployed manually. + + --proxy=PROXY + The proxy address in the format of http[s]://{hostname}. The proxy must + support the HTTP CONNECT method in order for this connection to + succeed. + +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. These variants are also available: + + $ gcloud container fleet memberships register + + $ gcloud beta container fleet memberships register + diff --git a/gcloud/alpha/container/fleet/memberships/unregister b/gcloud/alpha/container/fleet/memberships/unregister new file mode 100644 index 000000000..bfe1bdd2c --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/unregister @@ -0,0 +1,116 @@ +NAME + gcloud alpha container fleet memberships unregister - unregister a cluster + from Fleet + +SYNOPSIS + gcloud alpha container fleet memberships unregister CLUSTER_NAME + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command unregisters a cluster with the Fleet by: + + 1. Deleting the Fleet Membership resource for this cluster (a.k.a + `gcloud alpha container fleet memberships delete`). + 2. Removing the corresponding in-cluster Kubernetes Resources that make the + cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + membership`). + 3. Uninstalling the Connect Agent from this cluster (a.k.a + `kubectl delete on the gke-connect namespace`). + + The unregister command makes additional internal checks to ensure that all + three steps can be safely done to properly clean-up in-Fleet and in-cluster + resources. + + To register a non-GKE cluster use --context flag (with an optional + --kubeconfig flag). + + To register a GKE cluster use --gke-cluster or --gke-uri flag (no + --kubeconfig flag is required). + + To only delete the Fleet membership resource, consider using the command: + gcloud alpha container fleet memberships delete. This command is intended + to delete stale Fleet Membership resources as doing so on a fully + registered cluster will skip some of the steps above and orphan in-cluster + resources and agent connections to Google. + +EXAMPLES + Unregister a non-GKE cluster referenced from a specific kubeconfig file: + + $ gcloud alpha container fleet memberships unregister \ + my-membership --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig + + Unregister a non-GKE cluster referenced from the default kubeconfig file: + + $ gcloud alpha container fleet memberships unregister \ + my-membership --context=my-cluster-context + + Unregister a GKE cluster referenced from a GKE URI: + + $ gcloud alpha container fleet memberships unregister \ + my-membership --gke-uri=my-cluster-gke-uri + + Unregister a GKE cluster referenced from a GKE Cluster location and name: + + $ gcloud alpha container fleet memberships unregister \ + my-membership --gke-cluster=my-cluster-region-or-zone/my-cluster + +POSITIONAL ARGUMENTS + CLUSTER_NAME + The membership name that corresponds to the cluster being unregistered. + To get list of all the memberships on the Fleet, consider using the + command: gcloud alpha container fleet memberships list. + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + +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. These variants are also available: + + $ gcloud container fleet memberships unregister + + $ gcloud beta container fleet memberships unregister + diff --git a/gcloud/alpha/container/fleet/memberships/update b/gcloud/alpha/container/fleet/memberships/update new file mode 100644 index 000000000..b7b0c7c12 --- /dev/null +++ b/gcloud/alpha/container/fleet/memberships/update @@ -0,0 +1,101 @@ +NAME + gcloud alpha container fleet memberships update - update a membership + +SYNOPSIS + gcloud alpha container fleet memberships update + (MEMBERSHIP : --location=LOCATION) [--async] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update an existing membership in Fleet. + +EXAMPLES + Update a membership for a cluster: + + $ gcloud alpha container fleet memberships update a-membership + +POSITIONAL ARGUMENTS + Membership resource - membership resource representing a cluster in Fleet. + 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud alpha container fleet memberships update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud alpha container fleet memberships update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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 gkehub/v1alpha2 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-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. These variants are also available: + + $ gcloud container fleet memberships update + + $ gcloud beta container fleet memberships update + diff --git a/gcloud/alpha/container/fleet/mesh/describe b/gcloud/alpha/container/fleet/mesh/describe new file mode 100644 index 000000000..24c1722bb --- /dev/null +++ b/gcloud/alpha/container/fleet/mesh/describe @@ -0,0 +1,33 @@ +NAME + gcloud alpha container fleet mesh describe - describe the status of Service + Mesh Feature resource + +SYNOPSIS + gcloud alpha container fleet mesh describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Describe the status of Service Mesh Feature resource in a fleet. + +EXAMPLES + To describe the Service Mesh Feature, run: + + $ gcloud alpha container fleet mesh describe + +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. These variants are also available: + + $ gcloud container fleet mesh describe + + $ gcloud beta container fleet mesh describe + diff --git a/gcloud/alpha/container/fleet/mesh/disable b/gcloud/alpha/container/fleet/mesh/disable new file mode 100644 index 000000000..a4626285a --- /dev/null +++ b/gcloud/alpha/container/fleet/mesh/disable @@ -0,0 +1,37 @@ +NAME + gcloud alpha container fleet mesh disable - disable Service Mesh Feature + +SYNOPSIS + gcloud alpha container fleet mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disable the Service Mesh Feature in a fleet. + +EXAMPLES + To disable the Service Mesh Feature, run: + + $ gcloud alpha container fleet mesh disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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. These variants are also available: + + $ gcloud container fleet mesh disable + + $ gcloud beta container fleet mesh disable + diff --git a/gcloud/alpha/container/fleet/mesh/enable b/gcloud/alpha/container/fleet/mesh/enable new file mode 100644 index 000000000..6c9524db6 --- /dev/null +++ b/gcloud/alpha/container/fleet/mesh/enable @@ -0,0 +1,32 @@ +NAME + gcloud alpha container fleet mesh enable - enable Service Mesh Feature + +SYNOPSIS + gcloud alpha container fleet mesh enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enable the Service Mesh Feature in a fleet. + +EXAMPLES + To enable the Service Mesh Feature, run: + + $ gcloud alpha container fleet mesh enable + +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. These variants are also available: + + $ gcloud container fleet mesh enable + + $ gcloud beta container fleet mesh enable + diff --git a/gcloud/alpha/container/fleet/mesh/help b/gcloud/alpha/container/fleet/mesh/help new file mode 100644 index 000000000..fc0509666 --- /dev/null +++ b/gcloud/alpha/container/fleet/mesh/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet mesh - manage Service Mesh Feature + +SYNOPSIS + gcloud alpha container fleet mesh COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Service Mesh Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe the status of Service Mesh Feature resource. + + disable + (ALPHA) Disable Service Mesh Feature. + + enable + (ALPHA) Enable Service Mesh Feature. + + update + (ALPHA) Update the configuration of the Service Mesh Feature. + +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. These variants are also available: + + $ gcloud container fleet mesh + + $ gcloud beta container fleet mesh + diff --git a/gcloud/alpha/container/fleet/mesh/update b/gcloud/alpha/container/fleet/mesh/update new file mode 100644 index 000000000..53b52524a --- /dev/null +++ b/gcloud/alpha/container/fleet/mesh/update @@ -0,0 +1,41 @@ +NAME + gcloud alpha container fleet mesh update - update the configuration of the + Service Mesh Feature + +SYNOPSIS + gcloud alpha container fleet mesh update --control-plane=CONTROL_PLANE + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Update the Service Mesh Feature Spec of a Membership. + +EXAMPLES + To update the control plane management of a Membership named MEMBERSHIP, + run: + + $ gcloud alpha container fleet mesh update --membership=MEMBERSHIP \ + --control-plane=CONTROL_PLANE + +REQUIRED FLAGS + --control-plane=CONTROL_PLANE + The control plane management to update to. CONTROL_PLANE must be one + of: automatic, manual. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name to update. + +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/container/fleet/multi-cluster-services/describe b/gcloud/alpha/container/fleet/multi-cluster-services/describe new file mode 100644 index 000000000..4b8ebbe26 --- /dev/null +++ b/gcloud/alpha/container/fleet/multi-cluster-services/describe @@ -0,0 +1,35 @@ +NAME + gcloud alpha container fleet multi-cluster-services describe - describe the + status of the Multi-cluster Services Feature resource + +SYNOPSIS + gcloud alpha container fleet multi-cluster-services describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command gets the detailed status of the Multi-cluster Services + Feature in a fleet. + +EXAMPLES + To describe the Multi-cluster Services Feature, run: + + $ gcloud alpha container fleet multi-cluster-services describe + +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. These variants are also available: + + $ gcloud container fleet multi-cluster-services describe + + $ gcloud beta container fleet multi-cluster-services describe + diff --git a/gcloud/alpha/container/fleet/multi-cluster-services/disable b/gcloud/alpha/container/fleet/multi-cluster-services/disable new file mode 100644 index 000000000..712ad573a --- /dev/null +++ b/gcloud/alpha/container/fleet/multi-cluster-services/disable @@ -0,0 +1,40 @@ +NAME + gcloud alpha container fleet multi-cluster-services disable - disable the + Multi-cluster Services Feature + +SYNOPSIS + gcloud alpha container fleet multi-cluster-services disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command disables the Multi-cluster Services Feature in a + fleet. + +EXAMPLES + To disable the Multi-cluster Services Feature, run: + + $ gcloud alpha container fleet multi-cluster-services disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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. These variants are also available: + + $ gcloud container fleet multi-cluster-services disable + + $ gcloud beta container fleet multi-cluster-services disable + diff --git a/gcloud/alpha/container/fleet/multi-cluster-services/enable b/gcloud/alpha/container/fleet/multi-cluster-services/enable new file mode 100644 index 000000000..5168c33fb --- /dev/null +++ b/gcloud/alpha/container/fleet/multi-cluster-services/enable @@ -0,0 +1,34 @@ +NAME + gcloud alpha container fleet multi-cluster-services enable - enable the + Multi-cluster Services Feature + +SYNOPSIS + gcloud alpha container fleet multi-cluster-services enable + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command enables the Multi-cluster Services Feature in a fleet. + +EXAMPLES + To enable the Multi-cluster Services Feature, run: + + $ gcloud alpha container fleet multi-cluster-services enable + +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. These variants are also available: + + $ gcloud container fleet multi-cluster-services enable + + $ gcloud beta container fleet multi-cluster-services enable + diff --git a/gcloud/alpha/container/fleet/multi-cluster-services/help b/gcloud/alpha/container/fleet/multi-cluster-services/help new file mode 100644 index 000000000..e1c60f952 --- /dev/null +++ b/gcloud/alpha/container/fleet/multi-cluster-services/help @@ -0,0 +1,39 @@ +NAME + gcloud alpha container fleet multi-cluster-services - manage Multi-cluster + Services Feature + +SYNOPSIS + gcloud alpha container fleet multi-cluster-services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage Multi-cluster Services Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe the status of the Multi-cluster Services Feature + resource. + + disable + (ALPHA) Disable the Multi-cluster Services Feature. + + enable + (ALPHA) Enable the Multi-cluster Services Feature. + +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. These variants are also available: + + $ gcloud container fleet multi-cluster-services + + $ gcloud beta container fleet multi-cluster-services + diff --git a/gcloud/alpha/container/fleet/service-directory/describe b/gcloud/alpha/container/fleet/service-directory/describe new file mode 100644 index 000000000..3c20f41ee --- /dev/null +++ b/gcloud/alpha/container/fleet/service-directory/describe @@ -0,0 +1,31 @@ +NAME + gcloud alpha container fleet service-directory describe - describe the + status of the Service Directory Feature resource + +SYNOPSIS + gcloud alpha container fleet service-directory describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) This command gets the detailed status of the Service Directory + Feature resource in a fleet. + +EXAMPLES + To describe the Service Directory Feature, run: + + $ gcloud alpha container fleet service-directory describe + +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/container/fleet/service-directory/disable b/gcloud/alpha/container/fleet/service-directory/disable new file mode 100644 index 000000000..092d75a9c --- /dev/null +++ b/gcloud/alpha/container/fleet/service-directory/disable @@ -0,0 +1,35 @@ +NAME + gcloud alpha container fleet service-directory disable - disable the + Service Directory Feature + +SYNOPSIS + gcloud alpha container fleet service-directory disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Disables the Service Directory Feature in a fleet. + +EXAMPLES + To disable the Service Directory Feature, run: + + $ gcloud alpha container fleet service-directory disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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/container/fleet/service-directory/enable b/gcloud/alpha/container/fleet/service-directory/enable new file mode 100644 index 000000000..00314655c --- /dev/null +++ b/gcloud/alpha/container/fleet/service-directory/enable @@ -0,0 +1,30 @@ +NAME + gcloud alpha container fleet service-directory enable - enable the Service + Directory Feature + +SYNOPSIS + gcloud alpha container fleet service-directory enable + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Enables the Service Directory Feature in a fleet. + +EXAMPLES + To enable the Service Directory Feature, run: + + $ gcloud alpha container fleet service-directory enable + +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/container/fleet/service-directory/help b/gcloud/alpha/container/fleet/service-directory/help new file mode 100644 index 000000000..fde43f0b2 --- /dev/null +++ b/gcloud/alpha/container/fleet/service-directory/help @@ -0,0 +1,34 @@ +NAME + gcloud alpha container fleet service-directory - manage the Service + Directory Feature + +SYNOPSIS + gcloud alpha container fleet service-directory COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (ALPHA) Manage the Service Directory Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + (ALPHA) Describe the status of the Service Directory Feature resource. + + disable + (ALPHA) Disable the Service Directory Feature. + + enable + (ALPHA) Enable the Service Directory Feature. + +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/container/help b/gcloud/alpha/container/help index b9f0b8f55..3206eaee8 100644 --- a/gcloud/alpha/container/help +++ b/gcloud/alpha/container/help @@ -34,9 +34,13 @@ GROUPS clusters (ALPHA) Deploy and teardown Google Kubernetes Engine clusters. + fleet + (ALPHA) Centrally manage features and services on all your Kubernetes + clusters with fleet. + hub (ALPHA) Centrally manage features and services on all your Kubernetes - clusters with Hub. + clusters with fleet. images (ALPHA) List and manipulate Google Container Registry images. diff --git a/gcloud/alpha/container/hub/help b/gcloud/alpha/container/hub/help index c50f73a91..fb0dd1dbd 100644 --- a/gcloud/alpha/container/hub/help +++ b/gcloud/alpha/container/hub/help @@ -1,6 +1,6 @@ NAME gcloud alpha container hub - centrally manage features and services on all - your Kubernetes clusters with Hub + your Kubernetes clusters with fleet SYNOPSIS gcloud alpha container hub GROUP | COMMAND [GCLOUD_WIDE_FLAG ...] @@ -8,15 +8,16 @@ SYNOPSIS DESCRIPTION (ALPHA) The command group to register GKE or other Kubernetes clusters running in a variety of environments, including Google cloud, on premises - in customer datacenters, or other third party clouds with Hub. Hub provides - a centralized control-plane to managed features and services on all - registered clusters. + in customer datacenters, or other third party clouds with fleet. Fleet + provides a centralized control-plane to managed features and services on + all registered clusters. A registered cluster is always associated with a Membership, a resource - within Hub. + within fleet. EXAMPLES - Manage memberships of all your GKE and other Kubernetes clusters with Hub: + Manage memberships of all your GKE and other Kubernetes clusters with + fleet: $ gcloud alpha container hub memberships --help diff --git a/gcloud/alpha/database-migration/connection-profiles/create/cloudsql b/gcloud/alpha/database-migration/connection-profiles/create/cloudsql index 53ede769b..a126bec0c 100644 --- a/gcloud/alpha/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/alpha/database-migration/connection-profiles/create/cloudsql @@ -8,12 +8,11 @@ SYNOPSIS --database-version=DATABASE_VERSION --source-id=SOURCE_ID --tier=TIER [--activation-policy=ACTIVATION_POLICY] [--authorized-networks=NETWORK,[NETWORK,...]] - [--auto-storage-increase=AUTO_STORAGE_INCREASE] - [--data-disk-size=DATA_DISK_SIZE] [--data-disk-type=DATA_DISK_TYPE] - [--database-flags=[KEY=VALUE,...]] [--display-name=DISPLAY_NAME] - [--enable-ip-v4=ENABLE_IP_V4] [--labels=[KEY=VALUE,...]] - [--private-network=PRIVATE_NETWORK] [--provider=PROVIDER] - [--require-ssl=REQUIRE_SSL] + [--no-auto-storage-increase] [--data-disk-size=DATA_DISK_SIZE] + [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[KEY=VALUE,...]] + [--display-name=DISPLAY_NAME] [--no-enable-ip-v4] + [--labels=[KEY=VALUE,...]] [--private-network=PRIVATE_NETWORK] + [--provider=PROVIDER] [--require-ssl] [--storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT] [--user-labels=[KEY=VALUE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -107,13 +106,14 @@ OPTIONAL FLAGS https://en.wikipedia.org/wiki/CIDR_notation#CIDR_notation, also known as 'slash' notation (e.g.192.168.100.0/24). - --auto-storage-increase=AUTO_STORAGE_INCREASE + --auto-storage-increase If you enable this setting, Cloud SQL checks your available storage every 30 seconds. If the available storage falls below a threshold size, Cloud SQL automatically adds additional storage capacity. If the available storage repeatedly falls below the threshold size, Cloud SQL continues to add storage until it reaches the maximum of 30 TB. - Default: ON. + Default: ON. Enabled by default, use --no-auto-storage-increase to + disable. --data-disk-size=DATA_DISK_SIZE Storage capacity available to the database, in GB. The minimum (and @@ -131,8 +131,9 @@ OPTIONAL FLAGS --display-name=DISPLAY_NAME Friendly name for the connection profile. - --enable-ip-v4=ENABLE_IP_V4 - Whether the instance should be assigned an IPv4 address or not. + --enable-ip-v4 + Whether the instance should be assigned an IPv4 address or not. Enabled + by default, use --no-enable-ip-v4 to disable. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -152,7 +153,7 @@ OPTIONAL FLAGS Database provider (CLOUDSQL or RDS). PROVIDER must be one of: RDS, CLOUDSQL. - --require-ssl=REQUIRE_SSL + --require-ssl Whether SSL connections over IP should be enforced or not. --storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT diff --git a/gcloud/alpha/iam/workload-identity-pools/create-cred-config b/gcloud/alpha/iam/workload-identity-pools/create-cred-config index 1cc566782..a3985043e 100644 --- a/gcloud/alpha/iam/workload-identity-pools/create-cred-config +++ b/gcloud/alpha/iam/workload-identity-pools/create-cred-config @@ -10,8 +10,8 @@ SYNOPSIS [--app-id-uri=APP_ID_URI] [--credential-source-field-name=CREDENTIAL_SOURCE_FIELD_NAME] [--credential-source-headers=[key=value,...]] - [--credential-source-type=CREDENTIAL_SOURCE_TYPE] - [--include-aws-session-token-url] [--service-account=SERVICE_ACCOUNT] + [--credential-source-type=CREDENTIAL_SOURCE_TYPE] [--enable-imdsv2] + [--service-account=SERVICE_ACCOUNT] [--subject-token-type=SUBJECT_TOKEN_TYPE] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -43,7 +43,7 @@ EXAMPLES $ gcloud alpha iam workload-identity-pools create-cred-config \ projects/$PROJECT_NUMBER/locations/$REGION/\ workloadIdentityPools/$WORKLOAD_POOL_ID/providers/$PROVIDER_ID \ - --service-account=$EMAIL --aws --include-aws-session-token-url \ + --service-account=$EMAIL --aws --enable-imdsv2 \ --output-file=credentials.json To create an Azure-based credential configuration for your project, run: @@ -96,9 +96,9 @@ OPTIONAL FLAGS --credential-source-type=CREDENTIAL_SOURCE_TYPE The format of the credential source (JSON or text). - --include-aws-session-token-url - Adds the AWS session token url to the credential source to enforce the - AWS IMDSv2 flow. + --enable-imdsv2 + Adds the AWS IMDSv2 session token url to the credential source to + enforce the AWS IMDSv2 flow. --service-account=SERVICE_ACCOUNT The email of the service account to impersonate. diff --git a/gcloud/alpha/resource-manager/tags/bindings/list b/gcloud/alpha/resource-manager/tags/bindings/list index a363e6bd5..8e5bfdd8e 100644 --- a/gcloud/alpha/resource-manager/tags/bindings/list +++ b/gcloud/alpha/resource-manager/tags/bindings/list @@ -4,8 +4,8 @@ NAME SYNOPSIS gcloud alpha resource-manager tags bindings list --parent=PARENT - [--location=LOCATION] [--filter=EXPRESSION] [--limit=LIMIT] - [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [--effective] [--location=LOCATION] [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] DESCRIPTION @@ -25,6 +25,10 @@ REQUIRED FLAGS Full resource name attached to the binding FLAGS + --effective + Show all effective TagBindings on the resource. TagBindings applied at + a higher level will be inherited to all descendants. + --location=LOCATION Region or zone of the resource for listing TagBindings. This field should not be set if the resource is a global resource like projects, diff --git a/gcloud/alpha/run/deploy b/gcloud/alpha/run/deploy index fa5675481..4ea378c25 100644 --- a/gcloud/alpha/run/deploy +++ b/gcloud/alpha/run/deploy @@ -10,7 +10,8 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--port=PORT] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--[no-]use-http2] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -43,16 +44,17 @@ DESCRIPTION EXAMPLES To deploy a container to the service my-backend on Cloud Run: - $ gcloud alpha run deploy my-backend --image=gcr.io/my/image + $ gcloud alpha run deploy my-backend \ + --image=us-docker.pkg.dev/project/image You may also omit the service name. Then a prompt will be displayed with a suggested default value: - $ gcloud alpha run deploy --image=gcr.io/my/image + $ gcloud alpha run deploy --image=us-docker.pkg.dev/project/image To deploy to Cloud Run on Kubernetes Engine, you need to specify a cluster: - $ gcloud alpha run deploy --image=gcr.io/my/image \ + $ gcloud alpha run deploy --image=us-docker.pkg.dev/project/image \ --cluster=my-cluster POSITIONAL ARGUMENTS @@ -206,6 +208,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/alpha/run/jobs/create b/gcloud/alpha/run/jobs/create index b7c288e85..bd0a3137a 100644 --- a/gcloud/alpha/run/jobs/create +++ b/gcloud/alpha/run/jobs/create @@ -1,6 +1,5 @@ NAME - gcloud alpha run jobs create - deploy a container to Cloud Run that will - run to completion + gcloud alpha run jobs create - deploy a new job to Cloud Run SYNOPSIS gcloud alpha run jobs create [JOB] --image=IMAGE [--args=[ARG,...]] @@ -23,12 +22,13 @@ EXAMPLES To deploy a new job my-data-transformation on Cloud Run: $ gcloud alpha run jobs create my-data-transformation \ - --image=gcr.io/my/image + --image=us-docker.pkg.dev/project/image You may also omit the job name. Then a prompt will be displayed with a suggested default value: - $ gcloud alpha run jobs create --image=gcr.io/my/image + $ gcloud alpha run jobs create \ + --image=us-docker.pkg.dev/project/image POSITIONAL ARGUMENTS Job resource - Job to create. This represents a Cloud resource. (NOTE) @@ -97,7 +97,7 @@ OPTIONAL FLAGS --parallelism=PARALLELISM Number of tasks that may run concurrently. Must be less than or equal - to the number of completions. + to the number of tasks. --region=REGION Region in which the resource can be found. Alternatively, set the diff --git a/gcloud/alpha/run/jobs/help b/gcloud/alpha/run/jobs/help index 619cd0afb..4fe499eb8 100644 --- a/gcloud/alpha/run/jobs/help +++ b/gcloud/alpha/run/jobs/help @@ -30,7 +30,7 @@ COMMANDS (ALPHA) Add IAM policy binding to a Cloud Run job. create - (ALPHA) Deploy a container to Cloud Run that will run to completion. + (ALPHA) Deploy a new job to Cloud Run. delete (ALPHA) Delete a job. diff --git a/gcloud/alpha/run/jobs/update b/gcloud/alpha/run/jobs/update index 3a811dfa2..48c53a19b 100644 --- a/gcloud/alpha/run/jobs/update +++ b/gcloud/alpha/run/jobs/update @@ -15,7 +15,8 @@ SYNOPSIS | --remove-cloudsql-instances=[CLOUDSQL-INSTANCES,...] | --set-cloudsql-instances=[CLOUDSQL-INSTANCES,...]] [--binary-authorization=POLICY | --clear-binary-authorization] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -29,7 +30,8 @@ DESCRIPTION EXAMPLES To update the container image of Cloud Run job my-job: - $ gcloud alpha run jobs update my-job --image=gcr.io/my-project/image + $ gcloud alpha run jobs update my-job \ + --image=us-docker.pkg.dev/project/image POSITIONAL ARGUMENTS Job resource - Job to update. This represents a Cloud resource. (NOTE) @@ -97,7 +99,7 @@ FLAGS --parallelism=PARALLELISM Number of tasks that may run concurrently. Must be less than or equal - to the number of completions. + to the number of tasks. --region=REGION Region in which the resource can be found. Alternatively, set the @@ -177,6 +179,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/alpha/run/services/update b/gcloud/alpha/run/services/update index 7071e42e9..f17b62c2f 100644 --- a/gcloud/alpha/run/services/update +++ b/gcloud/alpha/run/services/update @@ -23,7 +23,8 @@ SYNOPSIS | --clear-binary-authorization --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -312,6 +313,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/anthos/config/controller/delete b/gcloud/anthos/config/controller/delete index 1a2045ef0..9e5a50648 100644 --- a/gcloud/anthos/config/controller/delete +++ b/gcloud/anthos/config/controller/delete @@ -57,8 +57,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/anthos/config/controller/describe b/gcloud/anthos/config/controller/describe index 877cfc240..c5ce1e8ce 100644 --- a/gcloud/anthos/config/controller/describe +++ b/gcloud/anthos/config/controller/describe @@ -54,8 +54,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/anthos/config/controller/list b/gcloud/anthos/config/controller/list index cba829f06..7c4880cc8 100644 --- a/gcloud/anthos/config/controller/list +++ b/gcloud/anthos/config/controller/list @@ -72,8 +72,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/anthos/config/operations/describe b/gcloud/anthos/config/operations/describe index 06a8c6fc7..8651ae27b 100644 --- a/gcloud/anthos/config/operations/describe +++ b/gcloud/anthos/config/operations/describe @@ -54,8 +54,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/anthos/config/operations/list b/gcloud/anthos/config/operations/list index e5e76d7b5..3ef65b815 100644 --- a/gcloud/anthos/config/operations/list +++ b/gcloud/anthos/config/operations/list @@ -72,8 +72,8 @@ GCLOUD WIDE FLAGS Run $ gcloud help for details. API REFERENCE - This command uses the krmapihosting/v1alpha1 API. The full documentation - for this API can be found at: https://cloud.google.com/ + This command uses the krmapihosting/v1 API. The full documentation for this + API can be found at: https://cloud.google.com/ NOTES This variant is also available: diff --git a/gcloud/app/deploy b/gcloud/app/deploy index 95bf39459..d7aeacbc5 100644 --- a/gcloud/app/deploy +++ b/gcloud/app/deploy @@ -84,9 +84,9 @@ FLAGS default code bucket is used. --cache - Skip caching mechanisms involved in the deployment process, in - particular do not use cached dependencies during the build step. - Enabled by default, use --no-cache to disable. + Enable caching mechanisms involved in the deployment process, + particularly in the build step. Enabled by default, use --no-cache to + disable. --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/beta/app/deploy b/gcloud/beta/app/deploy index 6a367a9f0..bdd8b843a 100644 --- a/gcloud/beta/app/deploy +++ b/gcloud/beta/app/deploy @@ -86,9 +86,9 @@ FLAGS default code bucket is used. --cache - Skip caching mechanisms involved in the deployment process, in - particular do not use cached dependencies during the build step. - Enabled by default, use --no-cache to disable. + Enable caching mechanisms involved in the deployment process, + particularly in the build step. Enabled by default, use --no-cache to + disable. --ignore-file=IGNORE_FILE Override the .gcloudignore file and use the specified file instead. diff --git a/gcloud/beta/compute/disks/snapshot b/gcloud/beta/compute/disks/snapshot index 23d03672e..174eb3aae 100644 --- a/gcloud/beta/compute/disks/snapshot +++ b/gcloud/beta/compute/disks/snapshot @@ -67,8 +67,7 @@ FLAGS --guest-flush Create an application-consistent snapshot by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/beta/compute/machine-images/create b/gcloud/beta/compute/machine-images/create index 9dafe5a49..e8c8af892 100644 --- a/gcloud/beta/compute/machine-images/create +++ b/gcloud/beta/compute/machine-images/create @@ -47,8 +47,7 @@ OPTIONAL FLAGS --guest-flush Create an application-consistent machine image by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --require-csek-key-create Refuse to create machine images not protected by a user managed key in diff --git a/gcloud/beta/compute/machine-images/import b/gcloud/beta/compute/machine-images/import index 454ab2794..bea78ebf8 100644 --- a/gcloud/beta/compute/machine-images/import +++ b/gcloud/beta/compute/machine-images/import @@ -118,8 +118,7 @@ OPTIONAL FLAGS --guest-flush Create an application-consistent machine image by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --guest-os-features=[GUEST_OS_FEATURE,...] This parameter enables one or more features for VM instances that use diff --git a/gcloud/beta/config/get b/gcloud/beta/config/get index fa5eb38d7..0fb79d340 100644 --- a/gcloud/beta/config/get +++ b/gcloud/beta/config/get @@ -75,6 +75,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/beta/config/help b/gcloud/beta/config/help index 430bc3c22..d1b6d0237 100644 --- a/gcloud/beta/config/help +++ b/gcloud/beta/config/help @@ -107,6 +107,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/beta/config/list b/gcloud/beta/config/list index 56e314f51..c00013378 100644 --- a/gcloud/beta/config/list +++ b/gcloud/beta/config/list @@ -109,6 +109,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/beta/config/set b/gcloud/beta/config/set index 7bfdb21a2..3bfbfa50d 100644 --- a/gcloud/beta/config/set +++ b/gcloud/beta/config/set @@ -122,6 +122,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/beta/config/unset b/gcloud/beta/config/unset index 3dae72fd5..db1514392 100644 --- a/gcloud/beta/config/unset +++ b/gcloud/beta/config/unset @@ -83,6 +83,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/beta/container/binauthz/attestors/public-keys/add b/gcloud/beta/container/binauthz/attestors/public-keys/add index 502c4aead..278b6f52b 100644 --- a/gcloud/beta/container/binauthz/attestors/public-keys/add +++ b/gcloud/beta/container/binauthz/attestors/public-keys/add @@ -112,7 +112,9 @@ REQUIRED FLAGS ecdsa-p384-sha384, ecdsa-p521-sha512, rsa-pss-2048-sha256, rsa-pss-3072-sha256, rsa-pss-4096-sha256, rsa-pss-4096-sha512, rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512. + rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, + rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, + rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512. This flag must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/beta/container/fleet/cloudrun/apply b/gcloud/beta/container/fleet/cloudrun/apply new file mode 100644 index 000000000..80a53e06c --- /dev/null +++ b/gcloud/beta/container/fleet/cloudrun/apply @@ -0,0 +1,74 @@ +NAME + gcloud beta container fleet cloudrun apply - deploy or update the CloudRun + feature + +SYNOPSIS + gcloud beta container fleet cloudrun apply + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [--config=CONFIG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Deploy or update a user-specified config file of the CloudRun custom + resource. The config file should be a YAML file. + +EXAMPLES + To apply the CloudRun YAML file, run: + + $ gcloud beta container fleet cloudrun apply \ + --kubeconfig=/path/to/kubeconfig \ + --config=/path/to/cloud-run-cr.yaml + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + +OPTIONAL FLAGS + --config=CONFIG + The path to CloudRun custom resource config file. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet cloudrun apply + + $ gcloud alpha container fleet cloudrun apply + diff --git a/gcloud/beta/container/fleet/cloudrun/describe b/gcloud/beta/container/fleet/cloudrun/describe new file mode 100644 index 000000000..85760c591 --- /dev/null +++ b/gcloud/beta/container/fleet/cloudrun/describe @@ -0,0 +1,29 @@ +NAME + gcloud beta container fleet cloudrun describe - describe the status of the + CloudRun feature + +SYNOPSIS + gcloud beta container fleet cloudrun describe [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To get the detailed current status of the CloudRun Feature in Anthos + clusters, run: + + $ gcloud beta container fleet cloudrun describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet cloudrun describe + + $ gcloud alpha container fleet cloudrun describe + diff --git a/gcloud/beta/container/fleet/cloudrun/disable b/gcloud/beta/container/fleet/cloudrun/disable new file mode 100644 index 000000000..e6d332795 --- /dev/null +++ b/gcloud/beta/container/fleet/cloudrun/disable @@ -0,0 +1,36 @@ +NAME + gcloud beta container fleet cloudrun disable - disable the CloudRun feature + +SYNOPSIS + gcloud beta container fleet cloudrun disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command disables the CloudRun feature in Anthos clusters. + +EXAMPLES + To disable the CloudRun Feature, run: + + $ gcloud beta container fleet cloudrun disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet cloudrun disable + + $ gcloud alpha container fleet cloudrun disable + diff --git a/gcloud/beta/container/fleet/cloudrun/enable b/gcloud/beta/container/fleet/cloudrun/enable new file mode 100644 index 000000000..12fdc3d8c --- /dev/null +++ b/gcloud/beta/container/fleet/cloudrun/enable @@ -0,0 +1,30 @@ +NAME + gcloud beta container fleet cloudrun enable - enable the CloudRun feature + +SYNOPSIS + gcloud beta container fleet cloudrun enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command enables the CloudRun feature in Anthos clusters. + +EXAMPLES + To enable the CloudRun Feature, run: + + $ gcloud beta container fleet cloudrun enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet cloudrun enable + + $ gcloud alpha container fleet cloudrun enable + diff --git a/gcloud/beta/container/fleet/cloudrun/help b/gcloud/beta/container/fleet/cloudrun/help new file mode 100644 index 000000000..2ff8a3727 --- /dev/null +++ b/gcloud/beta/container/fleet/cloudrun/help @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet cloudrun - manage the CloudRun feature + +SYNOPSIS + gcloud beta container fleet cloudrun COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage the CloudRun feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + (BETA) Deploy or update the CloudRun feature. + + describe + (BETA) Describe the status of the CloudRun feature. + + disable + (BETA) Disable the CloudRun feature. + + enable + (BETA) Enable the CloudRun feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet cloudrun + + $ gcloud alpha container fleet cloudrun + diff --git a/gcloud/beta/container/fleet/config-management/apply b/gcloud/beta/container/fleet/config-management/apply new file mode 100644 index 000000000..3804a95fe --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/apply @@ -0,0 +1,48 @@ +NAME + gcloud beta container fleet config-management apply - update a Config + Management Feature Spec + +SYNOPSIS + gcloud beta container fleet config-management apply --config=CONFIG + [--membership=MEMBERSHIP] [--version=VERSION] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update a user-specified config file to a ConfigManagement Custom + Resource. The config file should be a .yaml file, all eligible fields are + listed in + https://cloud.google.com/anthos-config-management/docs/reference/gcloud-apply-fields + +EXAMPLES + To apply a YAML config file to a membership, prepare apply-spec.yaml + (https://cloud.google.com/anthos-config-management/docs/reference/gcloud-apply-fields#example_gcloud_apply_spec) + then run: + + $ gcloud beta container fleet config-management apply \ + --membership=CLUSTER_NAME --config=APPLY-SPEC.YAML \ + --version=VERSION + +REQUIRED FLAGS + --config=CONFIG + The path to config-management.yaml. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + + --version=VERSION + The version of ACM to install. + +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 fleet config-management apply + diff --git a/gcloud/beta/container/fleet/config-management/disable b/gcloud/beta/container/fleet/config-management/disable new file mode 100644 index 000000000..4a7750f37 --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/disable @@ -0,0 +1,35 @@ +NAME + gcloud beta container fleet config-management disable - disable Config + Management Feature + +SYNOPSIS + gcloud beta container fleet config-management disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Disable the Config Management Feature in a fleet. + +EXAMPLES + To disable the Config Management Feature, run: + + $ gcloud beta container fleet config-management disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 fleet config-management disable + diff --git a/gcloud/beta/container/fleet/config-management/enable b/gcloud/beta/container/fleet/config-management/enable new file mode 100644 index 000000000..f6516ce7e --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/enable @@ -0,0 +1,29 @@ +NAME + gcloud beta container fleet config-management enable - enable Config + Management Feature + +SYNOPSIS + gcloud beta container fleet config-management enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enables the Config Management Feature in a fleet. + +EXAMPLES + To enable the Config Management Feature, run: + + $ gcloud beta container fleet config-management enable + +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 fleet config-management enable + diff --git a/gcloud/beta/container/fleet/config-management/help b/gcloud/beta/container/fleet/config-management/help new file mode 100644 index 000000000..a9f7725c8 --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/help @@ -0,0 +1,48 @@ +NAME + gcloud beta container fleet config-management - manage Config Management + Feature + +SYNOPSIS + gcloud beta container fleet config-management COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Config Management Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + (BETA) Update a Config Management Feature Spec. + + disable + (BETA) Disable Config Management Feature. + + enable + (BETA) Enable Config Management Feature. + + status + (BETA) Print the status of all clusters with Config Management enabled. + + unmanage + (BETA) Remove the Config Management Feature Spec for the given + membership. + + upgrade + (BETA) Upgrade the version of the Config Management Feature. + + version + (BETA) Print the version of all clusters with Config Management + enabled. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet config-management + diff --git a/gcloud/beta/container/fleet/config-management/status b/gcloud/beta/container/fleet/config-management/status new file mode 100644 index 000000000..92e6ae081 --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/status @@ -0,0 +1,89 @@ +NAME + gcloud beta container fleet config-management status - print the status of + all clusters with Config Management enabled + +SYNOPSIS + gcloud beta container fleet config-management status [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Print the status of all clusters with Config Management enabled. + +EXAMPLES + Print the status of the Config Management Feature: + + $ gcloud beta container fleet config-management status + + Name Status Last_Synced_Token Sync_Branch Last_Synced_Time Hierarchy_Controller + managed-cluster SYNCED 2945500b7f acme 2020-03-23 + 11:12:31 -0700 PDT INSTALLED + + View the status for the cluster named managed-cluster-a: + + $ gcloud beta container fleet config-management status \ + --filter="acm_status.name:managed-cluster-a" + + Use a regular expression to list status for multiple clusters: + + $ gcloud beta container fleet config-management status \ + --filter="acm_status.name ~ managed-cluster.*" + + List all clusters where current status is SYNCED: + + $ gcloud beta container fleet config-management status \ + --filter="acm_status.config_sync:SYNCED" + + List all the clusters where sync_branch is v1 and current Config Sync + status is not SYNCED: + + $ gcloud beta container fleet config-management status \ + --filter="acm_status.sync_branch:v1 AND \ + -acm_status.config_sync:SYNCED" + +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 fleet config-management status + diff --git a/gcloud/beta/container/fleet/config-management/unmanage b/gcloud/beta/container/fleet/config-management/unmanage new file mode 100644 index 000000000..07e394a7f --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/unmanage @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet config-management unmanage - remove the Config + Management Feature Spec for the given membership + +SYNOPSIS + gcloud beta container fleet config-management unmanage + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Remove the Config Management Feature Spec for the given membership. + The existing ConfigManagement resources in the clusters will become + unmanaged. + +EXAMPLES + To remove the Config Management Feature spec for a Membership, run: + + $ gcloud beta container fleet config-management unmanage \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +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 fleet config-management unmanage + diff --git a/gcloud/beta/container/fleet/config-management/upgrade b/gcloud/beta/container/fleet/config-management/upgrade new file mode 100644 index 000000000..432498cac --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/upgrade @@ -0,0 +1,40 @@ +NAME + gcloud beta container fleet config-management upgrade - upgrade the version + of the Config Management Feature + +SYNOPSIS + gcloud beta container fleet config-management upgrade --version=VERSION + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Upgrade a specified membership to any supported version of the + Config Management Feature. + +EXAMPLES + To upgrade a membership named CLUSTER_NAME, run: + + $ gcloud beta container fleet config-management upgrade \ + --membership=CLUSTER_NAME --version=VERSION + +REQUIRED FLAGS + --version=VERSION + The version of ACM to change to. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +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 fleet config-management upgrade + diff --git a/gcloud/beta/container/fleet/config-management/version b/gcloud/beta/container/fleet/config-management/version new file mode 100644 index 000000000..a9bb1c7a8 --- /dev/null +++ b/gcloud/beta/container/fleet/config-management/version @@ -0,0 +1,60 @@ +NAME + gcloud beta container fleet config-management version - print the version + of all clusters with Config Management enabled + +SYNOPSIS + gcloud beta container fleet config-management version [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To print the version of all clusters with Config Management enabled, run: + + $ gcloud beta container fleet config-management version + +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 fleet config-management version + diff --git a/gcloud/beta/container/fleet/features/help b/gcloud/beta/container/fleet/features/help new file mode 100644 index 000000000..6f8edd003 --- /dev/null +++ b/gcloud/beta/container/fleet/features/help @@ -0,0 +1,30 @@ +NAME + gcloud beta container fleet features - manage Hub Feature resources + +SYNOPSIS + gcloud beta container fleet features COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) These commands manage Features generically. Most Features offer + specialized commands under dedicated sub-groups that may be more effective + for that specific Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + (BETA) List enabled features. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet features + + $ gcloud alpha container fleet features + diff --git a/gcloud/beta/container/fleet/features/list b/gcloud/beta/container/fleet/features/list new file mode 100644 index 000000000..c057847e5 --- /dev/null +++ b/gcloud/beta/container/fleet/features/list @@ -0,0 +1,87 @@ +NAME + gcloud beta container fleet features list - list enabled features + +SYNOPSIS + gcloud beta container fleet features list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List enabled Hub features in a project. + +EXAMPLES + To list all enabled Hub features in a project, run: + + $ gcloud beta container fleet features list + +FLAGS + Location resource - The location to list Features under. + + 'global' is the only supported value. 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; + ◆ global is the only supported location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --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; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1beta API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet features list + + $ gcloud alpha container fleet features list + diff --git a/gcloud/beta/container/fleet/help b/gcloud/beta/container/fleet/help new file mode 100644 index 000000000..ba0b9c258 --- /dev/null +++ b/gcloud/beta/container/fleet/help @@ -0,0 +1,80 @@ +NAME + gcloud beta container fleet - centrally manage features and services on all + your Kubernetes clusters with fleet + +SYNOPSIS + gcloud beta container fleet GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) The command group to register GKE or other Kubernetes clusters + running in a variety of environments, including Google cloud, on premises + in customer datacenters, or other third party clouds with fleet. Fleet + provides a centralized control-plane to managed features and services on + all registered clusters. + + A registered cluster is always associated with a Membership, a resource + within fleet. + +EXAMPLES + Manage memberships of all your GKE and other Kubernetes clusters with + fleet: + + $ gcloud beta container fleet memberships --help + + Manage Config Management feature on all memberships: + + $ gcloud beta container fleet config-management --help + + Manage Multi-cluster Ingress feature on all memberships: + + $ gcloud beta container fleet ingress --help + + Manage Multi-cluster Services feature on all memberships: + + $ gcloud beta container fleet multi-cluster-services --help + + Manage CloudRun feature on all memberships: + + $ gcloud beta container fleet cloudrun --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + cloudrun + (BETA) Manage the CloudRun feature. + + config-management + (BETA) Manage Config Management Feature. + + features + (BETA) Manage Hub Feature resources. + + identity-service + (BETA) Manage Identity Service Feature. + + ingress + (BETA) Manage Multi-cluster Ingress Feature. + + memberships + (BETA) Manage memberships of all your GKE and other Kubernetes cluster + with Fleet. + + mesh + (BETA) Manage Service Mesh Feature. + + multi-cluster-services + (BETA) Manage Multi-cluster Services Feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet + + $ gcloud alpha container fleet + diff --git a/gcloud/beta/container/fleet/identity-service/apply b/gcloud/beta/container/fleet/identity-service/apply new file mode 100644 index 000000000..600898176 --- /dev/null +++ b/gcloud/beta/container/fleet/identity-service/apply @@ -0,0 +1,45 @@ +NAME + gcloud beta container fleet identity-service apply - update an Identity + Service Feature Spec + +SYNOPSIS + gcloud beta container fleet identity-service apply --config=CONFIG + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Applies the authentication configuration to the Identity Service + feature spec for this membership. This configuration is now the "source of + truth" for the cluster and can only be updated by using this command or the + Cloud Console. Any local authentication configuration on the cluster is + overwritten by this configuration, including any local updates made after + you run this command. + +EXAMPLES + To apply an Identity Service configuration for a membership, run: + + $ gcloud beta container fleet identity-service apply \ + --membership=CLUSTER_NAME \ + --config=/path/to/identity-service.yaml + +REQUIRED FLAGS + --config=CONFIG + The path to the identity-service.yaml config file. + +OPTIONAL FLAGS + --membership=MEMBERSHIP + The Membership name provided during registration. + +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 fleet identity-service apply + diff --git a/gcloud/beta/container/fleet/identity-service/delete b/gcloud/beta/container/fleet/identity-service/delete new file mode 100644 index 000000000..299787396 --- /dev/null +++ b/gcloud/beta/container/fleet/identity-service/delete @@ -0,0 +1,35 @@ +NAME + gcloud beta container fleet identity-service delete - remove the Identity + Service Feature Spec for the given membership + +SYNOPSIS + gcloud beta container fleet identity-service delete + [--membership=MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Removes the Identity Service Feature Spec for the given membership. + +EXAMPLES + To delete an Identity Service configuration for a membership, run: + + $ gcloud beta container fleet identity-service delete \ + --membership=CLUSTER_NAME + +FLAGS + --membership=MEMBERSHIP + Membership name provided during registration. + +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 fleet identity-service delete + diff --git a/gcloud/beta/container/fleet/identity-service/describe b/gcloud/beta/container/fleet/identity-service/describe new file mode 100644 index 000000000..1af3b70b0 --- /dev/null +++ b/gcloud/beta/container/fleet/identity-service/describe @@ -0,0 +1,64 @@ +NAME + gcloud beta container fleet identity-service describe - prints the status + of all clusters with Identity Service installed + +SYNOPSIS + gcloud beta container fleet identity-service describe [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Prints the status of the Identity Service Feature resource in a + fleet. + +EXAMPLES + To describe the status of the Identity Service configuration, run: + + $ gcloud beta container fleet identity-service describe + +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 fleet identity-service describe + diff --git a/gcloud/beta/container/fleet/identity-service/disable b/gcloud/beta/container/fleet/identity-service/disable new file mode 100644 index 000000000..db1f55131 --- /dev/null +++ b/gcloud/beta/container/fleet/identity-service/disable @@ -0,0 +1,35 @@ +NAME + gcloud beta container fleet identity-service disable - disable Identity + Service Feature + +SYNOPSIS + gcloud beta container fleet identity-service disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command disables the Identity Service Feature in a fleet. + +EXAMPLES + To disable the Identity Service Feature, run: + + $ gcloud beta container fleet identity-service disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +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 fleet identity-service disable + diff --git a/gcloud/beta/container/fleet/identity-service/enable b/gcloud/beta/container/fleet/identity-service/enable new file mode 100644 index 000000000..80fcc80fa --- /dev/null +++ b/gcloud/beta/container/fleet/identity-service/enable @@ -0,0 +1,29 @@ +NAME + gcloud beta container fleet identity-service enable - enable Identity + Service Feature + +SYNOPSIS + gcloud beta container fleet identity-service enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command enables the Identity Service Feature in a fleet. + +EXAMPLES + To enable the Identity Service Feature, run: + + $ gcloud beta container fleet identity-service enable + +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 fleet identity-service enable + diff --git a/gcloud/beta/container/fleet/identity-service/help b/gcloud/beta/container/fleet/identity-service/help new file mode 100644 index 000000000..65e76c008 --- /dev/null +++ b/gcloud/beta/container/fleet/identity-service/help @@ -0,0 +1,41 @@ +NAME + gcloud beta container fleet identity-service - manage Identity Service + Feature + +SYNOPSIS + gcloud beta container fleet identity-service COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Identity Service Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + (BETA) Update an Identity Service Feature Spec. + + delete + (BETA) Remove the Identity Service Feature Spec for the given + membership. + + describe + (BETA) Prints the status of all clusters with Identity Service + installed. + + disable + (BETA) Disable Identity Service Feature. + + enable + (BETA) Enable Identity Service Feature. + +NOTES + This command is currently in beta and might change without notice. This + variant is also available: + + $ gcloud alpha container fleet identity-service + diff --git a/gcloud/beta/container/fleet/ingress/describe b/gcloud/beta/container/fleet/ingress/describe new file mode 100644 index 000000000..0250e1ddd --- /dev/null +++ b/gcloud/beta/container/fleet/ingress/describe @@ -0,0 +1,32 @@ +NAME + gcloud beta container fleet ingress describe - describe the status of + Multi-cluster Ingress Feature resource + +SYNOPSIS + gcloud beta container fleet ingress describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command describes the status of Multi-cluster Ingress Feature + resource in fleet. + +EXAMPLES + To describe the Ingress Feature, run: + + $ gcloud beta container fleet ingress describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet ingress describe + + $ gcloud alpha container fleet ingress describe + diff --git a/gcloud/beta/container/fleet/ingress/disable b/gcloud/beta/container/fleet/ingress/disable new file mode 100644 index 000000000..c36b3f42a --- /dev/null +++ b/gcloud/beta/container/fleet/ingress/disable @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet ingress disable - disable Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud beta container fleet ingress disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command disables Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To disable the Ingress Feature, run: + + $ gcloud beta container fleet ingress disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet ingress disable + + $ gcloud alpha container fleet ingress disable + diff --git a/gcloud/beta/container/fleet/ingress/enable b/gcloud/beta/container/fleet/ingress/enable new file mode 100644 index 000000000..6f2c238b7 --- /dev/null +++ b/gcloud/beta/container/fleet/ingress/enable @@ -0,0 +1,38 @@ +NAME + gcloud beta container fleet ingress enable - enable Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud beta container fleet ingress enable + [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command enables Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To enable the Ingress Feature, run: + + $ gcloud beta container fleet ingress enable \ + --config-membership=CONFIG_MEMBERSHIP + +FLAGS + --config-membership=CONFIG_MEMBERSHIP + Membership resource representing the cluster which hosts the + MultiClusterIngress and MultiClusterService CustomResourceDefinitions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet ingress enable + + $ gcloud alpha container fleet ingress enable + diff --git a/gcloud/beta/container/fleet/ingress/help b/gcloud/beta/container/fleet/ingress/help new file mode 100644 index 000000000..10f637a07 --- /dev/null +++ b/gcloud/beta/container/fleet/ingress/help @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet ingress - manage Multi-cluster Ingress Feature + +SYNOPSIS + gcloud beta container fleet ingress COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Multi-cluster Ingress Feature. + +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 the status of Multi-cluster Ingress Feature resource. + + disable + (BETA) Disable Multi-cluster Ingress Feature. + + enable + (BETA) Enable Multi-cluster Ingress Feature. + + update + (BETA) Update Multi-cluster Ingress Feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet ingress + + $ gcloud alpha container fleet ingress + diff --git a/gcloud/beta/container/fleet/ingress/update b/gcloud/beta/container/fleet/ingress/update new file mode 100644 index 000000000..13bd32725 --- /dev/null +++ b/gcloud/beta/container/fleet/ingress/update @@ -0,0 +1,38 @@ +NAME + gcloud beta container fleet ingress update - update Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud beta container fleet ingress update + [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command updates Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To update the Ingress Feature, run: + + $ gcloud beta container fleet ingress update \ + --config-membership=CONFIG_MEMBERSHIP + +FLAGS + --config-membership=CONFIG_MEMBERSHIP + Membership resource representing the cluster which hosts the + MultiClusterIngress and MultiClusterService CustomResourceDefinitions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet ingress update + + $ gcloud alpha container fleet ingress update + diff --git a/gcloud/beta/container/fleet/memberships/delete b/gcloud/beta/container/fleet/memberships/delete new file mode 100644 index 000000000..13af6fbb9 --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/delete @@ -0,0 +1,75 @@ +NAME + gcloud beta container fleet memberships delete - delete a membership + +SYNOPSIS + gcloud beta container fleet memberships delete + (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command deletes the Fleet membership resource corresponding to + the cluster. + + This command is intended to delete stale Fleet Membership resources as + doing so on a fully registered cluster will skip uninstalling the Connect + Agent and and orphan in-cluster resources and agent connections to Google. + To completely unregister the cluster, consider using the command: gcloud + beta container fleet memberships unregister. + +EXAMPLES + Delete a membership from Fleet: + + $ gcloud beta container fleet memberships delete a-membership + +POSITIONAL ARGUMENTS + Membership resource - The cluster membership 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1beta1 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships delete + + $ gcloud alpha container fleet memberships delete + diff --git a/gcloud/beta/container/fleet/memberships/describe b/gcloud/beta/container/fleet/memberships/describe new file mode 100644 index 000000000..a45382586 --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/describe @@ -0,0 +1,63 @@ +NAME + gcloud beta container fleet memberships describe - describe a membership + +SYNOPSIS + gcloud beta container fleet memberships describe + (MEMBERSHIP : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe a membership in Fleet. + +EXAMPLES + Describe a membership in Fleet: + + $ gcloud beta container fleet memberships describe a-membership + +POSITIONAL ARGUMENTS + Membership resource - The cluster membership 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1beta1 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships describe + + $ gcloud alpha container fleet memberships describe + diff --git a/gcloud/beta/container/fleet/memberships/get-credentials b/gcloud/beta/container/fleet/memberships/get-credentials new file mode 100644 index 000000000..8c9d9f531 --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/get-credentials @@ -0,0 +1,47 @@ +NAME + gcloud beta container fleet memberships get-credentials - fetch credentials + for a Fleet-registered cluster to be used in Connect Gateway + +SYNOPSIS + gcloud beta container fleet memberships get-credentials MEMBERSHIP + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) gcloud beta container fleet memberships get-credentials updates the + kubeconfig file with the appropriate credentials and endpoint information + to send kubectl commands to a Fleet-registered and connected cluster + through Connect Gateway Service. + + It takes a project, passed through by set defaults or flags. By default, + credentials are written to $HOME/.kube/config. You can provide an alternate + path by setting the KUBECONFIG environment variable. If KUBECONFIG contains + multiple paths, the first one is used. + + Upon success, this command will switch current context to the target + cluster, when working with multiple clusters. + +EXAMPLES + Get gateway kubeconfig for a registered cluster: + + $ gcloud beta container fleet memberships get-credentials my-cluster + +POSITIONAL ARGUMENTS + MEMBERSHIP + The membership name used to locate a cluster in your 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. These + variants are also available: + + $ gcloud container fleet memberships get-credentials + + $ gcloud alpha container fleet memberships get-credentials + diff --git a/gcloud/beta/container/fleet/memberships/help b/gcloud/beta/container/fleet/memberships/help new file mode 100644 index 000000000..0de7dcff5 --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/help @@ -0,0 +1,49 @@ +NAME + gcloud beta container fleet memberships - manage memberships of all your + GKE and other Kubernetes cluster with Fleet + +SYNOPSIS + gcloud beta container fleet memberships COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage memberships of all your GKE and other Kubernetes cluster with + Fleet. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + (BETA) Delete a membership. + + describe + (BETA) Describe a membership. + + get-credentials + (BETA) Fetch credentials for a Fleet-registered cluster to be used in + Connect Gateway. + + list + (BETA) List memberships. + + register + (BETA) Register a cluster with Fleet. + + unregister + (BETA) Unregister a cluster from Fleet. + + update + (BETA) Update a membership. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships + + $ gcloud alpha container fleet memberships + diff --git a/gcloud/beta/container/fleet/memberships/list b/gcloud/beta/container/fleet/memberships/list new file mode 100644 index 000000000..03137fedc --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/list @@ -0,0 +1,69 @@ +NAME + gcloud beta container fleet memberships list - list memberships + +SYNOPSIS + gcloud beta container fleet memberships list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) List memberships in Fleet. + +EXAMPLES + List memberships in Fleet: + + $ gcloud beta container fleet memberships list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1beta1 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships list + + $ gcloud alpha container fleet memberships list + diff --git a/gcloud/beta/container/fleet/memberships/register b/gcloud/beta/container/fleet/memberships/register new file mode 100644 index 000000000..6f2ae7f3b --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/register @@ -0,0 +1,245 @@ +NAME + gcloud beta container fleet memberships register - register a cluster with + Fleet + +SYNOPSIS + gcloud beta container fleet memberships register CLUSTER_NAME + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) + (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE + | [--enable-workload-identity : --has-private-issuer + | --public-issuer-url=PUBLIC_ISSUER_URL]) [--internal-ip] + [--manifest-output-file=MANIFEST_OUTPUT_FILE] [--proxy=PROXY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command registers a cluster with the Fleet by: + + 1. Creating a Fleet Membership resource corresponding to the cluster. + 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive + to one Fleet. + 3. Installing the Connect Agent into this cluster. + + A successful registration implies that the cluster is now exclusive to a + single Fleet. + + For more information about Connect Agent, go to: + https://cloud.google.com/anthos/multicluster-management/connect/overview/ + + To register a non-GKE or GKE On-Prem cluster use --context flag (with an + optional --kubeconfig flag). + + To register a GKE cluster use --gke-cluster or --gke-uri flag (no + --kubeconfig flag is required). + + In all cases, the Connect Agent that is installed in the target cluster + must authenticate to Google using a --service-account-key-file that + corresponds to a service account that has been granted gkehub.connect + permissions. + + If the cluster is already registered to another Fleet, the registration is + not successful. + + Rerunning this command against the same cluster with the same CLUSTER_NAME + and target GKEFleet is successful and upgrades the Connect Agent if a new + agent is available. + +EXAMPLES + Register a non-GKE or GKE On-Prem cluster referenced from a specific + kubeconfig file, and install the Connect Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster referenced from the default + kubeconfig file, and install the Connect Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster, and install a specific version + of the Connect Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster and output a manifest that can be + used to install the Connect Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster referenced from a GKE URI, and install the Connect + Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster referenced from a GKE Cluster location and name, and + install the Connect Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster, and install a specific version of the Connect + Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster and output a manifest that can be used to install + the Connect Agent: + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + + $ gcloud beta container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + +POSITIONAL ARGUMENTS + CLUSTER_NAME + The membership name that you choose to uniquely represents the cluster + being registered on the Fleet. + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + + Exactly one of these must be specified: + + --service-account-key-file=SERVICE_ACCOUNT_KEY_FILE + The JSON file of a Google Cloud service account private key. This + service account key is stored as a secret named creds-gcp in + gke-connect namespace. To update the creds-gcp secret in gke-connect + namespace with a new service account key file, run the following + command: + + kubectl delete secret creds-gcp -n gke-connect + + kubectl create secret generic creds-gcp -n gke-connect + --from-file=creds-gcp.json=/path/to/file + + Workload Identity + + --enable-workload-identity + Enable Workload Identity when registering the cluster with Fleet. + Ensure that GKE Workload Identity is enabled on your GKE cluster, + it is a requirement for using Workload Identity with memberships. + Refer to the Registering a cluster using Workload Identity section + in + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster#register_cluster + --service_account_key_file flag should not be set if this is set. + + This flag must be specified if any of the other arguments in this + group are specified. + + At most one of these can be specified: + + --has-private-issuer + Set to true for clusters where no publicly-routable OIDC + discovery endpoint for the Kubernetes service account token + issuer exists. + + When set to true, the gcloud command-line tool will read the + private issuer URL and JSON Web Key Set (JWKS) (public keys) for + validating service account tokens from the cluster's API server + and upload both when creating the Membership. Google Cloud + Platform will then use the JWKS, instead of a public OIDC + endpoint, to validate service account tokens issued by this + cluster. Note the JWKS establishes the uniqueness of issuers in + this configuration, but issuer claims in tokens are still + compared to the issuer URL associated with the Membership when + validating tokens. + + Note the cluster's OIDC discovery endpoints (KUBE-API-ADDRESS + (https://)/.well-known/openid-configuration and KUBE-API-ADDRESS + (https://)/openid/v1/jwks) must still be network-accessible to + the gcloud client running this command. + + --public-issuer-url=PUBLIC_ISSUER_URL + Skip auto-discovery and register the cluster with this issuer + URL. Use this option when the OpenID Provider Configuration and + associated JSON Web Key Set for validating the cluster's service + account JWTs are served at a public endpoint different from the + cluster API server. Requires --enable-workload-identity. + +OPTIONAL FLAGS + --internal-ip + Whether to use the internal IP address of the cluster endpoint. + + --manifest-output-file=MANIFEST_OUTPUT_FILE + The full path of the file into which the Connect Agent installation + manifest should be stored. If this option is provided, then the + manifest will be written to this file and will not be deployed into the + cluster by gcloud, and it will need to be deployed manually. + + --proxy=PROXY + The proxy address in the format of http[s]://{hostname}. The proxy must + support the HTTP CONNECT method in order for this connection to + succeed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships register + + $ gcloud alpha container fleet memberships register + diff --git a/gcloud/beta/container/fleet/memberships/unregister b/gcloud/beta/container/fleet/memberships/unregister new file mode 100644 index 000000000..17fa4a42c --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/unregister @@ -0,0 +1,114 @@ +NAME + gcloud beta container fleet memberships unregister - unregister a cluster + from Fleet + +SYNOPSIS + gcloud beta container fleet memberships unregister CLUSTER_NAME + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command unregisters a cluster with the Fleet by: + + 1. Deleting the Fleet Membership resource for this cluster (a.k.a + `gcloud beta container fleet memberships delete`). + 2. Removing the corresponding in-cluster Kubernetes Resources that make the + cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + membership`). + 3. Uninstalling the Connect Agent from this cluster (a.k.a + `kubectl delete on the gke-connect namespace`). + + The unregister command makes additional internal checks to ensure that all + three steps can be safely done to properly clean-up in-Fleet and in-cluster + resources. + + To register a non-GKE cluster use --context flag (with an optional + --kubeconfig flag). + + To register a GKE cluster use --gke-cluster or --gke-uri flag (no + --kubeconfig flag is required). + + To only delete the Fleet membership resource, consider using the command: + gcloud beta container fleet memberships delete. This command is intended to + delete stale Fleet Membership resources as doing so on a fully registered + cluster will skip some of the steps above and orphan in-cluster resources + and agent connections to Google. + +EXAMPLES + Unregister a non-GKE cluster referenced from a specific kubeconfig file: + + $ gcloud beta container fleet memberships unregister my-membership \ + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig + + Unregister a non-GKE cluster referenced from the default kubeconfig file: + + $ gcloud beta container fleet memberships unregister my-membership \ + --context=my-cluster-context + + Unregister a GKE cluster referenced from a GKE URI: + + $ gcloud beta container fleet memberships unregister my-membership \ + --gke-uri=my-cluster-gke-uri + + Unregister a GKE cluster referenced from a GKE Cluster location and name: + + $ gcloud beta container fleet memberships unregister my-membership \ + --gke-cluster=my-cluster-region-or-zone/my-cluster + +POSITIONAL ARGUMENTS + CLUSTER_NAME + The membership name that corresponds to the cluster being unregistered. + To get list of all the memberships on the Fleet, consider using the + command: gcloud beta container fleet memberships list. + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships unregister + + $ gcloud alpha container fleet memberships unregister + diff --git a/gcloud/beta/container/fleet/memberships/update b/gcloud/beta/container/fleet/memberships/update new file mode 100644 index 000000000..550b3b0d5 --- /dev/null +++ b/gcloud/beta/container/fleet/memberships/update @@ -0,0 +1,99 @@ +NAME + gcloud beta container fleet memberships update - update a membership + +SYNOPSIS + gcloud beta container fleet memberships update + (MEMBERSHIP : --location=LOCATION) [--async] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Update an existing membership in Fleet. + +EXAMPLES + Update a membership for a cluster: + + $ gcloud beta container fleet memberships update a-membership + +POSITIONAL ARGUMENTS + Membership resource - membership resource representing a cluster in Fleet. + 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud beta container fleet memberships update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud beta container fleet memberships update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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 gkehub/v1beta1 API. The full documentation for this + API can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet memberships update + + $ gcloud alpha container fleet memberships update + diff --git a/gcloud/beta/container/fleet/mesh/describe b/gcloud/beta/container/fleet/mesh/describe new file mode 100644 index 000000000..941d6e403 --- /dev/null +++ b/gcloud/beta/container/fleet/mesh/describe @@ -0,0 +1,31 @@ +NAME + gcloud beta container fleet mesh describe - describe the status of Service + Mesh Feature resource + +SYNOPSIS + gcloud beta container fleet mesh describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Describe the status of Service Mesh Feature resource in a fleet. + +EXAMPLES + To describe the Service Mesh Feature, run: + + $ gcloud beta container fleet mesh describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet mesh describe + + $ gcloud alpha container fleet mesh describe + diff --git a/gcloud/beta/container/fleet/mesh/disable b/gcloud/beta/container/fleet/mesh/disable new file mode 100644 index 000000000..66167e9d1 --- /dev/null +++ b/gcloud/beta/container/fleet/mesh/disable @@ -0,0 +1,35 @@ +NAME + gcloud beta container fleet mesh disable - disable Service Mesh Feature + +SYNOPSIS + gcloud beta container fleet mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Disable the Service Mesh Feature in a fleet. + +EXAMPLES + To disable the Service Mesh Feature, run: + + $ gcloud beta container fleet mesh disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet mesh disable + + $ gcloud alpha container fleet mesh disable + diff --git a/gcloud/beta/container/fleet/mesh/enable b/gcloud/beta/container/fleet/mesh/enable new file mode 100644 index 000000000..1b31a0d5b --- /dev/null +++ b/gcloud/beta/container/fleet/mesh/enable @@ -0,0 +1,30 @@ +NAME + gcloud beta container fleet mesh enable - enable Service Mesh Feature + +SYNOPSIS + gcloud beta container fleet mesh enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Enable the Service Mesh Feature in a fleet. + +EXAMPLES + To enable the Service Mesh Feature, run: + + $ gcloud beta container fleet mesh enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet mesh enable + + $ gcloud alpha container fleet mesh enable + diff --git a/gcloud/beta/container/fleet/mesh/help b/gcloud/beta/container/fleet/mesh/help new file mode 100644 index 000000000..782af6614 --- /dev/null +++ b/gcloud/beta/container/fleet/mesh/help @@ -0,0 +1,34 @@ +NAME + gcloud beta container fleet mesh - manage Service Mesh Feature + +SYNOPSIS + gcloud beta container fleet mesh COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Service Mesh Feature. + +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 the status of Service Mesh Feature resource. + + disable + (BETA) Disable Service Mesh Feature. + + enable + (BETA) Enable Service Mesh Feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet mesh + + $ gcloud alpha container fleet mesh + diff --git a/gcloud/beta/container/fleet/multi-cluster-services/describe b/gcloud/beta/container/fleet/multi-cluster-services/describe new file mode 100644 index 000000000..b7debe5fa --- /dev/null +++ b/gcloud/beta/container/fleet/multi-cluster-services/describe @@ -0,0 +1,33 @@ +NAME + gcloud beta container fleet multi-cluster-services describe - describe the + status of the Multi-cluster Services Feature resource + +SYNOPSIS + gcloud beta container fleet multi-cluster-services describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command gets the detailed status of the Multi-cluster Services + Feature in a fleet. + +EXAMPLES + To describe the Multi-cluster Services Feature, run: + + $ gcloud beta container fleet multi-cluster-services describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet multi-cluster-services describe + + $ gcloud alpha container fleet multi-cluster-services describe + diff --git a/gcloud/beta/container/fleet/multi-cluster-services/disable b/gcloud/beta/container/fleet/multi-cluster-services/disable new file mode 100644 index 000000000..2d3430231 --- /dev/null +++ b/gcloud/beta/container/fleet/multi-cluster-services/disable @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet multi-cluster-services disable - disable the + Multi-cluster Services Feature + +SYNOPSIS + gcloud beta container fleet multi-cluster-services disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command disables the Multi-cluster Services Feature in a fleet. + +EXAMPLES + To disable the Multi-cluster Services Feature, run: + + $ gcloud beta container fleet multi-cluster-services disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet multi-cluster-services disable + + $ gcloud alpha container fleet multi-cluster-services disable + diff --git a/gcloud/beta/container/fleet/multi-cluster-services/enable b/gcloud/beta/container/fleet/multi-cluster-services/enable new file mode 100644 index 000000000..9cf5de293 --- /dev/null +++ b/gcloud/beta/container/fleet/multi-cluster-services/enable @@ -0,0 +1,32 @@ +NAME + gcloud beta container fleet multi-cluster-services enable - enable the + Multi-cluster Services Feature + +SYNOPSIS + gcloud beta container fleet multi-cluster-services enable + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) This command enables the Multi-cluster Services Feature in a fleet. + +EXAMPLES + To enable the Multi-cluster Services Feature, run: + + $ gcloud beta container fleet multi-cluster-services enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet multi-cluster-services enable + + $ gcloud alpha container fleet multi-cluster-services enable + diff --git a/gcloud/beta/container/fleet/multi-cluster-services/help b/gcloud/beta/container/fleet/multi-cluster-services/help new file mode 100644 index 000000000..452f94ce4 --- /dev/null +++ b/gcloud/beta/container/fleet/multi-cluster-services/help @@ -0,0 +1,37 @@ +NAME + gcloud beta container fleet multi-cluster-services - manage Multi-cluster + Services Feature + +SYNOPSIS + gcloud beta container fleet multi-cluster-services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + (BETA) Manage Multi-cluster Services Feature. + +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 the status of the Multi-cluster Services Feature + resource. + + disable + (BETA) Disable the Multi-cluster Services Feature. + + enable + (BETA) Enable the Multi-cluster Services Feature. + +NOTES + This command is currently in beta and might change without notice. These + variants are also available: + + $ gcloud container fleet multi-cluster-services + + $ gcloud alpha container fleet multi-cluster-services + diff --git a/gcloud/beta/container/help b/gcloud/beta/container/help index 4d64aeb75..8a5f86be4 100644 --- a/gcloud/beta/container/help +++ b/gcloud/beta/container/help @@ -23,9 +23,13 @@ GROUPS clusters (BETA) Deploy and teardown Google Kubernetes Engine clusters. + fleet + (BETA) Centrally manage features and services on all your Kubernetes + clusters with fleet. + hub (BETA) Centrally manage features and services on all your Kubernetes - clusters with Hub. + clusters with fleet. images (BETA) List and manipulate Google Container Registry images. diff --git a/gcloud/beta/container/hub/help b/gcloud/beta/container/hub/help index 2bb5f3a57..577d63fbd 100644 --- a/gcloud/beta/container/hub/help +++ b/gcloud/beta/container/hub/help @@ -1,6 +1,6 @@ NAME gcloud beta container hub - centrally manage features and services on all - your Kubernetes clusters with Hub + your Kubernetes clusters with fleet SYNOPSIS gcloud beta container hub GROUP [GCLOUD_WIDE_FLAG ...] @@ -8,15 +8,16 @@ SYNOPSIS DESCRIPTION (BETA) The command group to register GKE or other Kubernetes clusters running in a variety of environments, including Google cloud, on premises - in customer datacenters, or other third party clouds with Hub. Hub provides - a centralized control-plane to managed features and services on all - registered clusters. + in customer datacenters, or other third party clouds with fleet. Fleet + provides a centralized control-plane to managed features and services on + all registered clusters. A registered cluster is always associated with a Membership, a resource - within Hub. + within fleet. EXAMPLES - Manage memberships of all your GKE and other Kubernetes clusters with Hub: + Manage memberships of all your GKE and other Kubernetes clusters with + fleet: $ gcloud beta container hub memberships --help diff --git a/gcloud/beta/run/deploy b/gcloud/beta/run/deploy index 228e4fc22..217753186 100644 --- a/gcloud/beta/run/deploy +++ b/gcloud/beta/run/deploy @@ -10,7 +10,8 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--port=PORT] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--[no-]use-http2] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -43,16 +44,18 @@ DESCRIPTION EXAMPLES To deploy a container to the service my-backend on Cloud Run: - $ gcloud beta run deploy my-backend --image=gcr.io/my/image + $ gcloud beta run deploy my-backend \ + --image=us-docker.pkg.dev/project/image You may also omit the service name. Then a prompt will be displayed with a suggested default value: - $ gcloud beta run deploy --image=gcr.io/my/image + $ gcloud beta run deploy --image=us-docker.pkg.dev/project/image To deploy to Cloud Run on Kubernetes Engine, you need to specify a cluster: - $ gcloud beta run deploy --image=gcr.io/my/image --cluster=my-cluster + $ gcloud beta run deploy --image=us-docker.pkg.dev/project/image \ + --cluster=my-cluster POSITIONAL ARGUMENTS Service resource - Service to deploy to. The arguments in this group can @@ -205,6 +208,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/beta/run/services/update b/gcloud/beta/run/services/update index 71d4cac3f..ccae6be16 100644 --- a/gcloud/beta/run/services/update +++ b/gcloud/beta/run/services/update @@ -23,7 +23,8 @@ SYNOPSIS | --clear-binary-authorization --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -303,6 +304,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/compute/disks/snapshot b/gcloud/compute/disks/snapshot index d8850d1c1..d5e4eeaab 100644 --- a/gcloud/compute/disks/snapshot +++ b/gcloud/compute/disks/snapshot @@ -67,8 +67,7 @@ FLAGS --guest-flush Create an application-consistent snapshot by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/compute/machine-images/create b/gcloud/compute/machine-images/create index 2a9f037c2..01cdd3864 100644 --- a/gcloud/compute/machine-images/create +++ b/gcloud/compute/machine-images/create @@ -47,8 +47,7 @@ OPTIONAL FLAGS --guest-flush Create an application-consistent machine image by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --require-csek-key-create Refuse to create machine images not protected by a user managed key in diff --git a/gcloud/compute/machine-images/import b/gcloud/compute/machine-images/import index a373e47c6..53b02ed08 100644 --- a/gcloud/compute/machine-images/import +++ b/gcloud/compute/machine-images/import @@ -117,8 +117,7 @@ OPTIONAL FLAGS --guest-flush Create an application-consistent machine image by informing the OS to - prepare for the snapshot process. Currently only supported on Windows - instances using the Volume Shadow Copy Service (VSS). + prepare for the snapshot process. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. diff --git a/gcloud/config/get b/gcloud/config/get index 8c9c3d98a..6055454c3 100644 --- a/gcloud/config/get +++ b/gcloud/config/get @@ -75,6 +75,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/config/help b/gcloud/config/help index 40cd00f88..e43288b27 100644 --- a/gcloud/config/help +++ b/gcloud/config/help @@ -107,6 +107,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/config/list b/gcloud/config/list index 7fedc5c0a..926e4c3ee 100644 --- a/gcloud/config/list +++ b/gcloud/config/list @@ -109,6 +109,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/config/set b/gcloud/config/set index a7f7fd4f7..6babad071 100644 --- a/gcloud/config/set +++ b/gcloud/config/set @@ -122,6 +122,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/config/unset b/gcloud/config/unset index 92c358df1..33c83eb3d 100644 --- a/gcloud/config/unset +++ b/gcloud/config/unset @@ -83,6 +83,9 @@ AVAILABLE PROPERTIES installation, but can be changed at any time. For more information, see: https://cloud.google.com/sdk/usage-statistics + enable_feature_flags + If True, remote config-file driven feature flags will be enabled. + log_http If True, log HTTP requests and responses to the logs. To see logs in the terminal, adjust verbosity settings. Otherwise, logs are diff --git a/gcloud/container/binauthz/attestors/public-keys/add b/gcloud/container/binauthz/attestors/public-keys/add index d84eb8862..4dc12d506 100644 --- a/gcloud/container/binauthz/attestors/public-keys/add +++ b/gcloud/container/binauthz/attestors/public-keys/add @@ -111,7 +111,9 @@ REQUIRED FLAGS ecdsa-p384-sha384, ecdsa-p521-sha512, rsa-pss-2048-sha256, rsa-pss-3072-sha256, rsa-pss-4096-sha256, rsa-pss-4096-sha512, rsa-sign-pkcs1-2048-sha256, rsa-sign-pkcs1-3072-sha256, - rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512. + rsa-sign-pkcs1-4096-sha256, rsa-sign-pkcs1-4096-sha512, + rsa-sign-pss-2048-sha256, rsa-sign-pss-3072-sha256, + rsa-sign-pss-4096-sha256, rsa-sign-pss-4096-sha512. This flag must be specified if any of the other arguments in this group are specified. diff --git a/gcloud/container/fleet/cloudrun/apply b/gcloud/container/fleet/cloudrun/apply new file mode 100644 index 000000000..1f99bee56 --- /dev/null +++ b/gcloud/container/fleet/cloudrun/apply @@ -0,0 +1,73 @@ +NAME + gcloud container fleet cloudrun apply - deploy or update the CloudRun + feature + +SYNOPSIS + gcloud container fleet cloudrun apply + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) [--config=CONFIG] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Deploy or update a user-specified config file of the CloudRun custom + resource. The config file should be a YAML file. + +EXAMPLES + To apply the CloudRun YAML file, run: + + $ gcloud container fleet cloudrun apply \ + --kubeconfig=/path/to/kubeconfig \ + --config=/path/to/cloud-run-cr.yaml + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + +OPTIONAL FLAGS + --config=CONFIG + The path to CloudRun custom resource config file. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet cloudrun apply + + $ gcloud beta container fleet cloudrun apply + diff --git a/gcloud/container/fleet/cloudrun/describe b/gcloud/container/fleet/cloudrun/describe new file mode 100644 index 000000000..c55ee18d0 --- /dev/null +++ b/gcloud/container/fleet/cloudrun/describe @@ -0,0 +1,28 @@ +NAME + gcloud container fleet cloudrun describe - describe the status of the + CloudRun feature + +SYNOPSIS + gcloud container fleet cloudrun describe [GCLOUD_WIDE_FLAG ...] + +EXAMPLES + To get the detailed current status of the CloudRun Feature in Anthos + clusters, run: + + $ gcloud container fleet cloudrun describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet cloudrun describe + + $ gcloud beta container fleet cloudrun describe + diff --git a/gcloud/container/fleet/cloudrun/disable b/gcloud/container/fleet/cloudrun/disable new file mode 100644 index 000000000..d08fc63d5 --- /dev/null +++ b/gcloud/container/fleet/cloudrun/disable @@ -0,0 +1,34 @@ +NAME + gcloud container fleet cloudrun disable - disable the CloudRun feature + +SYNOPSIS + gcloud container fleet cloudrun disable [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables the CloudRun feature in Anthos clusters. + +EXAMPLES + To disable the CloudRun Feature, run: + + $ gcloud container fleet cloudrun disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet cloudrun disable + + $ gcloud beta container fleet cloudrun disable + diff --git a/gcloud/container/fleet/cloudrun/enable b/gcloud/container/fleet/cloudrun/enable new file mode 100644 index 000000000..e38d03ed9 --- /dev/null +++ b/gcloud/container/fleet/cloudrun/enable @@ -0,0 +1,29 @@ +NAME + gcloud container fleet cloudrun enable - enable the CloudRun feature + +SYNOPSIS + gcloud container fleet cloudrun enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables the CloudRun feature in Anthos clusters. + +EXAMPLES + To enable the CloudRun Feature, run: + + $ gcloud container fleet cloudrun enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet cloudrun enable + + $ gcloud beta container fleet cloudrun enable + diff --git a/gcloud/container/fleet/cloudrun/help b/gcloud/container/fleet/cloudrun/help new file mode 100644 index 000000000..e77a00b67 --- /dev/null +++ b/gcloud/container/fleet/cloudrun/help @@ -0,0 +1,36 @@ +NAME + gcloud container fleet cloudrun - manage the CloudRun feature + +SYNOPSIS + gcloud container fleet cloudrun COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage the CloudRun feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + apply + Deploy or update the CloudRun feature. + + describe + Describe the status of the CloudRun feature. + + disable + Disable the CloudRun feature. + + enable + Enable the CloudRun feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet cloudrun + + $ gcloud beta container fleet cloudrun + diff --git a/gcloud/container/fleet/features/help b/gcloud/container/fleet/features/help new file mode 100644 index 000000000..17e73afa1 --- /dev/null +++ b/gcloud/container/fleet/features/help @@ -0,0 +1,29 @@ +NAME + gcloud container fleet features - manage Hub Feature resources + +SYNOPSIS + gcloud container fleet features COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + These commands manage Features generically. Most Features offer specialized + commands under dedicated sub-groups that may be more effective for that + specific Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + list + List enabled features. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet features + + $ gcloud beta container fleet features + diff --git a/gcloud/container/fleet/features/list b/gcloud/container/fleet/features/list new file mode 100644 index 000000000..6e2107379 --- /dev/null +++ b/gcloud/container/fleet/features/list @@ -0,0 +1,86 @@ +NAME + gcloud container fleet features list - list enabled features + +SYNOPSIS + gcloud container fleet features list [--location=LOCATION] + [--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE] + [--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List enabled Hub features in a project. + +EXAMPLES + To list all enabled Hub features in a project, run: + + $ gcloud container fleet features list + +FLAGS + Location resource - The location to list Features under. + + 'global' is the only supported value. 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; + ◆ global is the only supported location with a fully specified name; + ◆ set the property core/project; + ◆ provide the argument --project on the command line. + + --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; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + These variants are also available: + + $ gcloud alpha container fleet features list + + $ gcloud beta container fleet features list + diff --git a/gcloud/container/fleet/help b/gcloud/container/fleet/help new file mode 100644 index 000000000..0dca5068a --- /dev/null +++ b/gcloud/container/fleet/help @@ -0,0 +1,73 @@ +NAME + gcloud container fleet - centrally manage features and services on all your + Kubernetes clusters with fleet + +SYNOPSIS + gcloud container fleet GROUP [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + The command group to register GKE or other Kubernetes clusters running in a + variety of environments, including Google cloud, on premises in customer + datacenters, or other third party clouds with fleet. Fleet provides a + centralized control-plane to managed features and services on all + registered clusters. + + A registered cluster is always associated with a Membership, a resource + within fleet. + +EXAMPLES + Manage memberships of all your GKE and other Kubernetes clusters with + fleet: + + $ gcloud container fleet memberships --help + + Manage Config Management feature on all memberships: + + $ gcloud container fleet config-management --help + + Manage Multi-cluster Ingress feature on all memberships: + + $ gcloud container fleet ingress --help + + Manage Multi-cluster Services feature on all memberships: + + $ gcloud container fleet multi-cluster-services --help + + Manage CloudRun feature on all memberships: + + $ gcloud container fleet cloudrun --help + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +GROUPS + GROUP is one of the following: + + cloudrun + Manage the CloudRun feature. + + features + Manage Hub Feature resources. + + ingress + Manage Multi-cluster Ingress Feature. + + memberships + Manage memberships of all your GKE and other Kubernetes cluster with + Fleet. + + mesh + Manage Service Mesh Feature. + + multi-cluster-services + Manage Multi-cluster Services Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet + + $ gcloud beta container fleet + diff --git a/gcloud/container/fleet/ingress/describe b/gcloud/container/fleet/ingress/describe new file mode 100644 index 000000000..3068ddd1b --- /dev/null +++ b/gcloud/container/fleet/ingress/describe @@ -0,0 +1,31 @@ +NAME + gcloud container fleet ingress describe - describe the status of + Multi-cluster Ingress Feature resource + +SYNOPSIS + gcloud container fleet ingress describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command describes the status of Multi-cluster Ingress Feature resource + in fleet. + +EXAMPLES + To describe the Ingress Feature, run: + + $ gcloud container fleet ingress describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet ingress describe + + $ gcloud beta container fleet ingress describe + diff --git a/gcloud/container/fleet/ingress/disable b/gcloud/container/fleet/ingress/disable new file mode 100644 index 000000000..721a34bff --- /dev/null +++ b/gcloud/container/fleet/ingress/disable @@ -0,0 +1,35 @@ +NAME + gcloud container fleet ingress disable - disable Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud container fleet ingress disable [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To disable the Ingress Feature, run: + + $ gcloud container fleet ingress disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet ingress disable + + $ gcloud beta container fleet ingress disable + diff --git a/gcloud/container/fleet/ingress/enable b/gcloud/container/fleet/ingress/enable new file mode 100644 index 000000000..cdd6d1cbd --- /dev/null +++ b/gcloud/container/fleet/ingress/enable @@ -0,0 +1,37 @@ +NAME + gcloud container fleet ingress enable - enable Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud container fleet ingress enable + [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To enable the Ingress Feature, run: + + $ gcloud container fleet ingress enable \ + --config-membership=CONFIG_MEMBERSHIP + +FLAGS + --config-membership=CONFIG_MEMBERSHIP + Membership resource representing the cluster which hosts the + MultiClusterIngress and MultiClusterService CustomResourceDefinitions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet ingress enable + + $ gcloud beta container fleet ingress enable + diff --git a/gcloud/container/fleet/ingress/help b/gcloud/container/fleet/ingress/help new file mode 100644 index 000000000..5cbc4d25a --- /dev/null +++ b/gcloud/container/fleet/ingress/help @@ -0,0 +1,36 @@ +NAME + gcloud container fleet ingress - manage Multi-cluster Ingress Feature + +SYNOPSIS + gcloud container fleet ingress COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Multi-cluster Ingress Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe the status of Multi-cluster Ingress Feature resource. + + disable + Disable Multi-cluster Ingress Feature. + + enable + Enable Multi-cluster Ingress Feature. + + update + Update Multi-cluster Ingress Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet ingress + + $ gcloud beta container fleet ingress + diff --git a/gcloud/container/fleet/ingress/update b/gcloud/container/fleet/ingress/update new file mode 100644 index 000000000..9f02bdfc9 --- /dev/null +++ b/gcloud/container/fleet/ingress/update @@ -0,0 +1,37 @@ +NAME + gcloud container fleet ingress update - update Multi-cluster Ingress + Feature + +SYNOPSIS + gcloud container fleet ingress update + [--config-membership=CONFIG_MEMBERSHIP] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command updates Multi-cluster Ingress Feature in a fleet. + +EXAMPLES + To update the Ingress Feature, run: + + $ gcloud container fleet ingress update \ + --config-membership=CONFIG_MEMBERSHIP + +FLAGS + --config-membership=CONFIG_MEMBERSHIP + Membership resource representing the cluster which hosts the + MultiClusterIngress and MultiClusterService CustomResourceDefinitions. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet ingress update + + $ gcloud beta container fleet ingress update + diff --git a/gcloud/container/fleet/memberships/delete b/gcloud/container/fleet/memberships/delete new file mode 100644 index 000000000..4a37e0a27 --- /dev/null +++ b/gcloud/container/fleet/memberships/delete @@ -0,0 +1,74 @@ +NAME + gcloud container fleet memberships delete - delete a membership + +SYNOPSIS + gcloud container fleet memberships delete + (MEMBERSHIP : --location=LOCATION) [--async] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command deletes the Fleet membership resource corresponding to the + cluster. + + This command is intended to delete stale Fleet Membership resources as + doing so on a fully registered cluster will skip uninstalling the Connect + Agent and and orphan in-cluster resources and agent connections to Google. + To completely unregister the cluster, consider using the command: gcloud + container fleet memberships unregister. + +EXAMPLES + Delete a membership from Fleet: + + $ gcloud container fleet memberships delete a-membership + +POSITIONAL ARGUMENTS + Membership resource - The cluster membership 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships delete + + $ gcloud beta container fleet memberships delete + diff --git a/gcloud/container/fleet/memberships/describe b/gcloud/container/fleet/memberships/describe new file mode 100644 index 000000000..59a9f10fd --- /dev/null +++ b/gcloud/container/fleet/memberships/describe @@ -0,0 +1,62 @@ +NAME + gcloud container fleet memberships describe - describe a membership + +SYNOPSIS + gcloud container fleet memberships describe + (MEMBERSHIP : --location=LOCATION) [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe a membership in Fleet. + +EXAMPLES + Describe a membership in Fleet: + + $ gcloud container fleet memberships describe a-membership + +POSITIONAL ARGUMENTS + Membership resource - The cluster membership 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported 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. + +API REFERENCE + This command uses the gkehub/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships describe + + $ gcloud beta container fleet memberships describe + diff --git a/gcloud/container/fleet/memberships/get-credentials b/gcloud/container/fleet/memberships/get-credentials new file mode 100644 index 000000000..e307fd508 --- /dev/null +++ b/gcloud/container/fleet/memberships/get-credentials @@ -0,0 +1,46 @@ +NAME + gcloud container fleet memberships get-credentials - fetch credentials for + a Fleet-registered cluster to be used in Connect Gateway + +SYNOPSIS + gcloud container fleet memberships get-credentials MEMBERSHIP + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + gcloud container fleet memberships get-credentials updates the kubeconfig + file with the appropriate credentials and endpoint information to send + kubectl commands to a Fleet-registered and connected cluster through + Connect Gateway Service. + + It takes a project, passed through by set defaults or flags. By default, + credentials are written to $HOME/.kube/config. You can provide an alternate + path by setting the KUBECONFIG environment variable. If KUBECONFIG contains + multiple paths, the first one is used. + + Upon success, this command will switch current context to the target + cluster, when working with multiple clusters. + +EXAMPLES + Get gateway kubeconfig for a registered cluster: + + $ gcloud container fleet memberships get-credentials my-cluster + +POSITIONAL ARGUMENTS + MEMBERSHIP + The membership name used to locate a cluster in your 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 + These variants are also available: + + $ gcloud alpha container fleet memberships get-credentials + + $ gcloud beta container fleet memberships get-credentials + diff --git a/gcloud/container/fleet/memberships/help b/gcloud/container/fleet/memberships/help new file mode 100644 index 000000000..d02d61d47 --- /dev/null +++ b/gcloud/container/fleet/memberships/help @@ -0,0 +1,47 @@ +NAME + gcloud container fleet memberships - manage memberships of all your GKE and + other Kubernetes cluster with Fleet + +SYNOPSIS + gcloud container fleet memberships COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage memberships of all your GKE and other Kubernetes cluster with Fleet. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + delete + Delete a membership. + + describe + Describe a membership. + + get-credentials + Fetch credentials for a Fleet-registered cluster to be used in Connect + Gateway. + + list + List memberships. + + register + Register a cluster with Fleet. + + unregister + Unregister a cluster from Fleet. + + update + Update a membership. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships + + $ gcloud beta container fleet memberships + diff --git a/gcloud/container/fleet/memberships/list b/gcloud/container/fleet/memberships/list new file mode 100644 index 000000000..af0adb5f3 --- /dev/null +++ b/gcloud/container/fleet/memberships/list @@ -0,0 +1,68 @@ +NAME + gcloud container fleet memberships list - list memberships + +SYNOPSIS + gcloud container fleet memberships list [--filter=EXPRESSION] + [--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + List memberships in Fleet. + +EXAMPLES + List memberships in Fleet: + + $ gcloud container fleet memberships list + +LIST COMMAND FLAGS + --filter=EXPRESSION + Apply a Boolean filter EXPRESSION to each resource item to be listed. + If the expression evaluates True, then that item is listed. For more + details and examples of filter expressions, run $ gcloud topic filters. + This flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --limit=LIMIT + Maximum number of resources to list. The default is unlimited. This + flag interacts with other flags that are applied in this order: + --flatten, --sort-by, --filter, --limit. + + --page-size=PAGE_SIZE + Some services group resource list output into pages. This flag + specifies the maximum number of resources per page. The default is + determined by the service if it supports paging, otherwise it is + unlimited (no paging). Paging may be applied before or after --filter + and --limit depending on the service. + + --sort-by=[FIELD,...] + Comma-separated list of resource field key names to sort by. The + default order is ascending. Prefix a field with ``~'' for descending + order on that field. This flag interacts with other flags that are + applied in this order: --flatten, --sort-by, --filter, --limit. + + --uri + Print a list of resource URIs instead of the default output, and change + the command output to a list of URIs. If this flag is used with + --format, the formatting is applied on this URI list. To display URIs + alongside other keys instead, use the uri() transform. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +API REFERENCE + This command uses the gkehub/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships list + + $ gcloud beta container fleet memberships list + diff --git a/gcloud/container/fleet/memberships/register b/gcloud/container/fleet/memberships/register new file mode 100644 index 000000000..2fe319f77 --- /dev/null +++ b/gcloud/container/fleet/memberships/register @@ -0,0 +1,243 @@ +NAME + gcloud container fleet memberships register - register a cluster with Fleet + +SYNOPSIS + gcloud container fleet memberships register CLUSTER_NAME + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) + (--service-account-key-file=SERVICE_ACCOUNT_KEY_FILE + | [--enable-workload-identity : --has-private-issuer + | --public-issuer-url=PUBLIC_ISSUER_URL]) [--internal-ip] + [--manifest-output-file=MANIFEST_OUTPUT_FILE] [--proxy=PROXY] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command registers a cluster with the Fleet by: + + 1. Creating a Fleet Membership resource corresponding to the cluster. + 2. Adding in-cluster Kubernetes Resources that make the cluster exclusive + to one Fleet. + 3. Installing the Connect Agent into this cluster. + + A successful registration implies that the cluster is now exclusive to a + single Fleet. + + For more information about Connect Agent, go to: + https://cloud.google.com/anthos/multicluster-management/connect/overview/ + + To register a non-GKE or GKE On-Prem cluster use --context flag (with an + optional --kubeconfig flag). + + To register a GKE cluster use --gke-cluster or --gke-uri flag (no + --kubeconfig flag is required). + + In all cases, the Connect Agent that is installed in the target cluster + must authenticate to Google using a --service-account-key-file that + corresponds to a service account that has been granted gkehub.connect + permissions. + + If the cluster is already registered to another Fleet, the registration is + not successful. + + Rerunning this command against the same cluster with the same CLUSTER_NAME + and target GKEFleet is successful and upgrades the Connect Agent if a new + agent is available. + +EXAMPLES + Register a non-GKE or GKE On-Prem cluster referenced from a specific + kubeconfig file, and install the Connect Agent: + + $ gcloud container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster referenced from the default + kubeconfig file, and install the Connect Agent: + + $ gcloud container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster, and install a specific version + of the Connect Agent: + + $ gcloud container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + Register a non-GKE or GKE On-Prem cluster and output a manifest that can be + used to install the Connect Agent: + + $ gcloud container fleet memberships register my-cluster \ + --context=my-cluster-context \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster referenced from a GKE URI, and install the Connect + Agent: + + $ gcloud container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster referenced from a GKE Cluster location and name, and + install the Connect Agent: + + $ gcloud container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster, and install a specific version of the Connect + Agent: + + $ gcloud container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + $ gcloud container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --version=gkeconnect_20190802_02_00 \ + --service-account-key-file=/tmp/keyfile.json + + Register a GKE cluster and output a manifest that can be used to install + the Connect Agent: + + $ gcloud container fleet memberships register my-cluster \ + --gke-uri=my-cluster-gke-uri \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + + $ gcloud container fleet memberships register my-cluster \ + --gke-cluster=my-cluster-region-or-zone/my-cluster \ + --manifest-output-file=/tmp/manifest.yaml \ + --service-account-key-file=/tmp/keyfile.json + +POSITIONAL ARGUMENTS + CLUSTER_NAME + The membership name that you choose to uniquely represents the cluster + being registered on the Fleet. + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + + Exactly one of these must be specified: + + --service-account-key-file=SERVICE_ACCOUNT_KEY_FILE + The JSON file of a Google Cloud service account private key. This + service account key is stored as a secret named creds-gcp in + gke-connect namespace. To update the creds-gcp secret in gke-connect + namespace with a new service account key file, run the following + command: + + kubectl delete secret creds-gcp -n gke-connect + + kubectl create secret generic creds-gcp -n gke-connect + --from-file=creds-gcp.json=/path/to/file + + Workload Identity + + --enable-workload-identity + Enable Workload Identity when registering the cluster with Fleet. + Ensure that GKE Workload Identity is enabled on your GKE cluster, + it is a requirement for using Workload Identity with memberships. + Refer to the Registering a cluster using Workload Identity section + in + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster#register_cluster + --service_account_key_file flag should not be set if this is set. + + This flag must be specified if any of the other arguments in this + group are specified. + + At most one of these can be specified: + + --has-private-issuer + Set to true for clusters where no publicly-routable OIDC + discovery endpoint for the Kubernetes service account token + issuer exists. + + When set to true, the gcloud command-line tool will read the + private issuer URL and JSON Web Key Set (JWKS) (public keys) for + validating service account tokens from the cluster's API server + and upload both when creating the Membership. Google Cloud + Platform will then use the JWKS, instead of a public OIDC + endpoint, to validate service account tokens issued by this + cluster. Note the JWKS establishes the uniqueness of issuers in + this configuration, but issuer claims in tokens are still + compared to the issuer URL associated with the Membership when + validating tokens. + + Note the cluster's OIDC discovery endpoints (KUBE-API-ADDRESS + (https://)/.well-known/openid-configuration and KUBE-API-ADDRESS + (https://)/openid/v1/jwks) must still be network-accessible to + the gcloud client running this command. + + --public-issuer-url=PUBLIC_ISSUER_URL + Skip auto-discovery and register the cluster with this issuer + URL. Use this option when the OpenID Provider Configuration and + associated JSON Web Key Set for validating the cluster's service + account JWTs are served at a public endpoint different from the + cluster API server. Requires --enable-workload-identity. + +OPTIONAL FLAGS + --internal-ip + Whether to use the internal IP address of the cluster endpoint. + + --manifest-output-file=MANIFEST_OUTPUT_FILE + The full path of the file into which the Connect Agent installation + manifest should be stored. If this option is provided, then the + manifest will be written to this file and will not be deployed into the + cluster by gcloud, and it will need to be deployed manually. + + --proxy=PROXY + The proxy address in the format of http[s]://{hostname}. The proxy must + support the HTTP CONNECT method in order for this connection to + succeed. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships register + + $ gcloud beta container fleet memberships register + diff --git a/gcloud/container/fleet/memberships/unregister b/gcloud/container/fleet/memberships/unregister new file mode 100644 index 000000000..056667294 --- /dev/null +++ b/gcloud/container/fleet/memberships/unregister @@ -0,0 +1,113 @@ +NAME + gcloud container fleet memberships unregister - unregister a cluster from + Fleet + +SYNOPSIS + gcloud container fleet memberships unregister CLUSTER_NAME + (--gke-cluster=LOCATION/CLUSTER_NAME | --gke-uri=GKE_URI + | [--context=CONTEXT : --kubeconfig=KUBECONFIG]) + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command unregisters a cluster with the Fleet by: + + 1. Deleting the Fleet Membership resource for this cluster (a.k.a + `gcloud container fleet memberships delete`). + 2. Removing the corresponding in-cluster Kubernetes Resources that make the + cluster exclusive to one Fleet (a.k.a `kubectl delete memberships + membership`). + 3. Uninstalling the Connect Agent from this cluster (a.k.a + `kubectl delete on the gke-connect namespace`). + + The unregister command makes additional internal checks to ensure that all + three steps can be safely done to properly clean-up in-Fleet and in-cluster + resources. + + To register a non-GKE cluster use --context flag (with an optional + --kubeconfig flag). + + To register a GKE cluster use --gke-cluster or --gke-uri flag (no + --kubeconfig flag is required). + + To only delete the Fleet membership resource, consider using the command: + gcloud container fleet memberships delete. This command is intended to + delete stale Fleet Membership resources as doing so on a fully registered + cluster will skip some of the steps above and orphan in-cluster resources + and agent connections to Google. + +EXAMPLES + Unregister a non-GKE cluster referenced from a specific kubeconfig file: + + $ gcloud container fleet memberships unregister my-membership \ + --context=my-cluster-context \ + --kubeconfig=/home/user/custom_kubeconfig + + Unregister a non-GKE cluster referenced from the default kubeconfig file: + + $ gcloud container fleet memberships unregister my-membership \ + --context=my-cluster-context + + Unregister a GKE cluster referenced from a GKE URI: + + $ gcloud container fleet memberships unregister my-membership \ + --gke-uri=my-cluster-gke-uri + + Unregister a GKE cluster referenced from a GKE Cluster location and name: + + $ gcloud container fleet memberships unregister my-membership \ + --gke-cluster=my-cluster-region-or-zone/my-cluster + +POSITIONAL ARGUMENTS + CLUSTER_NAME + The membership name that corresponds to the cluster being unregistered. + To get list of all the memberships on the Fleet, consider using the + command: gcloud container fleet memberships list. + +REQUIRED FLAGS + Cluster identifier. + + Exactly one of these must be specified: + + --gke-cluster=LOCATION/CLUSTER_NAME + The location/name of the GKE cluster. The location can be a zone or a + region for e.g us-central1-a/my-cluster. + + --gke-uri=GKE_URI + The URI of a GKE cluster that you want to register to Hub; for + example, + 'https://container.googleapis.com/v1/projects/my-project/locations/us-central1-a/clusters/my-cluster'. + To obtain the URI, you can run 'gcloud container clusters list + --uri'. Note that this should only be provided if the cluster being + registered is a GKE cluster. The service will validate the provided + URI to confirm that it maps to a valid GKE cluster." + + Non-GKE cluster identifier. + + --context=CONTEXT + The cluster context as it appears in the kubeconfig file. You can + get this value from the command line by running command: kubectl + config current-context. + + This flag must be specified if any of the other arguments in this + group are specified. + + --kubeconfig=KUBECONFIG + The kubeconfig file containing an entry for the cluster. Defaults + to $KUBECONFIG if it is set in the environment, otherwise defaults + to $HOME/.kube/config. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships unregister + + $ gcloud beta container fleet memberships unregister + diff --git a/gcloud/container/fleet/memberships/update b/gcloud/container/fleet/memberships/update new file mode 100644 index 000000000..36652cc38 --- /dev/null +++ b/gcloud/container/fleet/memberships/update @@ -0,0 +1,98 @@ +NAME + gcloud container fleet memberships update - update a membership + +SYNOPSIS + gcloud container fleet memberships update + (MEMBERSHIP : --location=LOCATION) [--async] + [--update-labels=[KEY=VALUE,...]] + [--clear-labels | --remove-labels=[KEY,...]] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update an existing membership in Fleet. + +EXAMPLES + Update a membership for a cluster: + + $ gcloud container fleet memberships update a-membership + +POSITIONAL ARGUMENTS + Membership resource - membership resource representing a cluster in Fleet. + 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 membership 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. + + MEMBERSHIP + ID of the membership or fully qualified identifier for the + membership. To set the membership attribute: + ▸ provide the argument membership on the command line. + + This positional must be specified if any of the other arguments in + this group are specified. + + --location=LOCATION + The location name. To set the location attribute: + ▸ provide the argument membership on the command line with a fully + specified name; + ▸ provide the argument --location on the command line; + ▸ global is the only supported location. + +FLAGS + --async + Return immediately, without waiting for the operation in progress to + complete. + + --update-labels=[KEY=VALUE,...] + List of label KEY=VALUE pairs to update. If a label exists, its value + is modified. Otherwise, a new label is created. + + Keys must start with a lowercase character and contain only hyphens + (-), underscores (_), lowercase characters, and numbers. Values must + contain only hyphens (-), underscores (_), lowercase characters, and + numbers. + + At most one of these can be specified: + + --clear-labels + Remove all labels. If --update-labels is also specified then + --clear-labels is applied first. + + For example, to remove all labels: + + $ gcloud container fleet memberships update --clear-labels + + To remove all existing labels and create two new labels, foo and baz: + + $ gcloud container fleet memberships update --clear-labels \ + --update-labels foo=bar,baz=qux + + --remove-labels=[KEY,...] + List of label keys to remove. If a label does not exist it is + silently ignored. If --update-labels is also specified then + --update-labels is applied first. + +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 gkehub/v1 API. The full documentation for this API + can be found at: + https://cloud.google.com/anthos/multicluster-management/connect/registering-a-cluster + +NOTES + These variants are also available: + + $ gcloud alpha container fleet memberships update + + $ gcloud beta container fleet memberships update + diff --git a/gcloud/container/fleet/mesh/describe b/gcloud/container/fleet/mesh/describe new file mode 100644 index 000000000..5bc84f339 --- /dev/null +++ b/gcloud/container/fleet/mesh/describe @@ -0,0 +1,30 @@ +NAME + gcloud container fleet mesh describe - describe the status of Service Mesh + Feature resource + +SYNOPSIS + gcloud container fleet mesh describe [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Describe the status of Service Mesh Feature resource in a fleet. + +EXAMPLES + To describe the Service Mesh Feature, run: + + $ gcloud container fleet mesh describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet mesh describe + + $ gcloud beta container fleet mesh describe + diff --git a/gcloud/container/fleet/mesh/disable b/gcloud/container/fleet/mesh/disable new file mode 100644 index 000000000..ec0eb1b8c --- /dev/null +++ b/gcloud/container/fleet/mesh/disable @@ -0,0 +1,34 @@ +NAME + gcloud container fleet mesh disable - disable Service Mesh Feature + +SYNOPSIS + gcloud container fleet mesh disable [--force] [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Disable the Service Mesh Feature in a fleet. + +EXAMPLES + To disable the Service Mesh Feature, run: + + $ gcloud container fleet mesh disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet mesh disable + + $ gcloud beta container fleet mesh disable + diff --git a/gcloud/container/fleet/mesh/enable b/gcloud/container/fleet/mesh/enable new file mode 100644 index 000000000..21d8135e3 --- /dev/null +++ b/gcloud/container/fleet/mesh/enable @@ -0,0 +1,29 @@ +NAME + gcloud container fleet mesh enable - enable Service Mesh Feature + +SYNOPSIS + gcloud container fleet mesh enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Enable the Service Mesh Feature in a fleet. + +EXAMPLES + To enable the Service Mesh Feature, run: + + $ gcloud container fleet mesh enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet mesh enable + + $ gcloud beta container fleet mesh enable + diff --git a/gcloud/container/fleet/mesh/help b/gcloud/container/fleet/mesh/help new file mode 100644 index 000000000..7b3588cb5 --- /dev/null +++ b/gcloud/container/fleet/mesh/help @@ -0,0 +1,33 @@ +NAME + gcloud container fleet mesh - manage Service Mesh Feature + +SYNOPSIS + gcloud container fleet mesh COMMAND [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Service Mesh Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe the status of Service Mesh Feature resource. + + disable + Disable Service Mesh Feature. + + enable + Enable Service Mesh Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet mesh + + $ gcloud beta container fleet mesh + diff --git a/gcloud/container/fleet/multi-cluster-services/describe b/gcloud/container/fleet/multi-cluster-services/describe new file mode 100644 index 000000000..f12d8282f --- /dev/null +++ b/gcloud/container/fleet/multi-cluster-services/describe @@ -0,0 +1,32 @@ +NAME + gcloud container fleet multi-cluster-services describe - describe the + status of the Multi-cluster Services Feature resource + +SYNOPSIS + gcloud container fleet multi-cluster-services describe + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command gets the detailed status of the Multi-cluster Services Feature + in a fleet. + +EXAMPLES + To describe the Multi-cluster Services Feature, run: + + $ gcloud container fleet multi-cluster-services describe + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet multi-cluster-services describe + + $ gcloud beta container fleet multi-cluster-services describe + diff --git a/gcloud/container/fleet/multi-cluster-services/disable b/gcloud/container/fleet/multi-cluster-services/disable new file mode 100644 index 000000000..19abd05db --- /dev/null +++ b/gcloud/container/fleet/multi-cluster-services/disable @@ -0,0 +1,36 @@ +NAME + gcloud container fleet multi-cluster-services disable - disable the + Multi-cluster Services Feature + +SYNOPSIS + gcloud container fleet multi-cluster-services disable [--force] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command disables the Multi-cluster Services Feature in a fleet. + +EXAMPLES + To disable the Multi-cluster Services Feature, run: + + $ gcloud container fleet multi-cluster-services disable + +FLAGS + --force + Disable this feature, even if it is currently in use. Force disablement + may result in unexpected behavior. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet multi-cluster-services disable + + $ gcloud beta container fleet multi-cluster-services disable + diff --git a/gcloud/container/fleet/multi-cluster-services/enable b/gcloud/container/fleet/multi-cluster-services/enable new file mode 100644 index 000000000..88ad42fda --- /dev/null +++ b/gcloud/container/fleet/multi-cluster-services/enable @@ -0,0 +1,30 @@ +NAME + gcloud container fleet multi-cluster-services enable - enable the + Multi-cluster Services Feature + +SYNOPSIS + gcloud container fleet multi-cluster-services enable [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + This command enables the Multi-cluster Services Feature in a fleet. + +EXAMPLES + To enable the Multi-cluster Services Feature, run: + + $ gcloud container fleet multi-cluster-services enable + +GCLOUD WIDE FLAGS + These flags are available to all commands: --access-token-file, --account, + --billing-project, --configuration, --flags-file, --flatten, --format, + --help, --impersonate-service-account, --log-http, --project, --quiet, + --trace-token, --user-output-enabled, --verbosity. + + Run $ gcloud help for details. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet multi-cluster-services enable + + $ gcloud beta container fleet multi-cluster-services enable + diff --git a/gcloud/container/fleet/multi-cluster-services/help b/gcloud/container/fleet/multi-cluster-services/help new file mode 100644 index 000000000..d358dc9f6 --- /dev/null +++ b/gcloud/container/fleet/multi-cluster-services/help @@ -0,0 +1,35 @@ +NAME + gcloud container fleet multi-cluster-services - manage Multi-cluster + Services Feature + +SYNOPSIS + gcloud container fleet multi-cluster-services COMMAND + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Manage Multi-cluster Services Feature. + +GCLOUD WIDE FLAGS + These flags are available to all commands: --help. + + Run $ gcloud help for details. + +COMMANDS + COMMAND is one of the following: + + describe + Describe the status of the Multi-cluster Services Feature resource. + + disable + Disable the Multi-cluster Services Feature. + + enable + Enable the Multi-cluster Services Feature. + +NOTES + These variants are also available: + + $ gcloud alpha container fleet multi-cluster-services + + $ gcloud beta container fleet multi-cluster-services + diff --git a/gcloud/container/help b/gcloud/container/help index 4d2cbe784..55b302de9 100644 --- a/gcloud/container/help +++ b/gcloud/container/help @@ -38,9 +38,13 @@ GROUPS clusters Deploy and teardown Google Kubernetes Engine clusters. + fleet + Centrally manage features and services on all your Kubernetes clusters + with fleet. + hub Centrally manage features and services on all your Kubernetes clusters - with Hub. + with fleet. images List and manipulate Google Container Registry images. diff --git a/gcloud/container/hub/help b/gcloud/container/hub/help index 7599fc0f3..e290d6d20 100644 --- a/gcloud/container/hub/help +++ b/gcloud/container/hub/help @@ -1,6 +1,6 @@ NAME gcloud container hub - centrally manage features and services on all your - Kubernetes clusters with Hub + Kubernetes clusters with fleet SYNOPSIS gcloud container hub GROUP [GCLOUD_WIDE_FLAG ...] @@ -8,15 +8,16 @@ SYNOPSIS DESCRIPTION The command group to register GKE or other Kubernetes clusters running in a variety of environments, including Google cloud, on premises in customer - datacenters, or other third party clouds with Hub. Hub provides a + datacenters, or other third party clouds with fleet. Fleet provides a centralized control-plane to managed features and services on all registered clusters. A registered cluster is always associated with a Membership, a resource - within Hub. + within fleet. EXAMPLES - Manage memberships of all your GKE and other Kubernetes clusters with Hub: + Manage memberships of all your GKE and other Kubernetes clusters with + fleet: $ gcloud container hub memberships --help diff --git a/gcloud/database-migration/connection-profiles/create/cloudsql b/gcloud/database-migration/connection-profiles/create/cloudsql index d9f8ab40c..51e8c91eb 100644 --- a/gcloud/database-migration/connection-profiles/create/cloudsql +++ b/gcloud/database-migration/connection-profiles/create/cloudsql @@ -8,12 +8,11 @@ SYNOPSIS --database-version=DATABASE_VERSION --source-id=SOURCE_ID --tier=TIER [--activation-policy=ACTIVATION_POLICY] [--authorized-networks=NETWORK,[NETWORK,...]] - [--auto-storage-increase=AUTO_STORAGE_INCREASE] - [--data-disk-size=DATA_DISK_SIZE] [--data-disk-type=DATA_DISK_TYPE] - [--database-flags=[KEY=VALUE,...]] [--display-name=DISPLAY_NAME] - [--enable-ip-v4=ENABLE_IP_V4] [--labels=[KEY=VALUE,...]] - [--private-network=PRIVATE_NETWORK] [--provider=PROVIDER] - [--require-ssl=REQUIRE_SSL] + [--no-auto-storage-increase] [--data-disk-size=DATA_DISK_SIZE] + [--data-disk-type=DATA_DISK_TYPE] [--database-flags=[KEY=VALUE,...]] + [--display-name=DISPLAY_NAME] [--no-enable-ip-v4] + [--labels=[KEY=VALUE,...]] [--private-network=PRIVATE_NETWORK] + [--provider=PROVIDER] [--require-ssl] [--storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT] [--user-labels=[KEY=VALUE,...]] [--zone=ZONE] [GCLOUD_WIDE_FLAG ...] @@ -106,13 +105,14 @@ OPTIONAL FLAGS https://en.wikipedia.org/wiki/CIDR_notation#CIDR_notation, also known as 'slash' notation (e.g.192.168.100.0/24). - --auto-storage-increase=AUTO_STORAGE_INCREASE + --auto-storage-increase If you enable this setting, Cloud SQL checks your available storage every 30 seconds. If the available storage falls below a threshold size, Cloud SQL automatically adds additional storage capacity. If the available storage repeatedly falls below the threshold size, Cloud SQL continues to add storage until it reaches the maximum of 30 TB. - Default: ON. + Default: ON. Enabled by default, use --no-auto-storage-increase to + disable. --data-disk-size=DATA_DISK_SIZE Storage capacity available to the database, in GB. The minimum (and @@ -130,8 +130,9 @@ OPTIONAL FLAGS --display-name=DISPLAY_NAME Friendly name for the connection profile. - --enable-ip-v4=ENABLE_IP_V4 - Whether the instance should be assigned an IPv4 address or not. + --enable-ip-v4 + Whether the instance should be assigned an IPv4 address or not. Enabled + by default, use --no-enable-ip-v4 to disable. --labels=[KEY=VALUE,...] List of label KEY=VALUE pairs to add. @@ -151,7 +152,7 @@ OPTIONAL FLAGS Database provider (CLOUDSQL or RDS). PROVIDER must be one of: RDS, CLOUDSQL. - --require-ssl=REQUIRE_SSL + --require-ssl Whether SSL connections over IP should be enforced or not. --storage-auto-resize-limit=STORAGE_AUTO_RESIZE_LIMIT diff --git a/gcloud/firebase/test/ios/run b/gcloud/firebase/test/ios/run index 4b12d29e7..feaea83af 100644 --- a/gcloud/firebase/test/ios/run +++ b/gcloud/firebase/test/ios/run @@ -6,7 +6,7 @@ SYNOPSIS gcloud firebase test ios run [ARGSPEC] [--device=DIMENSION=VALUE,[...]] [--test=XCTEST_ZIP] [--timeout=TIMEOUT] [--type=TYPE] [--xcode-version=XCODE_VERSION] [--xctestrun-file=XCTESTRUN_FILE] - [--async] [--num-flaky-test-attempts=int] [--record-video] + [--app=APP] [--async] [--num-flaky-test-attempts=int] [--record-video] [--results-bucket=RESULTS_BUCKET] [--results-dir=RESULTS_DIR] [--results-history-name=RESULTS_HISTORY_NAME] [--test-special-entitlements] [--filter=EXPRESSION] [--limit=LIMIT] @@ -126,6 +126,12 @@ COMMONLY USED FLAGS URL beginning with gs://. FLAGS + --app=APP + The path to the application archive (.ipa file) for game-loop testing. + The path may be in the local filesystem or in Google Cloud Storage + using gs:// notation. This flag is only valid when --type=game-loop is + also set. + --async Invoke a test asynchronously without waiting for test results. diff --git a/gcloud/privateca/roots/delete b/gcloud/privateca/roots/delete index 0570abc4a..ebe251b93 100644 --- a/gcloud/privateca/roots/delete +++ b/gcloud/privateca/roots/delete @@ -4,13 +4,17 @@ NAME SYNOPSIS gcloud privateca roots delete (CERTIFICATE_AUTHORITY : --location=LOCATION --pool=POOL) - [--ignore-active-certificates] [GCLOUD_WIDE_FLAG ...] + [--ignore-active-certificates] [--skip-grace-period] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a Root Certificate Authority. Deleted Root Certificate Authorities may be recovered with the gcloud privateca roots undelete command within a grace period of 30 days. + Use the --skip-grace-period flag to delete as soon as possible without the + 30-day grace period to undelete. + Note that any user-managed KMS keys or Google Cloud Storage buckets will not be affected by this operation. You will need to delete the user- managed resources separately once the CA is deleted. Any Google-managed @@ -81,6 +85,11 @@ FLAGS the Certificate Authority has un-revoked or un-expired certificates after the grace period. + --skip-grace-period + If this flag is set, the Certificate Authority will be deleted as soon + as possible without a 30-day grace period where undeletion would have + been allowed. If you proceed, there will be no way to recover this CA. + 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/privateca/subordinates/delete b/gcloud/privateca/subordinates/delete index b12849139..378d84e20 100644 --- a/gcloud/privateca/subordinates/delete +++ b/gcloud/privateca/subordinates/delete @@ -5,13 +5,17 @@ NAME SYNOPSIS gcloud privateca subordinates delete (CERTIFICATE_AUTHORITY : --location=LOCATION --pool=POOL) - [--ignore-active-certificates] [GCLOUD_WIDE_FLAG ...] + [--ignore-active-certificates] [--skip-grace-period] + [GCLOUD_WIDE_FLAG ...] DESCRIPTION Delete a Subordinate Certificate Authority. Deleted Subordinate Certificate Authorities may be recovered with the gcloud privateca subordinates undelete command within a grace period of 30 days. + Use the --skip-grace-period flag to delete as soon as possible without the + 30-day grace period to undelete. + Note that any user-managed KMS keys or Google Cloud Storage buckets will not be affected by this operation. You will need to delete the user- managed resources separately once the CA is deleted. Any Google-managed @@ -82,6 +86,11 @@ FLAGS the Certificate Authority has un-revoked or un-expired certificates after the grace period. + --skip-grace-period + If this flag is set, the Certificate Authority will be deleted as soon + as possible without a 30-day grace period where undeletion would have + been allowed. If you proceed, there will be no way to recover this CA. + 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/run/deploy b/gcloud/run/deploy index 67fb57564..72f87ce11 100644 --- a/gcloud/run/deploy +++ b/gcloud/run/deploy @@ -10,7 +10,8 @@ SYNOPSIS [--platform=PLATFORM; default="managed"] [--port=PORT] [--service-account=SERVICE_ACCOUNT] [--tag=TAG] [--timeout=TIMEOUT] [--no-traffic] [--[no-]use-http2] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -42,16 +43,18 @@ DESCRIPTION EXAMPLES To deploy a container to the service my-backend on Cloud Run: - $ gcloud run deploy my-backend --image=gcr.io/my/image + $ gcloud run deploy my-backend \ + --image=us-docker.pkg.dev/project/image You may also omit the service name. Then a prompt will be displayed with a suggested default value: - $ gcloud run deploy --image=gcr.io/my/image + $ gcloud run deploy --image=us-docker.pkg.dev/project/image To deploy to Cloud Run on Kubernetes Engine, you need to specify a cluster: - $ gcloud run deploy --image=gcr.io/my/image --cluster=my-cluster + $ gcloud run deploy --image=us-docker.pkg.dev/project/image \ + --cluster=my-cluster POSITIONAL ARGUMENTS Service resource - Service to deploy to. The arguments in this group can @@ -204,6 +207,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/run/services/update b/gcloud/run/services/update index 2608ae3b1..3cfacdaa6 100644 --- a/gcloud/run/services/update +++ b/gcloud/run/services/update @@ -22,7 +22,8 @@ SYNOPSIS | --clear-binary-authorization --clear-key | --key=KEY --clear-post-key-revocation-action-type | --post-key-revocation-action-type=POST_KEY_REVOCATION_ACTION_TYPE] - [--clear-env-vars | --set-env-vars=[KEY=VALUE,...] + [--clear-env-vars | --env-vars-file=FILE_PATH + | --set-env-vars=[KEY=VALUE,...] | --remove-env-vars=[KEY,...] --update-env-vars=[KEY=VALUE,...]] [--clear-labels | --remove-labels=[KEY,...] --labels=[KEY=VALUE,...] | --update-labels=[KEY=VALUE,...]] @@ -292,6 +293,11 @@ FLAGS --clear-env-vars Remove all environment variables. + --env-vars-file=FILE_PATH + Path to a local YAML file with definitions for all environment + variables. All existing environment variables will be removed before + the new environment variables are added. + --set-env-vars=[KEY=VALUE,...] List of key-value pairs to set as environment variables. All existing environment variables will be removed first. diff --git a/gcloud/scc/bqexports/help b/gcloud/scc/bqexports/help index 1a4630c08..810d2b640 100644 --- a/gcloud/scc/bqexports/help +++ b/gcloud/scc/bqexports/help @@ -27,3 +27,6 @@ COMMANDS list List Cloud Security Command Center BigQuery exports. + + update + Update a Cloud Security Command Center BigQuery export. diff --git a/gcloud/scc/bqexports/update b/gcloud/scc/bqexports/update new file mode 100644 index 000000000..ae946f1e8 --- /dev/null +++ b/gcloud/scc/bqexports/update @@ -0,0 +1,116 @@ +NAME + gcloud scc bqexports update - update a Cloud Security Command Center + BigQuery export + +SYNOPSIS + gcloud scc bqexports update BIG_QUERY_EXPORT [--dataset=DATASET] + [--description=DESCRIPTION] [--filter=FILTER] + [--update-mask=UPDATE_MASK] + [--folder=FOLDER | --organization=ORGANIZATION | --project=PROJECT] + [GCLOUD_WIDE_FLAG ...] + +DESCRIPTION + Update a Cloud Security Command Center BigQuery export. + +EXAMPLES + Update a BigQuery export with id test-bq-export under organization 123 with + a dataset abc in project 234 and a filter on category that equals to + XSS_SCRIPTING: + + $ gcloud scc bqexports update test-bq-export \ + --organization=organizations/123 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports update test-bq-export --organization=123 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports update \ + organizations/123/bigQueryExports/test-bq-export \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + + Update a BigQuery export with id test-bq-export under folder 456 with a + dataset abc in project 234 and a filter on category that equals to + XSS_SCRIPTING: + + $ gcloud scc bqexports update test-bq-export --folder=folders/456 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports update test-bq-export --folder=456 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports update \ + folders/456/bigQueryExports/test-bq-export \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + + Update a BigQuery export with id test-bq-export under project 789 with a + dataset abc in project 234 and a filter on category that equals to + XSS_SCRIPTING: + + $ gcloud scc bqexports update test-bq-export \ + --project=projects/789 --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports update test-bq-export --project=789 \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + $ gcloud scc bqexports update \ + projects/789/bigQueryExports/test-bq-export \ + --dataset=projects/234/datasets/abc \ + --description="This is a test BigQuery export" \ + --filter="category=\"XSS_SCRIPTING\"" + +POSITIONAL ARGUMENTS + BIG_QUERY_EXPORT + ID of the BigQuery export or the full resource name of the BigQuery + export. + +FLAGS + --dataset=DATASET + The dataset to write findings updates to. + + --description=DESCRIPTION + The text that will be used to describe a BigQuery export. + + --filter=FILTER + The filter string which will applied to findings muted by a BigQuery + export. + + --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 BigQuery export resides. Formatted as folders/456 or + just 456. + + --organization=ORGANIZATION + Organization where the BigQuery export resides. Formatted as + organizations/123 or just 123. + + --project=PROJECT + Project (id or number) where the BigQuery export 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