Thank you for your feedback. This is due to the fact that the yatai-deployment helm chart upgrade updated the environment variable secret but yatai-deployment was not restarted, this will be fixed in the next release.
You can currently fix this by restarting yatai-deployment manually with the following command:
kubectl -n yatai-deployment rollout restart deploy/yatai-deployment