1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-16 20:36:39 +00:00

gcloud: Wed Aug 23 10:30:46 UTC 2023

This commit is contained in:
Automated 2023-08-23 10:30:46 +00:00
parent 5f3d6bc974
commit f9edf67fe5
677 changed files with 22815 additions and 975 deletions

View file

@ -0,0 +1,92 @@
NAME
gcloud alpha container fleet scopes namespaces create - create a fleet
namespace
SYNOPSIS
gcloud alpha container fleet scopes namespaces create
(NAMESPACE : --scope=SCOPE) [--labels=[KEY=VALUE,...]]
[--namespace-labels=[KEY=VALUE,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command can fail for the following reasons:
▪ The project specified does not exist.
▪ The project has a fleet namespace with the same name.
▪ The caller does not have permission to access the given project.
EXAMPLES
To create a fleet namespace with name NAMESPACE in the active project, run:
$ gcloud alpha container fleet scopes namespaces create NAMESPACE
To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
name NAMESPACE, run:
$ gcloud alpha container fleet scopes namespaces create NAMESPACE \
--scope=SCOPE --project=PROJECT_ID
POSITIONAL ARGUMENTS
Namespace resource - The group of arguments defining the Fleet Namespace.
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 NAMESPACE on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
To set the location attribute:
◆ provide the argument NAMESPACE on the command line with a fully
specified name;
◆ global is the only supported location.
This must be specified.
NAMESPACE
ID of the namespace or fully qualified identifier for the namespace.
To set the namespace attribute:
▸ provide the argument NAMESPACE on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--scope=SCOPE
the
To set the scope attribute:
▸ provide the argument NAMESPACE on the command line with a fully
specified name;
▸ provide the argument --scope on the command line.
FLAGS
--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.
--namespace-labels=[KEY=VALUE,...]
List of namespace-level label KEY=VALUE pairs to add.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
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 scopes namespaces create
$ gcloud beta container fleet scopes namespaces create

View file

@ -0,0 +1,79 @@
NAME
gcloud alpha container fleet scopes namespaces delete - delete a fleet
namespace
SYNOPSIS
gcloud alpha container fleet scopes namespaces delete
(NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command can fail for the following reasons:
▪ The project specified does not exist.
▪ The namespace specified does not exist.
▪ The caller does not have permission to access the given project or
namespace.
EXAMPLES
To delete fleet namespace NAMESPACE in the active project:
$ gcloud alpha container fleet scopes namespaces delete NAMESPACE
To delete fleet namespace NAMESPACE in project PROJECT_ID:
$ gcloud alpha container fleet scopes namespaces delete NAMESPACE \
--project=PROJECT_ID
POSITIONAL ARGUMENTS
Namespace resource - The group of arguments defining the Fleet Namespace.
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 NAMESPACE on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
To set the location attribute:
◆ provide the argument NAMESPACE on the command line with a fully
specified name;
◆ global is the only supported location.
This must be specified.
NAMESPACE
ID of the namespace or fully qualified identifier for the namespace.
To set the namespace attribute:
▸ provide the argument NAMESPACE on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--scope=SCOPE
the
To set the scope attribute:
▸ provide the argument NAMESPACE on the command line with a fully
specified name;
▸ provide the argument --scope 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. These variants are also available:
$ gcloud container fleet scopes namespaces delete
$ gcloud beta container fleet scopes namespaces delete

View file

@ -0,0 +1,79 @@
NAME
gcloud alpha container fleet scopes namespaces describe - show fleet
namespace info
SYNOPSIS
gcloud alpha container fleet scopes namespaces describe
(NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command can fail for the following reasons:
▪ The project specified does not exist.
▪ The namespace specified does not exist in the project.
▪ The caller does not have permission to access the project or
namespace.
EXAMPLES
To print metadata for the namespace NAMESPACE in the active project, run:
$ gcloud alpha container fleet scopes namespaces describe NAMESPACE
To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
$ gcloud alpha container fleet scopes namespaces describe \
NAMESPACE --project=PROJECT_ID
POSITIONAL ARGUMENTS
Namespace resource - The group of arguments defining the Fleet Namespace.
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 NAMESPACE on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
To set the location attribute:
◆ provide the argument NAMESPACE on the command line with a fully
specified name;
◆ global is the only supported location.
This must be specified.
NAMESPACE
ID of the namespace or fully qualified identifier for the namespace.
To set the namespace attribute:
▸ provide the argument NAMESPACE on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--scope=SCOPE
the
To set the scope attribute:
▸ provide the argument NAMESPACE on the command line with a fully
specified name;
▸ provide the argument --scope 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. These variants are also available:
$ gcloud container fleet scopes namespaces describe
$ gcloud beta container fleet scopes namespaces describe

View file

@ -0,0 +1,62 @@
NAME
gcloud alpha container fleet scopes namespaces get-credentials - fetch
credentials for a membership with a particular namespace
SYNOPSIS
gcloud alpha container fleet scopes namespaces get-credentials NAMESPACE
[--membership=MEMBERSHIP] [--membership-location=MEMBERSHIP_LOCATION]
[--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG]
[GCLOUD_WIDE_FLAG ...]
EXAMPLES
Get the Connect Gateway kubeconfig for global membership MEMBERSHIP, using
namespace NAMESPACE in the config:
$ gcloud alpha container fleet scopes namespaces get-credentials \
NAMESPACE --membership=MEMBERSHIP --membership-location=global \
--set-namespace-in-config=true
Get the Connect Gateway kubeconfig for global membership MEMBERSHIP:
$ gcloud alpha container fleet scopes namespaces get-credentials \
NAMESPACE --membership=MEMBERSHIP --membership-location=global
POSITIONAL ARGUMENTS
NAMESPACE
Name of the namespace for which to get access to memberships.
FLAGS
--membership=MEMBERSHIP
Membership ID to get credentials from. If not provided, a prompt will
offer a list of memberships in the fleet.
--membership-location=MEMBERSHIP_LOCATION
The location of the membership resource, e.g. us-central1. If not
specified, defaults to global.
--set-namespace-in-config=SET_NAMESPACE_IN_CONFIG
If true, the default namespace for the context in the generated
kubeconfig will be set to the Fleet namespace (i.e. the name given as
the positional argument in this command).
Otherwise, no default namespace will be set, functioning the same as
gcloud container fleet memberships get-credentials.
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 scopes namespaces get-credentials
$ gcloud beta container fleet scopes namespaces get-credentials

View file

@ -0,0 +1,57 @@
NAME
gcloud alpha container fleet scopes namespaces - fleet namespaces are the
fleet equivalent of k8s cluster namespaces
SYNOPSIS
gcloud alpha container fleet scopes namespaces COMMAND
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command group allows for manipulation of fleet namespaces.
EXAMPLES
Manage fleet namespaces:
$ gcloud alpha container fleet scopes namespaces --help
Manage RBAC RoleBindings in a fleet namespace:
$ gcloud alpha container fleet scopes namespaces rbacrolebindings \
--help
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 fleet namespace.
delete
(ALPHA) Delete a fleet namespace.
describe
(ALPHA) Show fleet namespace info.
get-credentials
(ALPHA) Fetch credentials for a membership with a particular namespace.
list
(ALPHA) List fleet namespaces in a project.
update
(ALPHA) Update a fleet namespace.
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 scopes namespaces
$ gcloud beta container fleet scopes namespaces

View file

@ -0,0 +1,98 @@
NAME
gcloud alpha container fleet scopes namespaces list - list fleet namespaces
in a project
SYNOPSIS
gcloud alpha container fleet scopes namespaces list --scope=SCOPE
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command can fail for the following reasons:
▪ The project specified does not exist.
▪ The user does not have access to the project specified.
EXAMPLES
The following command lists namespaces in the active project:
$ gcloud alpha container fleet scopes namespaces list
The following command lists namespaces in project PROJECT_ID:
$ gcloud alpha container fleet scopes namespaces list \
--project=PROJECT_ID
REQUIRED FLAGS
Scope resource - The group of arguments defining the Fleet Scope. This
represents a Cloud resource. (NOTE) Some attributes are not given
arguments in this group but can be set in other ways.
To set the project attribute:
◆ provide the argument --scope on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
To set the location attribute:
◆ provide the argument --scope on the command line with a fully
specified name;
◆ global is the only supported location.
This must be specified.
--scope=SCOPE
ID of the scope or fully qualified identifier for the scope.
To set the scope attribute:
▸ provide the argument --scope on the command line.
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. These variants are also available:
$ gcloud container fleet scopes namespaces list
$ gcloud beta container fleet scopes namespaces list

View file

@ -0,0 +1,144 @@
NAME
gcloud alpha container fleet scopes namespaces update - update a fleet
namespace
SYNOPSIS
gcloud alpha container fleet scopes namespaces update
(NAMESPACE : --scope=SCOPE) [--update-labels=[KEY=VALUE,...]]
[--update-namespace-labels=[KEY=VALUE,...]]
[--clear-labels | --remove-labels=[KEY,...]]
[--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
(ALPHA) This command can fail for the following reasons:
▪ The project specified does not exist.
▪ The fleet namespace does not exist in the project.
▪ The caller does not have permission to access the project or
namespace.
EXAMPLES
To update the namespace NAMESPACE in the active project:
$ gcloud alpha container fleet scopes namespaces update NAMESPACE
To update the namespace NAMESPACE in project PROJECT_ID:
$ gcloud alpha container fleet scopes namespaces update NAMESPACE \
--project=PROJECT_ID
POSITIONAL ARGUMENTS
Namespace resource - The group of arguments defining the Fleet Namespace.
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 NAMESPACE on the command line with a fully
specified name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
To set the location attribute:
◆ provide the argument NAMESPACE on the command line with a fully
specified name;
◆ global is the only supported location.
This must be specified.
NAMESPACE
ID of the namespace or fully qualified identifier for the namespace.
To set the namespace attribute:
▸ provide the argument NAMESPACE on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--scope=SCOPE
the
To set the scope attribute:
▸ provide the argument NAMESPACE on the command line with a fully
specified name;
▸ provide the argument --scope on the command line.
FLAGS
--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.
--update-namespace-labels=[KEY=VALUE,...]
List of namespace-level label KEY=VALUE pairs to update in the cluster
namespace. If a label exists, its value is modified. Otherwise, a new
label is' created.
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 scopes namespaces update \
--clear-labels
To remove all existing labels and create two new labels, foo and baz:
$ gcloud alpha container fleet scopes namespaces 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.
At most one of these can be specified:
--clear-namespace-labels
Remove all namespace-level labels from the cluster namespace. If
--update-namespace-labels is also specified then
--clear-namespace-labels is applied first.
For example, to remove all labels:
$ gcloud alpha container fleet scopes namespaces update \
namespace_name --clear-namespace-labels
To remove all existing namespace-level labels and create two new
labels, foo and baz:
$ gcloud alpha container fleet scopes namespaces update \
namespace_name --clear-namespace-labels \
--update-namespace-labels foo=bar,baz=qux
--remove-namespace-labels=[KEY,...]
List of namespace-level label keys to remove in the cluster
namespace. If a label does not exist it is silently ignored. If
--update-namespace-labels is also specified then
--update-namespace-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. These variants are also available:
$ gcloud container fleet scopes namespaces update
$ gcloud beta container fleet scopes namespaces update