Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
    2. history
×

v1.SubjectRulesReview

Description

SubjectRulesReview is a resource you can create to determine which actions another user can perform in a namespace

Object Schema

Expand or mouse-over a field for more information about it.

apiVersion:

kind:

spec:

  groups:

  - [string]:

  scopes:

  - [string]:

  user:

status:

  evaluationError:

  rules:

  - apiGroups:

  - - [string]:

    attributeRestrictions:

      Raw:

    nonResourceURLs:

    - [string]:

    resourceNames:

    - [string]:

    resources:

    - [string]:

    verbs:

    - [string]:

Operations

Create a SubjectRulesReview

Create a SubjectRulesReview

HTTP request

POST /oapi/v1/subjectrulesreviews HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json'

{
  "kind": "SubjectRulesReview",
  "apiVersion": "v1",
  ...
}

Curl request

$ curl -k \
    -X POST \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    https://$ENDPOINT/oapi/v1/subjectrulesreviews <<'EOF'
{
  "kind": "SubjectRulesReview",
  "apiVersion": "v1",
  ...
}
EOF

HTTP body

Parameter Schema

body

v1.SubjectRulesReview

Query parameters

Parameter Description

pretty

If 'true', then the output is pretty printed.

Responses

HTTP Code Schema

200 OK

v1.SubjectRulesReview

401 Unauthorized

Consumes

  • */*

Produces

  • application/json

  • application/yaml

  • application/vnd.kubernetes.protobuf

Create a SubjectRulesReview in a namespace

Create a SubjectRulesReview

HTTP request

POST /oapi/v1/namespaces/$NAMESPACE/subjectrulesreviews HTTP/1.1
Authorization: Bearer $TOKEN
Accept: application/json
Connection: close
Content-Type: application/json'

{
  "kind": "SubjectRulesReview",
  "apiVersion": "v1",
  ...
}

Curl request

$ curl -k \
    -X POST \
    -d @- \
    -H "Authorization: Bearer $TOKEN" \
    -H 'Accept: application/json' \
    -H 'Content-Type: application/json' \
    https://$ENDPOINT/oapi/v1/namespaces/$NAMESPACE/subjectrulesreviews <<'EOF'
{
  "kind": "SubjectRulesReview",
  "apiVersion": "v1",
  ...
}
EOF

HTTP body

Parameter Schema

body

v1.SubjectRulesReview

Path parameters

Parameter Description

namespace

object name and auth scope, such as for teams and projects

Query parameters

Parameter Description

pretty

If 'true', then the output is pretty printed.

Responses

HTTP Code Schema

200 OK

v1.SubjectRulesReview

401 Unauthorized

Consumes

  • */*

Produces

  • application/json

  • application/yaml

  • application/vnd.kubernetes.protobuf