Replies: 3 comments 3 replies
-
Hi @benmoss, I'm going to convert this issue to a github discussion because it seems to be more of a question 😄 |
Beta Was this translation helpful? Give feedback.
-
Hi @benmoss, we have release manifest that does not depend on cert-manager. In our release artifact, the manifest with name suffix In our installation docs, we have a dedicated section about generated certs use case in Install with Generated Certificates. This installation doc is linked in the repo README. I love to learn from you about your feedback to these docs and any suggestions on how to make them more visible. |
Beta Was this translation helpful? Give feedback.
-
It has become even more relevant since 1.6 was released of cert manager which removed a bunch of long time deprecated APIs that are still in use by many tools unfortunately |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
As an operator I'd prefer not to have to install cert-manager if I'm not trying to do anything fancy with certificate management.
Describe the solution you'd like
A documented way for users to bring their own certificates, but not necessarily via cert-manager.
Additional context
Strimzi is a comparable operator for managing Kafka clusters. They do not have a dependency on cert-manager and this is their documentation for how to manage your own certificates.
It seems like it automatically can provision its own certificates, but in the case of bring-your-own it just expects the user to provide Kubernetes secrets containing the certificates and keys. A user could use cert-manager to create these and still get the benefits of cert-manager, or whatever certificate management system they want.
Beta Was this translation helpful? Give feedback.
All reactions