Replies: 2 comments 1 reply
-
i tried the env MESSAGING_DOMAIN_NAME But looks like it can not resolve the host, will we add some dns confguration ? |
Beta Was this translation helpful? Give feedback.
0 replies
-
it can work with the following configuration, is it expected solution? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi expert,
I'm using messaging-topology-operator to manage the user, exchange, binding...etc.
And I also configured the tls for the rabbitmq-cluser, according to the docs, we need add SAN when generate secret:
In our solution, cert-manger with Let's Encrypt is used to manage the secret. But it only supports regular DNS domain name (cannot support the format like servicename.mynamespace.svc.cluster.local).
The error is as following with the secret generated by Let's Encrypt
Would we have a way to disable the authentication for messaging-topology-operator? Or do you have any other suggestion?
By the way, it can work well with the secret generated by tl-geen(the tool provided by rabbitmq)
Beta Was this translation helpful? Give feedback.
All reactions