Skip to content

Fix CSI security context and SecurityPolicyException#189

Merged
aleksey-su merged 3 commits intomainfrom
fix/csi-spe
Apr 8, 2026
Merged

Fix CSI security context and SecurityPolicyException#189
aleksey-su merged 3 commits intomainfrom
fix/csi-spe

Conversation

@ptrvsrg
Copy link
Copy Markdown
Member

@ptrvsrg ptrvsrg commented Apr 8, 2026

Summary

Aligns the CSI node plugin’s pod security with policy expectations and documents the exception in SPE.

Changes

  • DaemonSet (node container): set allowPrivilegeEscalation: true (the default value is false, but if privileged is true, allowPrivilegeEscalation cannot be false), add capabilities.drop: [ALL] (this is requirement from admission policy engine).
  • SecurityPolicyException: allow allowPrivilegeEscalation: true (node and node-driver-registrar containers has enabled allowPrivilegeEscalation)
  • Tests: extend CSI node and SPE unittest suites to cover the new security context and SPE fields.

Why

Admission/policy checks may require explicit allowPrivilegeEscalation and a capability baseline (drop: ALL) even for privileged CSI node workloads; SPE must list the same allowances so the DaemonSet stays valid under the admission policy engine.

ptrvsrg added 3 commits April 8, 2026 16:44
Add rule for allowPrivilegeEscalation to CSI Node SPE

Signed-off-by: Sergey Petrov <sergey.petrov@flant.com>
Signed-off-by: Sergey Petrov <sergey.petrov@flant.com>
Signed-off-by: Sergey Petrov <sergey.petrov@flant.com>
@ptrvsrg ptrvsrg added the bug Something isn't working label Apr 8, 2026
@ptrvsrg ptrvsrg self-assigned this Apr 8, 2026
@ptrvsrg ptrvsrg marked this pull request as ready for review April 8, 2026 11:15
@aleksey-su aleksey-su merged commit 1a87add into main Apr 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants