Cluster does not always get redeployed when updating parameters

[t-persson]

Description

There are a few parameters in the cluster specification that does not trigger a restart. This includes, but is not limited to, the ESR template.

I believe, based on gut feeling, that it is when we are updating configmaps and secrets that are then used in the deployments. But because the deployment itself does not get updated a reload is not triggered.

We must fix so that the cluster controller makes sure to re-deploy the deployments when any change that requires a restart has been made.

Additional Context

No response

Further links

No response