[GH-ISSUE #33] Pipelines Not Detected #14

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

Originally created by @Altair-Bueno on GitHub (Jun 13, 2024).
Original GitHub issue: https://github.com/open-webui/helm-charts/issues/33

Expected behavior

Deploying the chart with the following values should enable pipelines

ollama:
  runtimeClassName: nvidia
  persistentVolume:
    enabled: true
  ollama:
    gpu:
      enabled: true
      type: nvidia
      number: 2

Current behavior

Pipelines tab shows the message Pipelines Not Detected

image

Current workaround

Setting the API key to 0p3n-w3bu!, as noted by pipelines' README, fixes this issue

Originally created by @Altair-Bueno on GitHub (Jun 13, 2024). Original GitHub issue: https://github.com/open-webui/helm-charts/issues/33 ### Expected behavior Deploying the chart with the following values should enable pipelines ```yml ollama: runtimeClassName: nvidia persistentVolume: enabled: true ollama: gpu: enabled: true type: nvidia number: 2 ``` ### Current behavior Pipelines tab shows the message `Pipelines Not Detected` ![image](https://github.com/open-webui/helm-charts/assets/67512202/73218b7c-c5cd-4afc-9763-6478ab84505b) ### Current workaround Setting the API key to `0p3n-w3bu!`, as noted by [pipelines' README](https://github.com/open-webui/pipelines), fixes this issue
bsakaguchi 2026-10-18 21:04:35 +00:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@james-westbrook commented on GitHub (Jun 13, 2024):

Thanks for the report @Altair-Bueno. In your Connections tab in Open WebUI, were you seeing the service name for Pipelines correctly populated there? I'm assuming you did, and that once you added the API key value there, you were able to connect to Pipelines correctly.

<!-- gh-comment-id:2166558503 --> @james-westbrook commented on GitHub (Jun 13, 2024): Thanks for the report @Altair-Bueno. In your `Connections` tab in Open WebUI, were you seeing the service name for Pipelines correctly populated there? I'm assuming you did, and that once you added the API key value there, you were able to connect to Pipelines correctly.
Author
Owner

@james-westbrook commented on GitHub (Jun 13, 2024):

I've just confirmed that the behavior I described above is accurate:
image

We can fix this by adding the API key to the helper when one isn't defined. Thanks again for the report, PR is welcome if you want to, otherwise I'll fix it when I can.

<!-- gh-comment-id:2166583244 --> @james-westbrook commented on GitHub (Jun 13, 2024): I've just confirmed that the behavior I described above is accurate: <img width="1245" alt="image" src="https://github.com/open-webui/helm-charts/assets/104535511/5de82e82-a5d6-4a02-b808-531c806cd590"> We can fix this by adding the API key to the helper when one isn't defined. Thanks again for the report, PR is welcome if you want to, otherwise I'll fix it when I can.
Author
Owner

@james-westbrook commented on GitHub (Jun 15, 2024):

Fixed: https://github.com/open-webui/helm-charts/pull/39

<!-- gh-comment-id:2169156113 --> @james-westbrook commented on GitHub (Jun 15, 2024): Fixed: https://github.com/open-webui/helm-charts/pull/39
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#14
No description provided.