CRD update process for new version of the Operators

Hey Stackable team

I have encountered the issue which seems to a common one regarding CRDs and how to handle the versioning/updates of them.

As helm seems to taken a defensive stance on the matter, I think it would be good to have sections dedicated to logging changes and instruction on, how to update already existing CRDs in your cluster.

The purpose of these docs would be to reduce the risk of a customer not being aware of the procedure there is around CRD and potentially safeguard them against force updating the CRD. Updating the CRDs without the proper procedure could result in objects being wiped as a side effect.

Inizia individuando la documentazione esistente relativa a CRDs, deployment Helm e aggiornamenti di versione dell’operatore; l’issue non indica file o test specifici. Documenta come devono essere registrate le modifiche ai CRDs e come aggiornare in sicurezza i CRDs esistenti senza forzarne l’aggiornamento. Il lavoro è completato quando i clienti possono trovare una procedura chiara e consapevole della versione e comprendere il rischio di perdita dei dati.