Antonio Gámez, PhD

The [3.8.2](https://github.com/helm/helm/releases/tag/v3.8.2) has been released, but it does not include our PR. It has been target to v3.9.0 😞

3.9.0 is planned for May 11th, but they have tagged an [rc1](https://github.com/helm/helm/releases/tag/v3.9.0-rc.1) and our changes have not been included. We are still blocked by https://github.com/helm/helm/pull/10408. So the update is... there...

Note that Helm 3.9.X includes some breaking changes with regards to the k8s version it uses in its deps. More info: https://github.com/vmware-tanzu/kubeapps/pull/4743

I've taken a look at the current status and... the PR was closed without a merge. However, I've noticed they added [a way to set bearer tokens (just passing a...

After a second analysis, we can't leverage from what I said. We are using the resolver and other fields for both production and testing codes. An alternative idea is to...

It seems more people are interested in setting a custom resolver, or, at least, modifying some of its default options: https://github.com/helm/helm/pull/10408#discussion_r919329730, but still I haven't heard back from the maintainers...

PR just approved!! https://github.com/helm/helm/pull/11129#pullrequestreview-1065422180

After Kapp released a new version, we should be able to upgrade to the Helm latest version. This should be the first step, then this issue will get blocked again,...

Currently, our deps have been successfully updated and helm finally was upgraded to `v3.9.4`., which will ease the upgrade path to subsequent versions. According to their release process, _3.10.0 is...

[3.10.0-rc.1](https://github.com/helm/helm/releases/tag/v3.10.0-rc.1) has been released [without our PR](https://github.com/helm/helm/pull/11129). I've pinged Helm folks to see if we could get it merged for the next rc release.