Kubernetes controller for multi-tenancy. It propagates resources between namespaces accurately and allows tenant users to create/delete sub-namespaces.
This PR is migrating away from the CRD "support" in Helm, making the CRDs regular Helm templates. This is a common workaround for the non-existing CRD support in Helm.
I am proposing to make Helm management of CRDs the default, but cert-manager decided to make it an opt-in. Both approaches have their pros and cons. Let me know what you think!
We don't use Helm in our clusters, but instead use the Helm support in kustomize to template resources client-side. I am not sure how easy it would be to migrate to the new way of managing CRDs with Helm. Maybe you can help me test so we can add some docs?
This PR is migrating away from the CRD "support" in Helm, making the CRDs regular Helm templates. This is a common workaround for the non-existing CRD support in Helm.
Unblocks https://github.com/cybozu-go/accurate/pull/107.
I am proposing to make Helm management of CRDs the default, but cert-manager decided to make it an opt-in. Both approaches have their pros and cons. Let me know what you think!
We don't use Helm in our clusters, but instead use the Helm support in kustomize to template resources client-side. I am not sure how easy it would be to migrate to the new way of managing CRDs with Helm. Maybe you can help me test so we can add some docs?