@Jermuk section C1 in this article describes modifying the values.yaml file. I learned how to do this a while back using OpenLens, but I had trouble rediscovering the documentation for setting up OpenLens when I had to do this again recently. I assume this is because the new Management Console is the "new" solution for adnimistration, monitoring, etc? What is the up-do-date recommended way to modify values.yaml?

W.r.t. OpenLens, you can set up a new UMH cluster by going to File > Add Cluster and then pasting the output of

sudo cat /etc/rancher/k3s/k3s.yaml

(on the host)

Yes, I found this demonstrated in an old youtube video.

what i have learned over the last couple of years is to have a specific values file containing only your modified values and use that with kubectl every time you upgrade.

@Ferdinand @Mateusz can you post the new recommended version you talked about today?

We wanted to use helm v3.17.0 (which is latest at the time of writing) as it has the [--reset-then-reuse-values](https://github.com/helm/helm/pull/9653) flag. If you are unable to use it, a very similar function can be done like this:

sudo $(which helm) repo update && sudo $(which helm) get values united-manufacturing-hub -n united-manufacturing-hub --kubeconfig /etc/rancher/k3s/k3s.yaml > /tmp/v.yaml && sudo $(which helm) upgrade united-manufacturing-hub united-manufacturing-hub/united-manufacturing-hub -n united-manufacturing-hub --reset-values --values /tmp/v.yaml --set nodered.tag=4.0.8 --version 0.27.0 --kubeconfig /etc/rancher/k3s/k3s.yaml --debug

^in this case we set the node red image version to 4.0.8, while emulating the behavior of --reset-then-reuse-values. See https://github.com/helm/helm/issues/8085#issuecomment-1404248379 for a better explaination of this flag.

This is basically what we discussed a long way back. I also wrote a bash script for this to extract all the changed values and compared it to the installed chart version and the new version to find if there was any removed values.. In my old( current) umh stack i have a lot of unused values since the chart have changed. this is from my perspective a quite large bug in helm which is good to handle in some way.