When an upgrade is performed via Helm and when we update the custom resource definition via kubectl, it creates the following conflicts:

This is likely because the Helm chart has installed the CRD, and to upgrade the chart, we need to execute commands using kubectl. So, there are two managers for the resource.
Maybe the documentation should add the --force-conflicts parameter in the following command when the helm upgrade happens:

Reference URL: