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
Would it be possible to implement selective CRDs for some of the services that are more commonly deployed to a Kubernetes cluster? Things like cert manager and external DNS.
Both of them require multiple CRDs for configuration storage, but I'm not sure how difficult it would be to implement them as part of the k2d API translator.
The text was updated successfully, but these errors were encountered:
I haven't looked at this properly but from the top of my head this would be pretty hard to implement with the current translation layer - I believe that we'd need to isolate which properties that are available via the CRDs should be translated on a 1 to 1 basis.
It kinda defeats the flexibility that is provided by the CRD concept as it is likely that we won't be able to support all the options without a lot of maintenance and testing.
But I understand the need and I'm open to suggestions on this side.
Would it be possible to implement selective CRDs for some of the services that are more commonly deployed to a Kubernetes cluster? Things like cert manager and external DNS.
Both of them require multiple CRDs for configuration storage, but I'm not sure how difficult it would be to implement them as part of the k2d API translator.
The text was updated successfully, but these errors were encountered: