Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

We recently upstreamed <https://github.com/flyteorg/flyte/commit/0bd4ab919b2ac49dbad888d0fe4195d02af5bf24|a fix for the stow token scope in GKE clusters with version > 1.25&gt; in the helm chart. Also after running `helm repo update` this is not included in the installed chart. Does the helm chart need to be released again? How does the process for this look like? Thanks :slightly_smiling_face:

Ya helm chart releases are tied to releases. Cc <@U017K8AJBAN> and <@U0265RTUJ5B> know better

yea the helm chart is published on release as well

but we have charts pushed to an OCI registry from main, if you are ok with bleeding edge, or need to test

<https://github.com/flyteorg/flyte/pkgs/container/helm-charts%2Fflyte-core|https://github.com/flyteorg/flyte/pkgs/container/helm-charts%2Fflyte-core>

<https://github.com/flyteorg/flyte/pkgs/container/helm-charts%2Fflyte-binary|https://github.com/flyteorg/flyte/pkgs/container/helm-charts%2Fflyte-binary>

Thanks, this helps a lot since currently I’m manually patching the flyteadmin configmap from time to time since the fix we upstreamed isn’t released yet :slightly_smiling_face: