Skip to content

fix(apparmor): allow sockets in cri-containerd profile (#5218) - #5235

Merged
bschimke95 merged 1 commit into
1.33from
KU-4123/strict-on-plucky-fix-backport-1.33
Sep 16, 2025
Merged

fix(apparmor): allow sockets in cri-containerd profile (#5218)#5235
bschimke95 merged 1 commit into
1.33from
KU-4123/strict-on-plucky-fix-backport-1.33

Conversation

@bschimke95

Copy link
Copy Markdown
Contributor

Add explicit AppArmor rules to permit common socket types (inet, inet6, unix) needed by Kubernetes workloads (e.g., kube-controller, coredns). Plucky ships AppArmor 4.1.0, which is stricter and requires exact socket types to be set. This resolves "apparmor=DENIED operation=create class=net" denials.

Fixes #5082
Fixes #5190
Fixes #5140

Add explicit AppArmor rules to permit common socket types (inet, inet6, unix)
needed by Kubernetes workloads (e.g., kube-controller, coredns). Plucky ships
AppArmor 4.1.0, which is stricter and requires exact socket types to be set.
This resolves "apparmor=DENIED operation=create class=net" denials.

Fixes #5082
Fixes #5190
Fixes #5140
@bschimke95
bschimke95 merged commit 34f73f8 into 1.33 Sep 16, 2025
22 checks passed
@bschimke95
bschimke95 deleted the KU-4123/strict-on-plucky-fix-backport-1.33 branch September 16, 2025 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants