[GH-ISSUE #239] Pipelines persistency #83

Closed
opened 2026-10-18 21:05:44 +00:00 by bsakaguchi · 1 comment
Owner

Originally created by @jkleinkauff on GitHub (May 9, 2025).
Original GitHub issue: https://github.com/open-webui/helm-charts/issues/239

Hey friends!
This is not a bug I think.

I've deployed OWUI and the pipelines module using this helm chart. To upload new pipelines to the platform, I have an initContainer in pipelines.extraInitContainer. The yaml also has the volume configuration to mount it to the pipelines folder properly.

  extraInitContainers:
    - name: fetch-github-folder
      image: appropriate/curl
      command:
        - sh
        - -c
        - |
          set -e
          echo "Fetching files from GitHub branch..."
          we clone the gh dir here.

This setup works ok. The problem is that whenever the pipeline pod is rebooted, any changes we've made to the Pipeline Valves are being overwritten by the default values configured in the pipe script. I understand why this is happening, since every time the pod boots it will clone the repo again. My question is if there is a better way of cloning the github repo or perhaps something to persist the pipeline changes?

Chart version: 6.0.0

Thank you!.

Originally created by @jkleinkauff on GitHub (May 9, 2025). Original GitHub issue: https://github.com/open-webui/helm-charts/issues/239 Hey friends! This is not a bug I think. I've deployed OWUI and the pipelines module using this helm chart. To upload new pipelines to the platform, I have an initContainer in pipelines.extraInitContainer. The yaml also has the volume configuration to mount it to the pipelines folder properly. ``` extraInitContainers: - name: fetch-github-folder image: appropriate/curl command: - sh - -c - | set -e echo "Fetching files from GitHub branch..." we clone the gh dir here. ``` This setup works ok. The problem is that whenever the pipeline pod is rebooted, any changes we've made to the Pipeline Valves are being overwritten by the default values configured in the pipe script. I understand why this is happening, since every time the pod boots it will clone the repo again. My question is if there is a better way of cloning the github repo or perhaps something to persist the pipeline changes? Chart version: 6.0.0 Thank you!.
bsakaguchi 2026-10-18 21:05:44 +00:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@james-westbrook commented on GitHub (Apr 9, 2026):

Pipelines is considered legacy at this point and is not recommended for new deployments, so we are not going to put much more energy into solving issues with workarounds available at this time.

<!-- gh-comment-id:4210702211 --> @james-westbrook commented on GitHub (Apr 9, 2026): Pipelines is considered legacy at this point and is not recommended for new deployments, so we are not going to put much more energy into solving issues with workarounds available at this time.
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#83
No description provided.