Currently, a rolling restart of the K8s deployment is triggered in response to a change in the context of secrets.yaml or configmap.yaml. As SOPS is frequently used to encrypt values in these manifests so that they can be stored in VCS, it would be useful to support syntax commonly used to name these files when installing/upgrading the Helm chart. This would allow Lightdash Helm chart deployments to automatically perform a rolling restart in response to values changing in these manifests, matching the behaviour for the default secrets.yaml file.

Without this, when secrets values are changed in files using this syntax, a rolling restart or scaling event must be manually performed to mount the new K8s secret values to pods in the deployment.