Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: clarify that context-aware capabilities are available using ClusterAdmissionPolicyGroup only #525

Merged
merged 1 commit into from
Jan 27, 2025
Merged

docs: clarify that context-aware capabilities are available using ClusterAdmissionPolicyGroup only #525

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion docs/explanations/policy-groups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -228,6 +228,9 @@ Another distinction between policy groups and ordinary policies is the location
where context-aware resource rules are defined. Each policy in a group
accepts an optional `contextAwareResources` field to specify the resources that
the policy is allowed to access during evaluation.
Similarly to ordinary policies, context-aware capabilities can only be used by defining a `ClusterAdmissionPolicyGroup`.
This is for security reasons, as `AdmissionPolicyGroup` resources can be deployed by unprivileged users.
For more details, refer to the [context-aware policies](./context-aware-policies.md) documentation.

<details>

Expand All @@ -237,7 +240,7 @@ An example of a policy group that makes use of a context-aware policy.

```yaml
apiVersion: policies.kubewarden.io/v1
kind: ClusterAdmissionPolicyGroup # or AdmissionPolicyGroup
kind: ClusterAdmissionPolicyGroup
metadata:
name: demo-ctx-aware
spec:
Expand Down
Loading