No documented method for safeguarding a Helm release from Fleet

[dagan]

Once a Helm release is created by Fleet, there does not appear to be a way to tell Fleet to not make any changes without user intervention. Fleet's documentation mentions a pause property on a bundle, but setting it to true does not appear to have any effect whatsoever after the bundle is installed (at least in v0.3.7) and there is no mention in the docs of how to push changes through if pause is working.

Without a mollygaurd preventing accidental removals, significant data loss is possible (uninstalling Istio Operator or Longhorn can have catastrophic results). Is pause simply not working as intended? Is there a different strategy missing from the docs?

[StrongMonkey]

Related #683 #680