Skip to content

fix(litellm): allow root seed initContainer under restricted PSS - #11

Open
Mushtaq-BGA wants to merge 1 commit into
mainfrom
fix/litellm-pss
Open

Mushtaq-BGA wants to merge 1 commit into
mainfrom
fix/litellm-pss

Conversation

@Mushtaq-BGA

Copy link
Copy Markdown
Contributor

Problem

The litellm namespace inherited the cluster-default restricted Pod Security Standard, which forbids running as root. The prisma-engine-seed initContainer runs as root by design, so under restricted PSS the deployment could not schedule.

Fix

Stamp the litellm namespace with baseline PSS (matching how keycloak is handled), scoped to that namespace only — the workload pods keep their own hardened securityContext.

Notes

Pre-existing bug, independent of the SeaweedFS object-store migration; surfaced when deploying litellm mode on a restricted-PSS cluster.

The litellm namespace inherited the cluster-default restricted PSS, which
blocks the deliberate root prisma-engine-seed initContainer, so the deployment
could not schedule. Stamp the namespace with baseline PSS (as keycloak does),
scoped to that namespace only.
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.

1 participant