Documentation around flagger.app/config-tracking is lacking

[WaDelma]

So when I read

flagger/docs/gitbook/usage/how-it-works.md

Lines 116 to 117 in b6ac5e1

	If you annotate your ConfigMap or Secret with `flagger.app/config-tracking: disabled`,
	Flagger will use the same object for the primary deployment instead of making a primary copy.

I thought that when adding this annotation flagger would now update canary and trigger rollout to primary deployment directly with the changes in the configmap/secret.

This doesn't seem to be the case.

The documentation should be made clearer in this regard. Maybe example could added how to get this behavior as doing checksum pattern on deployment won't work as that would just trigger flagger analysis. One option that I have thought would be to use sidecar that watches configmap/secret values and restarts pods.

Alternatively feature could be added to flagger for doing this. Maybe there already is and I am just missing it 🤷‍♀️