Chapter 5. RoleBinding [authorization.openshift.io/v1]

Description

RoleBinding references a Role, but not contain it. It can reference any Role in the same namespace or in the global namespace. It adds who information via (Users and Groups) OR Subjects and namespace information by which namespace it exists in. RoleBindings in a given namespace only have effect in that namespace (excepting the master namespace which has power in all namespaces).

Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer).

Type

object

Required

subjects
roleRef

5.1. Specification

Property	Type	Description
`apiVersion`	`string`	APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
`groupNames`	`array (string)`	GroupNames holds all the groups directly bound to the role. This field should only be specified when supporting legacy clients and servers. See Subjects for further details.
`kind`	`string`	Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
`metadata`	`ObjectMeta`	metadata is the standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
`roleRef`	`ObjectReference`	RoleRef can only reference the current namespace and the global namespace. If the RoleRef cannot be resolved, the Authorizer must return an error. Since Policy is a singleton, this is sufficient knowledge to locate a role.
`subjects`	`array (ObjectReference)`	Subjects hold object references to authorize with this rule. This field is ignored if UserNames or GroupNames are specified to support legacy clients and servers. Thus newer clients that do not need to support backwards compatibility should send only fully qualified Subjects and should omit the UserNames and GroupNames fields. Clients that need to support backwards compatibility can use this field to build the UserNames and GroupNames.
`userNames`	`array (string)`	UserNames holds all the usernames directly bound to the role. This field should only be specified when supporting legacy clients and servers. See Subjects for further details.

5.2. API endpoints

The following API endpoints are available:

/apis/authorization.openshift.io/v1/rolebindings
- GET: list objects of kind RoleBinding
/apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings
- GET: list objects of kind RoleBinding
- POST: create a RoleBinding
/apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings/{name}
- DELETE: delete a RoleBinding
- GET: read the specified RoleBinding
- PATCH: partially update the specified RoleBinding
- PUT: replace the specified RoleBinding

5.2.1. /apis/authorization.openshift.io/v1/rolebindings

HTTP method: GET
Description: list objects of kind RoleBinding

Table 5.1. HTTP responses
HTTP code	Reponse body
200 - OK	`RoleBindingList` schema
401 - Unauthorized	Empty

5.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings

HTTP method: GET
Description: list objects of kind RoleBinding

Table 5.2. HTTP responses
HTTP code	Reponse body
200 - OK	`RoleBindingList` schema
401 - Unauthorized	Empty

HTTP method: POST
Description: create a RoleBinding

Table 5.3. Query parameters
Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Table 5.4. Body parameters
Parameter	Type	Description
`body`	`RoleBinding` schema

Table 5.5. HTTP responses
HTTP code	Reponse body
200 - OK	`RoleBinding` schema
201 - Created	`RoleBinding` schema
202 - Accepted	`RoleBinding` schema
401 - Unauthorized	Empty

5.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings/{name}

Table 5.6. Global path parameters
Parameter	Type	Description
`name`	`string`	name of the RoleBinding

HTTP method: DELETE
Description: delete a RoleBinding

Table 5.7. Query parameters
Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

Table 5.8. HTTP responses
HTTP code	Reponse body
200 - OK	`Status` schema
202 - Accepted	`Status` schema
401 - Unauthorized	Empty

HTTP method: GET
Description: read the specified RoleBinding

Table 5.9. HTTP responses
HTTP code	Reponse body
200 - OK	`RoleBinding` schema
401 - Unauthorized	Empty

HTTP method: PATCH
Description: partially update the specified RoleBinding

Table 5.10. Query parameters
Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Table 5.11. HTTP responses
HTTP code	Reponse body
200 - OK	`RoleBinding` schema
201 - Created	`RoleBinding` schema
401 - Unauthorized	Empty

HTTP method: PUT
Description: replace the specified RoleBinding

Table 5.12. Query parameters
Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Table 5.13. Body parameters
Parameter	Type	Description
`body`	`RoleBinding` schema

Table 5.14. HTTP responses
HTTP code	Reponse body
200 - OK	`RoleBinding` schema
201 - Created	`RoleBinding` schema
401 - Unauthorized	Empty

Chapter 5. RoleBinding [authorization.openshift.io/v1]

5.1. Specification

5.2. API endpoints

5.2.1. /apis/authorization.openshift.io/v1/rolebindings

5.2.2. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings

5.2.3. /apis/authorization.openshift.io/v1/namespaces/{namespace}/rolebindings/{name}

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

Making open source more inclusive

About Red Hat

Red Hat legal and privacy links

Red Hat legal and privacy links