Replies: 4 comments 14 replies
-
I don't know if that is the only issue, but having |
Beta Was this translation helpful? Give feedback.
-
Thanks Jakub, I was playing with this (and other) settings and found that when I enable
And thats the only thing in the log |
Beta Was this translation helpful? Give feedback.
-
Ok, I took your advise and created a Strimzi TLS enabled cluster and checked the topic operator settings. I mounted the joined client certificate and key as a p12 file (instead of JKS) I than saw in the manual that for the I need to use both the Any reason we need the ca.key for? |
Beta Was this translation helpful? Give feedback.
-
UPDATE I did some reverse engineering on the and found out I need to add the following flags to prevent the tls side car from being used:
when I did that it seems that the topic operator finally connects to my cluster! Now im getting the following error:
Any tips? feels like im at the finish line :-) |
Beta Was this translation helpful? Give feedback.
-
Hi,
We have a secured cluster (TLS enabled) running outside of Kubernetes.
I would like to provide a tool for our devs to manage topics with and chose the standalone topic operator.
I configured it as seen below but sadly it tries to start but keeps failing showing it is disconnecting from the brokers.
I couldnt figure out why.
My setup:
kafka-keystore.jks - contains a certificate + key combined to a p12 file
kafka-truststore.jks - contains the ca.crt for the domain
both are mounted from a kubernetes secret
the standalone-topic-operator.yaml
The log file:
Is there anything im missing here?
I am able to connect using a client (conducktor)
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions