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

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

88
gcloud/container/fleet/scopes/add-iam-policy-binding Normal file
View file

@ -0,0 +1,88 @@
NAME
gcloud container fleet scopes add-iam-policy-binding - add IAM policy
binding to a Fleet Scope
SYNOPSIS
gcloud container fleet scopes add-iam-policy-binding SCOPE
--member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Add an IAM policy binding to the IAM policy of a Fleet Scope. One binding
consists of a member, and a role.
EXAMPLES
To add an IAM policy binding for the role of 'roles/gkehub.scopeUser' for
the user 'test-user@gmail.com' with scope 'my-scope', run:
$ gcloud container fleet scopes add-iam-policy-binding my-scope \
--member='user:test-user@gmail.com' \
--role='roles/gkehub.scopeUser'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
POSITIONAL ARGUMENTS
Scope resource - The scope for which to add IAM policy binding to. 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;
◆ set the property core/project;
◆ provide the argument --project on the command line.
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
ID of the scope or fully qualified identifier for the scope.
To set the scope attribute:
▸ provide the argument scope on the command line.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to add the binding for. Should be of the form
user|group|serviceAccount:email or domain:domain.
Examples: user:test-user@gmail.com, group:admins@example.com,
serviceAccount:test123@example.domain.com, or
domain:example.domain.com.
Some resources also accept the following special values:
◆ allUsers - Special identifier that represents anyone who is on the
internet, with or without a Google account.
◆ allAuthenticatedUsers - Special identifier that represents anyone
who is authenticated with a Google account or a service account.
--role=ROLE
Role name to assign to the principal. The role name is the complete
path of a predefined role, such as roles/logging.viewer, or the role ID
for a custom role, such as
organizations/{ORGANIZATION_ID}/roles/logging.viewer.
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 scopes add-iam-policy-binding
$ gcloud beta container fleet scopes add-iam-policy-binding

76
gcloud/container/fleet/scopes/create Normal file
View file

@ -0,0 +1,76 @@
NAME
gcloud container fleet scopes create - create a new fleet scope
SYNOPSIS
gcloud container fleet scopes create SCOPE [--async]
[--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Create a Fleet Scope resource.
EXAMPLES
Create a new scope SCOPE_NAME in the active project's fleet:
$ gcloud container fleet scopes create SCOPE_NAME
POSITIONAL ARGUMENTS
Scope resource - The fleet scope resourse to be created. 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;
◆ set the property core/project;
◆ provide the argument --project on the command line.
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
ID of the scope or fully qualified identifier for the scope.
To set the scope attribute:
▸ provide the argument scope on the command line.
FLAGS
--async
Return immediately, without waiting for the operation in progress to
complete.
--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 scope-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.
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 scopes create
$ gcloud beta container fleet scopes create

78
gcloud/container/fleet/scopes/delete Normal file
View file

@ -0,0 +1,78 @@
NAME
gcloud container fleet scopes delete - delete a fleet scope
SYNOPSIS
gcloud container fleet scopes delete (SCOPE : --location=LOCATION)
[--async] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command deletes a Fleet Scope resource .
EXAMPLES
First retrieve the ID of the scope using the command below. The output of
this command lists all the fleet's scopes, with their unique IDs in the
Names column:
$ gcloud container fleet scopes list
Delete a scope from the active project's fleet:
$ gcloud container fleet scopes delete SCOPE_NAME
POSITIONAL ARGUMENTS
Scope resource - The fleet scope 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 scope 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.
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.
This positional argument 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 scope 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 scopes delete
$ gcloud beta container fleet scopes delete

72
gcloud/container/fleet/scopes/describe Normal file
View file

@ -0,0 +1,72 @@
NAME
gcloud container fleet scopes describe - describe a fleet scope
SYNOPSIS
gcloud container fleet scopes describe (SCOPE : --location=LOCATION)
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe a Fleet Scope.
EXAMPLES
First retrieve the ID of the scope using the command below. The output of
this command lists all the fleet's members, with their unique IDs in the
Names column:
$ gcloud container fleet scopes list
Then describe it:
$ gcloud container fleet scopes describe SCOPE_NAME
POSITIONAL ARGUMENTS
Scope resource - The scope 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 scope 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.
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.
This positional argument 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 scope 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 scopes describe
$ gcloud beta container fleet scopes describe

87
gcloud/container/fleet/scopes/get-iam-policy Normal file
View file

@ -0,0 +1,87 @@
NAME
gcloud container fleet scopes get-iam-policy - get the IAM policy for a
Fleet Scope
SYNOPSIS
gcloud container fleet scopes get-iam-policy SCOPE [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command gets the IAM policy for a scope.
EXAMPLES
To print the IAM policy for a given scope, run:
$ gcloud container fleet scopes get-iam-policy my-scope
POSITIONAL ARGUMENTS
Scope resource - The scope for which to display the IAM 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 scope on the command line with a fully specified
name;
◆ set the property core/project;
◆ provide the argument --project on the command line.
To set the location attribute:
◆ provide the argument scope on the command line with a fully specified
name;
◆ global is the only supported location.
This must be specified.
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.
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 scopes get-iam-policy
$ gcloud beta container fleet scopes get-iam-policy

57
gcloud/container/fleet/scopes/help Normal file
View file

@ -0,0 +1,57 @@
NAME
gcloud container fleet scopes - manage scopes of all your GKE fleets
SYNOPSIS
gcloud container fleet scopes GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Manage scopes of all your GKE fleets.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
namespaces
Fleet namespaces are the fleet equivalent of k8s cluster namespaces.
rbacrolebindings
Fleet scope RBAC RoleBindings for permissions.
COMMANDS
COMMAND is one of the following:
add-iam-policy-binding
Add IAM policy binding to a Fleet Scope.
create
Create a new fleet scope.
delete
Delete a fleet scope.
describe
Describe a fleet scope.
get-iam-policy
Get the IAM policy for a Fleet Scope.
list
List fleet scopes.
remove-iam-policy-binding
Remove IAM policy binding of a Fleet Scope.
update
Update a scope.
NOTES
These variants are also available:
$ gcloud alpha container fleet scopes
$ gcloud beta container fleet scopes

68
gcloud/container/fleet/scopes/list Normal file
View file

@ -0,0 +1,68 @@
NAME
gcloud container fleet scopes list - list fleet scopes
SYNOPSIS
gcloud container fleet scopes list [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [--uri]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List scopes in a fleet.
EXAMPLES
List scopes in the active project's fleet:
$ gcloud container fleet scopes 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 scopes list
$ gcloud beta container fleet scopes list

88
gcloud/container/fleet/scopes/namespaces/create Normal file
View file

@ -0,0 +1,88 @@
NAME
gcloud container fleet scopes namespaces create - create a fleet namespace
SYNOPSIS
gcloud container fleet scopes namespaces create (NAMESPACE : --scope=SCOPE)
[--labels=[KEY=VALUE,...]] [--namespace-labels=[KEY=VALUE,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
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 container fleet scopes namespaces create NAMESPACE
To create a fleet namespace in fleet scope SCOPE in project PROJECT_ID with
name NAMESPACE, run:
$ gcloud 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
These variants are also available:
$ gcloud alpha container fleet scopes namespaces create
$ gcloud beta container fleet scopes namespaces create

75
gcloud/container/fleet/scopes/namespaces/delete Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud container fleet scopes namespaces delete - delete a fleet namespace
SYNOPSIS
gcloud container fleet scopes namespaces delete (NAMESPACE : --scope=SCOPE)
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
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 container fleet scopes namespaces delete NAMESPACE
To delete fleet namespace NAMESPACE in project PROJECT_ID:
$ gcloud 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
These variants are also available:
$ gcloud alpha container fleet scopes namespaces delete
$ gcloud beta container fleet scopes namespaces delete

76
gcloud/container/fleet/scopes/namespaces/describe Normal file
View file

@ -0,0 +1,76 @@
NAME
gcloud container fleet scopes namespaces describe - show fleet namespace
info
SYNOPSIS
gcloud container fleet scopes namespaces describe
(NAMESPACE : --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
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 container fleet scopes namespaces describe NAMESPACE
To print metadata for the namespace NAMESPACE in project PROJECT_ID, run:
$ gcloud 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
These variants are also available:
$ gcloud alpha container fleet scopes namespaces describe
$ gcloud beta container fleet scopes namespaces describe

59
gcloud/container/fleet/scopes/namespaces/get-credentials Normal file
View file

@ -0,0 +1,59 @@
NAME
gcloud container fleet scopes namespaces get-credentials - fetch
credentials for a membership with a particular namespace
SYNOPSIS
gcloud 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 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 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
These variants are also available:
$ gcloud alpha container fleet scopes namespaces get-credentials
$ gcloud beta container fleet scopes namespaces get-credentials

52
gcloud/container/fleet/scopes/namespaces/help Normal file
View file

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

94
gcloud/container/fleet/scopes/namespaces/list Normal file
View file

@ -0,0 +1,94 @@
NAME
gcloud container fleet scopes namespaces list - list fleet namespaces in a
project
SYNOPSIS
gcloud container fleet scopes namespaces list --scope=SCOPE
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
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 container fleet scopes namespaces list
The following command lists namespaces in project PROJECT_ID:
$ gcloud 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
These variants are also available:
$ gcloud alpha container fleet scopes namespaces list
$ gcloud beta container fleet scopes namespaces list

139
gcloud/container/fleet/scopes/namespaces/update Normal file
View file

@ -0,0 +1,139 @@
NAME
gcloud container fleet scopes namespaces update - update a fleet namespace
SYNOPSIS
gcloud 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
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 container fleet scopes namespaces update NAMESPACE
To update the namespace NAMESPACE in project PROJECT_ID:
$ gcloud 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 container fleet scopes namespaces update --clear-labels
To remove all existing labels and create two new labels, foo and baz:
$ gcloud 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 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 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
These variants are also available:
$ gcloud alpha container fleet scopes namespaces update
$ gcloud beta container fleet scopes namespaces update

105
gcloud/container/fleet/scopes/rbacrolebindings/create Normal file
View file

@ -0,0 +1,105 @@
NAME
gcloud container fleet scopes rbacrolebindings create - create an RBAC
RoleBinding
SYNOPSIS
gcloud container fleet scopes rbacrolebindings create
(NAME : --location=LOCATION --scope=SCOPE) --role=ROLE
(--group=GROUP | --user=USER) [--labels=[KEY=VALUE,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command can fail for the following reasons:
▪ The RBAC RoleBinding already exists.
▪ The caller does not have permission to access the given scope.
EXAMPLES
To create an admin RBAC RoleBinding RBRB in scope SCOPE for user
person@google.com, run:
$ gcloud container fleet scopes rbacrolebindings create RBRB \
--scope=SCOPE --role=admin --user=person@google.com
To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group
people@google.com, run:
$ gcloud container fleet scopes rbacrolebindings create RBRB \
--scope=SCOPE --role=viewer --group=people@google.com
POSITIONAL ARGUMENTS
Rbacrolebinding resource - The group of arguments defining an
RBACRoleBinding. 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 NAME on the command line with a fully specified
name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
NAME
ID of the rbacrolebinding or fully qualified identifier for the
rbacrolebinding.
To set the rbacrolebinding attribute:
▸ provide the argument NAME on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location for the rbacrolebinding.
To set the location attribute:
▸ provide the argument NAME on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property gkehub/location.
--scope=SCOPE
Name of the rbacrolebinding.
To set the scope attribute:
▸ provide the argument NAME on the command line with a fully
specified name;
▸ provide the argument --scope on the command line.
REQUIRED FLAGS
--role=ROLE
Role to assign. ROLE must be one of: admin, edit, view.
Exactly one of these must be specified:
--group=GROUP
Group for the RoleBinding.
--user=USER
User for the RoleBinding.
OPTIONAL 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.
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 scopes rbacrolebindings create
$ gcloud beta container fleet scopes rbacrolebindings create

75
gcloud/container/fleet/scopes/rbacrolebindings/delete Normal file
View file

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

75
gcloud/container/fleet/scopes/rbacrolebindings/describe Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud container fleet scopes rbacrolebindings describe - show fleet scope
RBAC RoleBinding information
SYNOPSIS
gcloud container fleet scopes rbacrolebindings describe
(NAME : --location=LOCATION --scope=SCOPE) [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command can fail for the following reasons:
▪ The RoleBinding specified does not exist in the project.
▪ The caller does not have permission to access the RoleBinding.
EXAMPLES
To print metadata for RBAC RoleBinding RBRB in the scope SCOPE, run:
$ gcloud container fleet scopes rbacrolebindings describe RBRB \
--scope=SCOPE
POSITIONAL ARGUMENTS
Rbacrolebinding resource - The group of arguments defining an
RBACRoleBinding. 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 NAME on the command line with a fully specified
name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
NAME
ID of the rbacrolebinding or fully qualified identifier for the
rbacrolebinding.
To set the rbacrolebinding attribute:
▸ provide the argument NAME on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location for the rbacrolebinding.
To set the location attribute:
▸ provide the argument NAME on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property gkehub/location.
--scope=SCOPE
Name of the rbacrolebinding.
To set the scope attribute:
▸ provide the argument NAME 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
These variants are also available:
$ gcloud alpha container fleet scopes rbacrolebindings describe
$ gcloud beta container fleet scopes rbacrolebindings describe

47
gcloud/container/fleet/scopes/rbacrolebindings/help Normal file
View file

@ -0,0 +1,47 @@
NAME
gcloud container fleet scopes rbacrolebindings - fleet scope RBAC
RoleBindings for permissions
SYNOPSIS
gcloud container fleet scopes rbacrolebindings COMMAND
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command group allows for manipulation of fleet namespace RBAC
RoleBindings.
EXAMPLES
Manage RBAC RoleBindings:
$ gcloud container fleet scopes 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
Create an RBAC RoleBinding.
delete
Delete a fleet scope RBAC RoleBinding.
describe
Show fleet scope RBAC RoleBinding information.
list
List RBAC RoleBindings in a fleet scope.
update
Update a fleet scope RBAC RoleBinding.
NOTES
These variants are also available:
$ gcloud alpha container fleet scopes rbacrolebindings
$ gcloud beta container fleet scopes rbacrolebindings

72
gcloud/container/fleet/scopes/rbacrolebindings/list Normal file
View file

@ -0,0 +1,72 @@
NAME
gcloud container fleet scopes rbacrolebindings list - list RBAC
RoleBindings in a fleet scope
SYNOPSIS
gcloud container fleet scopes rbacrolebindings list --scope=SCOPE
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [--uri] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command can fail for the following reasons:
▪ The scope specified does not exist.
▪ The user does not have access to the specified scope.
EXAMPLES
The following command lists RBAC RoleBindings in scope SCOPE in project
PROJECT_ID:
$ gcloud container fleet scopes rbacrolebindings list \
--scope=SCOPE --project=PROJECT_ID
REQUIRED FLAGS
--scope=SCOPE
Name of the fleet scope to list RBAC RoleBindings from.
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
These variants are also available:
$ gcloud alpha container fleet scopes rbacrolebindings list
$ gcloud beta container fleet scopes rbacrolebindings list

128
gcloud/container/fleet/scopes/rbacrolebindings/update Normal file
View file

@ -0,0 +1,128 @@
NAME
gcloud container fleet scopes rbacrolebindings update - update a fleet
scope RBAC RoleBinding
SYNOPSIS
gcloud container fleet scopes rbacrolebindings update
(NAME : --location=LOCATION --scope=SCOPE) [--role=ROLE]
[--update-labels=[KEY=VALUE,...]]
[--clear-labels | --remove-labels=[KEY,...]]
[--group=GROUP | --user=USER] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
This command can fail for the following reasons:
▪ The RoleBinding does not exist in the project.
▪ The caller does not have permission to access the RoleBinding.
EXAMPLES
To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
the viewer role:
$ gcloud container fleet scopes rbacrolebindings update RBRB \
--scope=SCOPE --role=viewer
To update the RBAC RoleBinding RBRB in scope SCOPE in the active project to
the user someone@google.com:
$ gcloud container fleet scopes rbacrolebindings update RBRB \
--scope=SCOPE --user=someone@google.com
POSITIONAL ARGUMENTS
Rbacrolebinding resource - The group of arguments defining an
RBACRoleBinding. 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 NAME on the command line with a fully specified
name;
◆ provide the argument --project on the command line;
◆ set the property core/project.
This must be specified.
NAME
ID of the rbacrolebinding or fully qualified identifier for the
rbacrolebinding.
To set the rbacrolebinding attribute:
▸ provide the argument NAME on the command line.
This positional argument must be specified if any of the other
arguments in this group are specified.
--location=LOCATION
Location for the rbacrolebinding.
To set the location attribute:
▸ provide the argument NAME on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ set the property gkehub/location.
--scope=SCOPE
Name of the rbacrolebinding.
To set the scope attribute:
▸ provide the argument NAME on the command line with a fully
specified name;
▸ provide the argument --scope on the command line.
FLAGS
--role=ROLE
Role for the RBACRoleBinding to update to. ROLE must be one of: admin,
edit, view.
--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 scopes rbacrolebindings update \
--clear-labels
To remove all existing labels and create two new labels, foo and baz:
$ gcloud container fleet scopes rbacrolebindings 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:
--group=GROUP
Group for the RBACRoleBinding to update to.
--user=USER
User for the RBACRoleBinding to update to.
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 scopes rbacrolebindings update
$ gcloud beta container fleet scopes rbacrolebindings update

89
gcloud/container/fleet/scopes/remove-iam-policy-binding Normal file
View file

@ -0,0 +1,89 @@
NAME
gcloud container fleet scopes remove-iam-policy-binding - remove IAM policy
binding of a Fleet Scope
SYNOPSIS
gcloud container fleet scopes remove-iam-policy-binding SCOPE
--member=PRINCIPAL --role=ROLE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Remove an IAM policy binding from the IAM policy of a scope. One binding
consists of a member, and a role.
EXAMPLES
To remove an IAM policy binding for the role of 'roles/gkehub.scopeUser'
for the user 'test-user@gmail.com' with scope 'my-scope', run:
$ gcloud container fleet scopes remove-iam-policy-binding my-scope \
--member='user:test-user@gmail.com' \
--role='roles/gkehub.scopeUser'
See https://cloud.google.com/iam/docs/managing-policies for details of
policy role and member types.
POSITIONAL ARGUMENTS
Scope resource - The scope for which to remove IAM policy binding from.
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;
◆ set the property core/project;
◆ provide the argument --project on the command line.
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
ID of the scope or fully qualified identifier for the scope.
To set the scope attribute:
▸ provide the argument scope on the command line.
REQUIRED FLAGS
--member=PRINCIPAL
The principal to remove the binding for. Should be of the form
user|group|serviceAccount:email or domain:domain.
Examples: user:test-user@gmail.com, group:admins@example.com,
serviceAccount:test123@example.domain.com, or
domain:example.domain.com.
Deleted principals have an additional deleted: prefix and a ?uid=UID
suffix, where UID is a unique identifier for the principal. Example:
deleted:user:test-user@gmail.com?uid=123456789012345678901.
Some resources also accept the following special values:
◆ allUsers - Special identifier that represents anyone who is on the
internet, with or without a Google account.
◆ allAuthenticatedUsers - Special identifier that represents anyone
who is authenticated with a Google account or a service account.
--role=ROLE
The role to remove the principal from.
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 scopes remove-iam-policy-binding
$ gcloud beta container fleet scopes remove-iam-policy-binding

227
gcloud/container/fleet/scopes/update Normal file
View file

@ -0,0 +1,227 @@
NAME
gcloud container fleet scopes update - update a scope
SYNOPSIS
gcloud container fleet scopes update (SCOPE : --location=LOCATION)
[--update-labels=[KEY=VALUE,...]]
[--update-namespace-labels=[KEY=VALUE,...]]
[--clear-labels | --remove-labels=[KEY,...]]
[--clear-namespace-labels | --remove-namespace-labels=[KEY,...]]
[--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
--remove-upgrade-soaking-overrides
| --add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
--upgrade-selector=[name=NAME],[version=VERSION]
--reset-upstream-scope | --upstream-scope=UPSTREAM_SCOPE]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Update an existing Fleet Scope.
EXAMPLES
First retrieve the ID of the scope using the command below.
$ gcloud container fleet scopes list
Update a scope.
$ gcloud container fleet scopes update SCOPE_NAME
POSITIONAL ARGUMENTS
Scope resource - fleet scope resource. 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 scope 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.
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.
This positional argument 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 scope on the command line with a fully
specified name;
▸ provide the argument --location on the command line;
▸ global is the only supported location.
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 scope-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 container fleet scopes update --clear-labels
To remove all existing labels and create two new labels, foo and baz:
$ gcloud container fleet scopes 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 scope-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 container fleet scopes update scope_name \
--clear-namespace-labels
To remove all existing scope-level labels and create two new labels,
foo and baz:
$ gcloud container fleet scopes update scope_name \
--clear-namespace-labels \
--update-namespace-labels foo=bar,baz=qux
--remove-namespace-labels=[KEY,...]
List of scope-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.
Rollout Sequencing
--default-upgrade-soaking=DEFAULT_UPGRADE_SOAKING
Configures the default soaking duration for each upgrade propagating
through the current scope to become "COMPLETE". Soaking begins after
all clusters in the scope are on the target version, or after 30 days
if all cluster upgrades are not complete. Once an upgrade state
becomes "COMPLETE", it will automatically be propagated to the
downstream scope. Max is 30 days.
See $ gcloud topic datetimes for information on duration formats.
To configure Rollout Sequencing for a given scope, SCOPE_NAME, this
attribute must be set. To do this while specifying a default soaking
duration of 7 days, run:
$ gcloud container fleet scopes update SCOPE_NAME \
default-upgrade-soaking=7d
At most one of these can be specified:
--remove-upgrade-soaking-overrides
Removes soaking time overrides for all upgrades propagating through
the current scope. Consequently, all upgrades will follow the soak
time configured by --default-upgrade-soaking until new overrides
are configured with --add_upgrade_soaking_override and
--upgrade_selector.
To remove all soaking time overrides configured for SCOPE_NAME,
run:
$ gcloud container fleet scopes update SCOPE_NAME \
--remove-upgrade-soaking-overrides
Upgrade soaking override.
Defines a specific soaking time override for a particular upgrade
propagating through the current scope that supercedes the default
soaking duration configured by --default-upgrade-soaking.
To set an upgrade soaking override of 12 hours for the upgrade with
name, k8s_control_plane, and version, 1.23.1-gke.1000, run:
$ gcloud container fleet scopes update SCOPE_NAME \
--add-upgrade-soaking-override=12h \
--upgrade-selector=name="k8s_control_plane",version="1.23.1-gke.1000"
--add-upgrade-soaking-override=ADD_UPGRADE_SOAKING_OVERRIDE
Overrides the soaking time for a particular upgrade name and
version propagating through the current scope. Set soaking to 0
days to bypass soaking and fast-forward the upgrade to the
downstream scope.
See $ gcloud topic datetimes for information on duration formats.
This flag argument must be specified if any of the other
arguments in this group are specified.
--upgrade-selector=[name=NAME],[version=VERSION]
Name and version of the upgrade to be overridden where version is
a full GKE version. Currently, name can be either
k8s_control_plane or k8s_node.
This flag argument must be specified if any of the other
arguments in this group are specified.
At most one of these can be specified:
--reset-upstream-scope
Clears the relationship between the current scope and its upstream
scope in the rollout sequence.
To remove the link between SCOPE_NAME and its upstream scope, run:
$ gcloud container fleet scopes update SCOPE_NAME \
--reset-upstream-scope
--upstream-scope=UPSTREAM_SCOPE
Full resource name of the upstream scope in the format of
projects/{project}/locations/{location}/scopes/{scope}. GKE will
finish upgrades on the upstream scope before applying the same
upgrades to the current scope.
To configure the upstream scope for SCOPE_NAME, run:
$ gcloud container fleet scopes update SCOPE_NAME \
--upstream-scope=projects/{upstream_project}/locations/global/scopes/{upstream_scope}
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 scopes update
$ gcloud beta container fleet scopes update