Chapter 4. PodSecurityPolicyReview [security.openshift.io/v1]
- Description
PodSecurityPolicyReview checks which service accounts (not users, since that would be cluster-wide) can create the
PodTemplateSpecin question.Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).
- Type
-
object - Required
-
spec
-
4.1. Specification
| Property | Type | Description |
|---|---|---|
|
|
| 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 |
|
|
| 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 |
|
|
| PodSecurityPolicyReviewSpec defines specification for PodSecurityPolicyReview |
|
|
| PodSecurityPolicyReviewStatus represents the status of PodSecurityPolicyReview. |
4.1.1. .spec
- Description
- PodSecurityPolicyReviewSpec defines specification for PodSecurityPolicyReview
- Type
-
object - Required
-
template
-
| Property | Type | Description |
|---|---|---|
|
|
| serviceAccountNames is an optional set of ServiceAccounts to run the check with. If serviceAccountNames is empty, the template.spec.serviceAccountName is used, unless it’s empty, in which case "default" is used instead. If serviceAccountNames is specified, template.spec.serviceAccountName is ignored. |
|
| template is the PodTemplateSpec to check. The template.spec.serviceAccountName field is used if serviceAccountNames is empty, unless the template.spec.serviceAccountName is empty, in which case "default" is used. If serviceAccountNames is specified, template.spec.serviceAccountName is ignored. |
4.1.2. .status
- Description
- PodSecurityPolicyReviewStatus represents the status of PodSecurityPolicyReview.
- Type
-
object - Required
-
allowedServiceAccounts
-
| Property | Type | Description |
|---|---|---|
|
|
| allowedServiceAccounts returns the list of service accounts in this namespace that have the power to create the PodTemplateSpec. |
|
|
| ServiceAccountPodSecurityPolicyReviewStatus represents ServiceAccount name and related review status |
4.1.3. .status.allowedServiceAccounts
- Description
- allowedServiceAccounts returns the list of service accounts in this namespace that have the power to create the PodTemplateSpec.
- Type
-
array
4.1.4. .status.allowedServiceAccounts[]
- Description
- ServiceAccountPodSecurityPolicyReviewStatus represents ServiceAccount name and related review status
- Type
-
object - Required
-
name
-
| Property | Type | Description |
|---|---|---|
|
|
allowedBy is a reference to the rule that allows the PodTemplateSpec. A rule can be a SecurityContextConstraint or a PodSecurityPolicy A | |
|
|
| name contains the allowed and the denied ServiceAccount name |
|
|
| A machine-readable description of why this operation is in the "Failure" status. If this value is empty there is no information available. |
|
| template is the PodTemplateSpec after the defaulting is applied. |
4.2. API endpoints
The following API endpoints are available:
/apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyreviews-
POST: create a PodSecurityPolicyReview
-
4.2.1. /apis/security.openshift.io/v1/namespaces/{namespace}/podsecuritypolicyreviews
| Parameter | Type | Description |
|---|---|---|
|
|
| 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 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. |
- HTTP method
-
POST - Description
- create a PodSecurityPolicyReview
| Parameter | Type | Description |
|---|---|---|
|
|
|
| HTTP code | Reponse body |
|---|---|
| 200 - OK |
|
| 201 - Created |
|
| 202 - Accepted |
|
| 401 - Unauthorized | Empty |
