Replies: 3 comments 2 replies
-
I guess that suggests your TLS passthrough is not really working in the Ingress? As the event suggests it is trying to do TLS termination. The secret is indeed missing in the Ingress resources -> because with TLS passthrough it is not needed since the TLS traffic has to go through ingress into the broker without being decoded in any way. |
Beta Was this translation helpful? Give feedback.
-
well, we are using nginx plus ingress controller and not the open source one. the annotation I need to add is the following: annotations:
nginx.org/ssl-services: "mystrimzi-broker-0" for each broker and for the bootstrap ingress rule |
Beta Was this translation helpful? Give feedback.
-
Thank you very much, I'll try that and update for future reference.
…On Mon, May 29, 2023, 17:16 Jakub Scholz ***@***.***> wrote:
You should be able to set the annotations in the listener configuration ->
see for example here:
https://strimzi.io/docs/operators/latest/full/configuring.html#property-listener-config-annotations-reference
—
Reply to this email directly, view it on GitHub
<#8580 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD2FI2KXJZFWSPD5MTLXJ3TXISVS3ANCNFSM6AAAAAAYS2N7RI>
.
You are receiving this because you authored the thread.Message ID:
<strimzi/strimzi-kafka-operator/repo-discussions/8580/comments/6029749@
github.com>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I am trying to configure my Strimzi external listener to ingress with tls enabled and our own certificate using cert manager.
we need ssl passthrough as well so that the brokers are also tls enabled.
seems like everything is configured properly except that im getting the following errors when I run
command
error:
"TLS termination for host 'strimzi-bootstrap.strimzi-sanity-tests.develop.mydomain.local' requires specifying a TLS secret or configuring a global wildcard TLS secret"
I believe the secret is already configured in my Kafka resource and its pointing to a valid certificate:
also,
i get the following when running :
the ingress role of all brokers is indeed missing the "secretName" key under tls by the way even though it is specified in the kafka resource:
Im trying to understand what am I missing here...
any idea are more than welcome.
thanks
Beta Was this translation helpful? Give feedback.
All reactions