oadm-policy-add-role-to-user man page

oadm policy add-role-to-user — Add a role to users or serviceaccounts for the current project

Synopsis

oadm policy add-role-to-user [Options]

Description

Add a role to users or serviceaccounts for the current project

Options

--role-namespace=""
namespace where the role is located: empty means a role defined in cluster policy
-z, --serviceaccount=[]
service account in the current namespace to use as a user

Options Inherited from Parent Commands

--api-version=""
DEPRECATED: The API version to use when talking to the server

--as=""
Username to impersonate for the operation.

--certificate-authority=""
Path to a cert. file for the certificate authority.

--client-certificate=""
Path to a client certificate file for TLS.

--client-key=""
Path to a client key file for TLS.

--cluster=""
The name of the kubeconfig cluster to use

--config=""
Path to the config file to use for CLI requests.

--context=""
The name of the kubeconfig context to use

--google-json-key=""
The Google Cloud Platform Service Account JSON Key to use for authentication.

--insecure-skip-tls-verify=false
If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure.

--log-flush-frequency=0
Maximum number of seconds between log flushes

--match-server-version=false
Require server version to match client version

-n, --namespace=""
If present, the namespace scope for this CLI request.

--server=""
The address and port of the Kubernetes API server

--token=""
Bearer token for authentication to the API server.

--user=""
The name of the kubeconfig user to use

Example

# Add the 'view' role to user1 for the current project
oadm policy add-role-to-user view user1

# Add the 'edit' role to serviceaccount1 for the current project
oadm policy add-role-to-user edit -z serviceaccount1

See Also

oadm-policy(1),

History

June 2016, Ported from the Kubernetes man-doc generator

Referenced By

oadm-policy(1).

Openshift CLI User Manuals Openshift June 2016