[GH-ISSUE #90] Some settings like model whitelisting, default model and default user role are not persisted #37

Closed
opened 2026-10-18 21:04:59 +00:00 by bsakaguchi · 2 comments
Owner

Originally created by @oboudry-mvp on GitHub (Oct 2, 2024).
Original GitHub issue: https://github.com/open-webui/helm-charts/issues/90

On Open-WebUI deployed using the provided helm chart found at https://helm.openwebui.com/. With an existing persistent volume defined in values.yaml file and mounted as /app/backend/data. Users, custom prompts, are persistent across reboot. All works fine on that side.

But other settings like:

  • Default user role
  • Default model
  • Models whitelisting

are reset each time a new pod is created.

I did not find corresponding variables in the helm chart to define these values. Is there a way these can be persisted ?

Originally created by @oboudry-mvp on GitHub (Oct 2, 2024). Original GitHub issue: https://github.com/open-webui/helm-charts/issues/90 On Open-WebUI deployed using the provided helm chart found at https://helm.openwebui.com/. With an existing persistent volume defined in `values.yaml` file and mounted as `/app/backend/data`. Users, custom prompts, are persistent across reboot. All works fine on that side. But other settings like: - Default user role - Default model - Models whitelisting are reset each time a new pod is created. I did not find corresponding variables in the helm chart to define these values. Is there a way these can be persisted ?
Author
Owner

@oboudry-mvp commented on GitHub (Oct 2, 2024):

Sorry, should have digged a bit more before posting. I found the config.py file and noticed a lot of the config comes from environment variables. Setting these in my values file fixed the question.

extraEnvVars:
  # -- Default API key value for Pipelines. Should be updated in a production deployment, or be changed to the required API key if not using Pipelines
  - name: OPENAI_API_KEYS
    valueFrom:
      secretKeyRef:
        name: openai-config
        key: api-keys
  - name: OPENAI_API_BASE_URLS
    valueFrom:
      secretKeyRef:
        name: openai-config
        key: api-urls
  - name: ENABLE_MODEL_FILTER
    value: "true"
  - name: MODEL_FILTER_LIST
    value: "gpt-4o-mini;gpt-4o-2024-08-06;ask_hr_policies"
  - name: DEFAULT_MODELS
    value: "gpt-4o-mini"
  - name: DEFAULT_LOCALE
    value: "fr_FR"
  - name: DEFAULT_USER_ROLE
    value: "user"
  - name: MICROSOFT_CLIENT_ID
    value: "39f9d7b7-4595-468a-b088-8d86db174b33"
  - name: MICROSOFT_CLIENT_TENANT_ID
    value: "eb0565ca-9b1f-4a27-a2df-0dcbdeac9fa0"
  - name: OAUTH_MERGE_ACCOUNTS_BY_EMAIL
    value: "true"
  - name: ENABLE_OAUTH_SIGNUP
    value: "true"
  - name: MICROSOFT_CLIENT_SECRET
    valueFrom:
      secretKeyRef:
        name: openai-config
        key: ms-client-secret

<!-- gh-comment-id:2388491008 --> @oboudry-mvp commented on GitHub (Oct 2, 2024): Sorry, should have digged a bit more before posting. I found the config.py file and noticed a lot of the config comes from environment variables. Setting these in my values file fixed the question. ``` extraEnvVars: # -- Default API key value for Pipelines. Should be updated in a production deployment, or be changed to the required API key if not using Pipelines - name: OPENAI_API_KEYS valueFrom: secretKeyRef: name: openai-config key: api-keys - name: OPENAI_API_BASE_URLS valueFrom: secretKeyRef: name: openai-config key: api-urls - name: ENABLE_MODEL_FILTER value: "true" - name: MODEL_FILTER_LIST value: "gpt-4o-mini;gpt-4o-2024-08-06;ask_hr_policies" - name: DEFAULT_MODELS value: "gpt-4o-mini" - name: DEFAULT_LOCALE value: "fr_FR" - name: DEFAULT_USER_ROLE value: "user" - name: MICROSOFT_CLIENT_ID value: "39f9d7b7-4595-468a-b088-8d86db174b33" - name: MICROSOFT_CLIENT_TENANT_ID value: "eb0565ca-9b1f-4a27-a2df-0dcbdeac9fa0" - name: OAUTH_MERGE_ACCOUNTS_BY_EMAIL value: "true" - name: ENABLE_OAUTH_SIGNUP value: "true" - name: MICROSOFT_CLIENT_SECRET valueFrom: secretKeyRef: name: openai-config key: ms-client-secret ```
Author
Owner

@oboudry-mvp commented on GitHub (Oct 2, 2024):

Not an issue

<!-- gh-comment-id:2388492011 --> @oboudry-mvp commented on GitHub (Oct 2, 2024): Not an issue
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/helm-charts#37
No description provided.