Currently both checksums use the same key, so only one is present in the resulting Deployment. This is leading to our Deployments not restarting on rule changes.
Short description of the changes
Change the key for the rules so it's distinct from the one for config.
How to verify that this has the expected result
Deploy the chart, observe that there are now 2 checksum annotations on the Pod instead of only one.
Which problem is this PR solving?
Currently both checksums use the same key, so only one is present in the resulting Deployment. This is leading to our Deployments not restarting on rule changes.
Short description of the changes
Change the key for the rules so it's distinct from the one for config.
How to verify that this has the expected result
Deploy the chart, observe that there are now 2 checksum annotations on the Pod instead of only one.