You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/blog/_posts/2021-12-17-security-profiles-operator-v0.4.0/index.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -104,11 +104,11 @@ validations are done here.
104
104
105
105
### AppArmor support
106
106
107
-
<!--
108
-
- Add CRD type to represent AppArmor profiles. (#643, @pjbgf)
109
-
- `spod` can load and unload AppArmor profiles into clusters host servers.
110
-
`spod` now runs as `root` and `privileged` when apparmor is enabled. (#680, @pjbgf)
111
-
-->
107
+
This version introduces the initial support for AppArmor, allowing users to load and
108
+
unload AppArmor profiles into cluster nodes by using the new [AppArmorProfile](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/deploy/base/crds/apparmorprofile.yaml) CRD.
109
+
110
+
To enable AppArmor support use the [enableAppArmor feature gate](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/examples/config.yaml#L10) switch of your SPO configuration.
111
+
Then use our [apparmor example](https://github.com/kubernetes-sigs/security-profiles-operator/blob/main/examples/apparmorprofile.yaml) to deploy your first profile across your cluster.
0 commit comments