hotfix: revert litellm guardrails (#540 + #544) — logging_only mode crash-looped litellm - #545
Merged
Merged
Conversation
lilyshen0722
added a commit
that referenced
this pull request
Jul 1, 2026
…rash-looped litellm (#545) * Revert "feat(litellm): prompt-injection guardrail + enforce-moderation scoped to platform features (#544)" This reverts commit 33059c1. * Revert "feat(litellm): add OpenAI moderation guardrail (monitor-only) for anti-pattern detection (#540)" This reverts commit 5a646c0.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Incident: the guardrails config crash-looped litellm on the deploy that rolled the pod. Root cause:
mode: "logging_only"(from #540) is NOT a valid guardrail event hook in LiteLLM v1.88 — onlypre_call/during_call/post_callare supported. It sat in the configmap since #540 but only loaded when #544 rolled the litellm pod →ValueError: Event hook GuardrailEventHooks.logging_only is not in the supported event hooks→Application startup failed→ CrashLoopBackOff (fleet LLM proxy down).Recovery: stripped the guardrails block from the live configmap + restarted litellm (now 3/3, 0 restarts). This PR reverts #540 + #544 so
main/the next deploy is safe (matches the recovered live state).Re-do plan: re-introduce guardrails with VALID modes (drop the unsupported logging_only monitor; enforce-moderation + injection scoped to platform features via
during_call), and VALIDATE the config boots in a throwaway litellm before deploying to the fleet — the lesson is an unvalidated guardrail config can take the whole proxy down. Tracked in #541 / #12.🤖 Generated with Claude Code