problem description:
Current CRD installation, controller installation etc of Kruise is all in one chart.
So if I have to helm delete kruise for whatever reason (say to start clean and start from scratch, or any other reason), the helm delete will delete the CRDs. And kubernetes without CRD definition will garbage collect and delete all the CRD resources created in various namespaces. This means if I helm delete kruise, all the CRD resources will instantly get deleted as well which is disastrous because I lose all the CRD resources .
The one way I think to address this issue is to create a seperate helm chart for just installing crds and another helm chart for rest (deployment, daemon set etc)
problem description: Current CRD installation, controller installation etc of Kruise is all in one chart. So if I have to helm delete kruise for whatever reason (say to start clean and start from scratch, or any other reason), the helm delete will delete the CRDs. And kubernetes without CRD definition will garbage collect and delete all the CRD resources created in various namespaces. This means if I helm delete kruise, all the CRD resources will instantly get deleted as well which is disastrous because I lose all the CRD resources . The one way I think to address this issue is to create a seperate helm chart for just installing crds and another helm chart for rest (deployment, daemon set etc)