[Question] Update syncing to otwld/ollama-helm? #11

New Issue

2026-02-15T19:15:24-05:00

yindo commented

2026-02-15 19:15:24 -05:00

Originally created by @malcolmlewis on GitHub (May 16, 2024).

Hi, there are a number of Nvidia GPU updates in the latest otwld/ollama-helm chart
App version: 0.1.38
Chart version: 0.29.1

If I do a fresh deployment on the open-webui chart, should these get pulled, or does the chart need updating?

Originally created by @malcolmlewis on GitHub (May 16, 2024). Hi, there are a number of Nvidia GPU updates in the latest otwld/ollama-helm chart App version: 0.1.38 Chart version: 0.29.1 If I do a fresh deployment on the open-webui chart, should these get pulled, or does the chart need updating?

yindo closed this issue

2026-02-15 19:15:24 -05:00

yindo commented

2026-02-15 19:15:24 -05:00

@westbrook-ai commented on GitHub (May 26, 2024):

Hey @robrakaric, could use your help understanding the behavior for the embedded Ollama chart.

I see that the Chart.yaml file pulls versions of the Ollama chart that are greater than version 0.24.0: https://github.com/open-webui/helm-charts/blob/main/charts/open-webui/Chart.yaml#L27

I also see that we have version v0.25.0 embedded in charts: https://github.com/open-webui/helm-charts/tree/main/charts/open-webui/charts

Do you know offhand whether the OWUI Helm chart pull the latest chart on a new build, or if it pulls the embedded 0.25.0 chart we have in the repo?

@westbrook-ai commented on GitHub (May 26, 2024): Hey @robrakaric, could use your help understanding the behavior for the embedded Ollama chart. I see that the Chart.yaml file pulls versions of the Ollama chart that are greater than version 0.24.0: https://github.com/open-webui/helm-charts/blob/main/charts/open-webui/Chart.yaml#L27 I also see that we have version v0.25.0 embedded in `charts`: https://github.com/open-webui/helm-charts/tree/main/charts/open-webui/charts Do you know offhand whether the OWUI Helm chart pull the latest chart on a new build, or if it pulls the embedded 0.25.0 chart we have in the repo?

yindo commented

2026-02-15 19:15:25 -05:00

@malcolmlewis commented on GitHub (May 26, 2024):

@0xThresh Hi, I see;

Labels:              app.kubernetes.io/component=ollama                                                                                                                                    │
│                      app.kubernetes.io/instance=open-webui                                                                                                                                 │
│                      app.kubernetes.io/managed-by=Helm                                                                                                                                     │
│                      app.kubernetes.io/version=0.1.34                                                                                                                                      │
│                      helm.sh/chart=ollama-0.25.0                                                                                                                                           │
│                      pod-template-hash=56c55f7c6

@malcolmlewis commented on GitHub (May 26, 2024): @0xThresh Hi, I see; ```bash Labels: app.kubernetes.io/component=ollama │ │ app.kubernetes.io/instance=open-webui │ │ app.kubernetes.io/managed-by=Helm │ │ app.kubernetes.io/version=0.1.34 │ │ helm.sh/chart=ollama-0.25.0 │ │ pod-template-hash=56c55f7c6 ```

yindo commented

2026-02-15 19:15:25 -05:00

@robrakaric commented on GitHub (May 26, 2024):

@0xThresh good question. I'd have to do some testing.

What I'm not sure of is chart-releaser's behavior. The assets in the gh release will be most relevant, and I'm not sure if chart-releaser actually downloads the newest version (helm dependency update), uses the one in the repo, or just respects what's in Chart.lock (helm dependency build).

I'll mess around with in on my fork and see what I can find out.

@robrakaric commented on GitHub (May 26, 2024): @0xThresh good question. I'd have to do some testing. What I'm not sure of is `chart-releaser`'s behavior. The assets in the gh release will be most relevant, and I'm not sure if `chart-releaser` actually downloads the newest version (`helm dependency update`), uses the one in the repo, or just respects what's in `Chart.lock` (`helm dependency build`). I'll mess around with in on my fork and see what I can find out.

yindo commented

2026-02-15 19:15:25 -05:00

@westbrook-ai commented on GitHub (May 26, 2024):

We have a PR open that should get merged whenever Tim takes a look at it, so we can also observe the behavior there once we pull that in. Thanks for taking a look!

@westbrook-ai commented on GitHub (May 26, 2024): We have a PR open that should get merged whenever Tim takes a look at it, so we can also observe the behavior there once we pull that in. Thanks for taking a look!

yindo commented

2026-02-15 19:15:25 -05:00

@westbrook-ai commented on GitHub (Jun 3, 2024):

I'm working on an Open WebUI chart update that will upgrade to the newest release of Open WebUI, and am going to work on getting better Ollama dependency management in place as part of that PR. While the chart file does specify any Ollama chart version >=0.24.0, we don't have helm dependency update running in our Github workflow, so I think adding that in should help solve it.

@westbrook-ai commented on GitHub (Jun 3, 2024): I'm working on an Open WebUI chart update that will upgrade to the newest release of Open WebUI, and am going to work on getting better Ollama dependency management in place as part of that PR. While the chart file does specify any Ollama chart version >=0.24.0, we don't have `helm dependency update` running in our Github workflow, so I think adding that in should help solve it.

yindo commented

2026-02-15 19:15:25 -05:00