Skip to content

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

Merged
bschimke95 merged 1 commit into1.32-strictfrom
KU-4123/strict-on-plucky-fix-backport-1.32-strict
Sep 16, 2025
Merged

fix(apparmor): allow sockets in cri-containerd profile (Backport #5218)#5232
bschimke95 merged 1 commit into1.32-strictfrom
KU-4123/strict-on-plucky-fix-backport-1.32-strict

Conversation

@bschimke95
Copy link
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 e7237f1 into 1.32-strict Sep 16, 2025
22 checks passed
@bschimke95 bschimke95 deleted the KU-4123/strict-on-plucky-fix-backport-1.32-strict 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants