Daemonset doesn't force a rollout when the CID changes

[ben-nelson-nbcuni]

When the FALCONCTL_OPT_CID value changes in the Configmap, the Daemonset pods do not restart. This is a common issue for helm charts. Helm has a tips and tricks section dedicated to this issue.

On your pod annotations in daemonset.yaml please add the following to force a pod restart on CID changes:

spec:
  template:
    metadata:
      annotations:
        checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}