[question/support] What is the request/data/template flow when we leverage the --force flag and when we don't leverage it in the helm upgrade command?

[mananmongia]

This is about the issue we are facing in Kyverno when we use the --force flag.
I further need to understand the flow when we are using --force and when not using this flag so that I can further debug the issue.

For more details on the mentioned issue, refer to kyverno/kyverno#10144

When Kyverno's verify image policy is running on the controller, deployment is 

1. fails when --force is leveraged: deployment fails with error autogen-verify-image: kyverno.io/verify-images annotation cannot be changed
2. Passes without --forece and pods are deployed.

[gjenkins8]

By default Helm does a "three-way strategic merge patch" which merges updates to the objects from the Helm chart, with changes that have been made external to Helm: https://helm.sh/docs/faq/changes_since_helm2/#improved-upgrade-strategy-3-way-strategic-merge-patches

--force tells helm to "replace" objects upon upgrade without this merging.