[Bug]: Helm deployment - updating values does not trigger deployment update

[leonardlin]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (Language Policy).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

e1f1184

RAGFlow image version

v0.24 and latest main

Other environment information

* Linux, AKS 1.37

Actual behavior

• Deploy ragflow via helm chart to AKS
• change a value in the helm/values.yaml
• Reploy ragflow via helm chart to AKS
• Pods are not recreated with the updated helm/values.yaml

Expected behavior

• The revision should increase and the pods should be recreated with the new values.yaml

Steps to reproduce

* Deploy ragflow via helm chart to AKS
* change a value in the helm/values.yaml
* Reploy ragflow via helm chart to AKS

Additional information

helm chart hashes the yamls and checks if it's updated.
Only if the hash has changed the deployments are updated.
This does not apply to secrets. Helm does not see inside secrets and any changes there.

Since ragflows helm config saves all configs as secrets helm chart does not detect the update.

Fix (will provide a PR)

• add explicit checksum/values: {{ .Values | toYaml | sha256sum }}