Replies: 1 comment 2 replies
-
Before opening a new issue, please make sure you:
If you did the first, you would know that you could use your own CA certificates already. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Related problem
Currently the operator is generating a CA to secure communication across brokers
Operator is generating clusterCA certificate and clientsCA certificate
Suggested solution
Introduce an ability in the operator Chart
values.yaml
to take a custom CA generate by the user which be used to generate certificates for brokers within the cluster or for clientsBasically, as a user, I am going to generate a root CA and going to provide it to the operator for it to use it and generate certificates for its managed components.
Also, certificates should renewed every while based on the same CA
One of use cases, I am going to sign a CSR for a client and allow it to use his certificate to authenticate to KAFKA cluster
Alternatives
Basic way to prevent auto-generation of CA and scope auto-renewal to the certificate themselves
Currently its being done by suspending reconciliation of operator, change root CA in secrets and resume reconciliation.
I haven't tested yet, but I saw a person who did it that way
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions