# Storage-proxy missing in official Helm chart for OS mender **URL:** \ **Category:** General Discussions\ **Tags:** mender-server\ **Created:** [March 28, 2021, 6:31pm UTC](https://hub.mender.io/t/storage-proxy-missing-in-official-helm-chart-for-os-mender/3433 "2021-03-28T18:31:23Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![markus4dev](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@markus4dev](https://hub.mender.io/u/markus4dev)\ **Post date:** [March 28, 2021, 6:31pm UTC](https://hub.mender.io/t/storage-proxy-missing-in-official-helm-chart-for-os-mender/3433/1 "2021-03-28T18:31:23Z")
Hi! I have been running on older mender server (2.1) and decided to install version 2.5 in k8s cluster. I followed this [instructions](https://mender.io/blog/official-helm-chart-for-mender-2-5) for installing mender server (os version) with helm charts. I got everything up and running but noticed when checking the pods that there is no storage-proxy. It is not in the [charts file](https://github.com/mendersoftware/mender-helm/blob/master/mender/values.yaml). Is the storage-proxy not needed any more? What about workflow-engine (mender-workflow-server, mender-workflow-worker, mender-create-artifact-worker), is it part of the os version or only enterprise? I can’t find any information in the [Mender docs](https://docs.mender.io/2.5/server-installation/overview). The overview diagram in the docs doesn’t reflect the one in the [mender-integration](https://github.com/mendersoftware/integration#how-to-use-in-production) repo. Could someone point out what components are actually needed as bare minimum to run mender server 2.5 (not in enterprise mode). Thanks! Regards, Markus ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [March 28, 2021, 7:07pm UTC](https://hub.mender.io/t/storage-proxy-missing-in-official-helm-chart-for-os-mender/3433/2 "2021-03-28T19:07:25Z")
@tranchitella can you help? ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [March 29, 2021, 4:18pm UTC](https://hub.mender.io/t/storage-proxy-missing-in-official-helm-chart-for-os-mender/3433/3 "2021-03-29T16:18:36Z")
Hello @markus4dev, the Mender’s Helm chart doesn’t provide the storage proxy as it is meant to be used with an external S3-compatible API end-point. Minio can be used, similarly to what you get running the docker-compose setup, but it is up to you to configure it and expose minio either directly over the internet, as an ingress or using a reverse proxy. Regarding your second question, workflow components are part of the Mender release, both open source and enterprise. ---
**Author:** ![markus4dev](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@markus4dev](https://hub.mender.io/u/markus4dev)\ **Post date:** [March 29, 2021, 6:48pm UTC](https://hub.mender.io/t/storage-proxy-missing-in-official-helm-chart-for-os-mender/3433/4 "2021-03-29T18:48:04Z")
Thanks for your reply @tranchitella! I think I got it, just for clarification: Mender-deployments uploads the release artifact files to a S3-compatible API endpoint that is defined under global.s3.AWS\_URI in the helm chart. And it is also this AWS\_URI (including the access key and secret key) that is passed on to the clients, in order for them to be able to download the new release artifact. Right? ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [March 29, 2021, 6:53pm UTC](https://hub.mender.io/t/storage-proxy-missing-in-official-helm-chart-for-os-mender/3433/5 "2021-03-29T18:53:48Z")
@markus4dev correct!