Closed jonathansick closed 1 year ago
Please be aware that there is no release of the Kafka Access Operator yet and it is still work in progress. So not everything is working and bug and missing features are to be expected.
No worries at all. Thanks again!
I'm giving the strimzi-access-operator a spin, running it on an image I built from the current main branch. I successfully got a secret generated from a KafkaAccess, and although it has info like
bootstrapServers
andsecurityProtocol
, the Secret is missing the TLS certs I'd expect for mutual TLS authentication. I was under the impression this was implemented, but if not I totally understand! I can come back later :)If generating the TLS certs is expected, I wonder if I'm not getting the TLS certs because the KafkaAccess is in a different namespace than the KafkaUser? Perhaps as a security default? One of my usecases for KafkaAccess to make it easier to run Kafka client in their own namespaces, while also using mutual-TLS for all producer/consumers.
Thanks for this project and Strimzi!
Below are the relevant Kubernetes resources
The KafkaAccess resource:
Here's the
squarebot-kafka
Secret:The value of
securityProtocol
isSSL
, which I expect.Here's the KafkaUser, which authenticates with TLS:
And here's the Kafka resource: