You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in the comment helm doesn't handle CRD upgrades well, so we either need to document or improve how helm handle the CRDs. As the comment here suggests we can simply move our CRD to templates directory to make this work but it needs to be tested and investigated.
Seems like CRD with helm charts are indeed complicated [1][2] but I also think our use-case is simple (w/o CRs, using ConfigMaps in future) so I will propose to move forward:
Move the charts to from crds to templates directory with an option skipCRDs (default: false) simplifying upgrades.
Document the workflow to use skipCRDs=false with kubectl apply ..., similar to cert-manager docs. in case user want to be careful with CRs.
Document the uninstall section with CRs removal to ensure we don't run into finalizers issue.
As mentioned in the comment helm doesn't handle CRD upgrades well, so we either need to document or improve how helm handle the CRDs. As the comment here suggests we can simply move our CRD to templates directory to make this work but it needs to be tested and investigated.
According to helm/helm#8668 (comment):
The text was updated successfully, but these errors were encountered: