As a long-time Docker-slonker I agree, however then that requires me to remember to upgrade the container images which means that it's harder to ensure that it's up to date. If you set up a cronjob to update the VMs packages and then a script that runs `/upgrade` on the weechat server every time the weechat package version changes, then you don't need to think.

Consider having Renovate handle this for you - using a git repo to apply your manifests will make it pull updated container images

I have this very easily setup to a set of simple commands which I can run to deploy new versions of packages.

Basically 3 paths for:

- things with well-maintained upstream helm charts (checks the latest version of the helm chart and updates helmfile)

- things where I wrote a helm chart (checks for the latest container image and updates the values.yaml)

- things where there is no (reasonable) public docker image, or my own software, where I have full CI/CD to build and deploy a new container image.

Probably takes me 15 minutes a week to keep my two personal clusters fully up-to-date.