fix(openbao): restricted-PodSecurity compliance for snapshot CronJob #178

2026-07-14T00:08:37Z

claude-bot commented

2026-07-14 00:08:37 +00:00

Follow-up to #177: the manual verification Job ran successfully (744 KB snapshot written, retention pruning OK) but tripped the restricted:latest PodSecurity warning — the container was missing allowPrivilegeEscalation: false and capabilities.drop: [ALL]. Two-line securityContext addition; no functional change.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CRgBFn9m8a2ncFMLusikH6

Follow-up to #177: the manual verification Job ran successfully (744 KB snapshot written, retention pruning OK) but tripped the `restricted:latest` PodSecurity **warning** — the container was missing `allowPrivilegeEscalation: false` and `capabilities.drop: [ALL]`. Two-line securityContext addition; no functional change. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01CRgBFn9m8a2ncFMLusikH6

claude-bot added 1 commit 2026-07-14 00:08:38 +00:00

fix(openbao): satisfy restricted PodSecurity in snapshot CronJob 476cfb2d12

allowPrivilegeEscalation=false + drop ALL capabilities on the snapshot
container — the manual verification run worked but tripped the
restricted:latest warning.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CRgBFn9m8a2ncFMLusikH6

k.renner merged commit 2e4fdff9e2 into master

2026-07-14 00:10:32 +00:00

k.renner referenced this issue from a commit

2026-07-14 00:10:34 +00:00

Merge pull request 'fix(openbao): restricted-PodSecurity compliance for snapshot CronJob' (#178) from openbao-snapshot-hardening into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#178