Replies: 1 comment 2 replies
-
This is not a bug. You are mixing two completely different things - using custom Cluster and Client CAs ... and using a custom listener certificate. Please check the docs to understand the difference and how to use one or the other. |
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
-
Bug Description
Hello !
I am deploying Strimzi Kafka (version 0.39.0) with Kafka 3.6.0 and I want to use an external Certificate Authority (CA) managed by Cert-Manager instead of Strimzi’s self-signed CA.
I disabled Strimzi’s built-in CA by setting:
I manually created TLS certificates using Cert-Manager and provided the secret (wildcard-mycompany-com-tls) to Kafka:
When deploying Kafka, Strimzi fails with the following error:
.strimzi.operator.common.model.InvalidResourceException: Cluster CA should not be generated, but the secrets were not found.
This indicates that Strimzi is expecting the Cluster CA and Clients CA secrets, but they are missing.
However, I am providing my own TLS certificates via Cert-Manager, so I do not want Strimzi to generate these secrets.
Steps to reproduce
No response
Expected behavior
Strimzi running with cert-manager certificate and external-clients able to connect to it.
Strimzi version
0.39.0
Kubernetes version
1.26.7
Installation method
Helm chart
Infrastructure
Baremetal
Configuration files and logs
No response
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions