gcloud container fleet scopes rbacrolebindings create

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 [e-mail], run:

gcloud container fleet scopes rbacrolebindings create RBRB --scope=SCOPE --role=admin --user=[e-mail]

To create a viewer RBAC RoleBinding RBRB in scope SCOPE for group [e-mail], run:

gcloud container fleet scopes rbacrolebindings create RBRB --scope=SCOPE --role=viewer --group=[e-mail]

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