Feature request: Helm repositories

[djjudas21]

My current workflow is to use Fairwinds Nova to detect outdated Helm deployments, and use Nova Exporter to display outdated Helm deployments as alerts in Prometheus. When I get an alert, I manually update my deployment with helm upgrade.

Example output of Nova:

[jonathan@poseidon ~]$ nova find --format table --wide --show-old
Release Name     Chart Name       Namespace       HelmVersion    Installed    Latest     Old      Deprecated
============     ==========       =========       ===========    =========    ======     ===      ==========
argocd           argo-cd          argocd          3              7.3.1        7.3.2      true     false    

When I heard about Keel this week I thought it looked like a really neat solution to automate my existing process, but then I realised, Keel is watching image registries, not Helm repositories, and updating the image alone. In my experience, upgrading a Helm deployment by simply changing the image is potentially unsafe.

I think it would be better if Keel was able to watch Helm repos and then perform actual Helm upgrades using the new Helm chart - which should reference the image it is designed to be compatible with. This will also handle upgrading things that Helm manages other than the container image, e.g. any RBAC rules that may be needed.

I'm no coder, so unfortunately I can't help with the implementation, but I'm happy to test etc. Thanks.

[happysquiddo]

I know its late, but you may want to look into FluxCD. It can be configured to do just what you need.
https://github.com/fluxcd/helm-controller/blob/main/docs/spec/v2beta1/helmreleases.md