Make LiteLLM admin password optional with a generated default#703
Merged
Conversation
aivong-openhands
approved these changes
Jun 11, 2026
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
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.
Follow-up to #690. The
litellm_admin_passwordKOTS field wasrequiredwith no default, which hard-blocks every upgrade from pre-0.7.44 until the admin invents a password — even on installs that never use the LiteLLM UI (hit on the R03 0.7.34→0.7.44 upgrade, and KOTSrequiredis not satisfied by adefault).Change
required: true; generate an initial value withvalue: '{{repl RandomString 32}}'— the same once-generated-then-sticky pattern the other bundled secrets (jwt_secret, redis_password, keycloak_admin_password) already use.hidden) so the no-kubectl flow from Add KOTS LiteLLM admin password #690 is unchanged: an admin who wants the LiteLLM dashboard sets their own password in the KOTS config and deploys — the existing pod checksum annotation restartsopenhands-litellmand the new password takes effect.Behavior
UI_PASSWORDinlitellm-env-secretsis now never empty (verified viahelm templaterender), so no chart changes needed.No chart content changes — replicated/config.yaml only.