Working example for native MongoDB SRV dns resolution in Kubernetes cluster #31971
Replies: 9 comments 45 replies
-
|
/cc @evanchooly (mongodb), @loicmathieu (mongodb) |
Beta Was this translation helpful? Give feedback.
-
|
/cc @cescoffier |
Beta Was this translation helpful? Give feedback.
-
|
Remove: quarkus.mongodb.native.dns.use-vertx-dns-resolver=true It should now work by default. |
Beta Was this translation helpful? Give feedback.
-
|
You need to configure Atlas to know the IP that will connect to the mongo instance. |
Beta Was this translation helpful? Give feedback.
-
|
doesn't 0.0.0.0/0 means every ip ? am I making something really stupid here ? xD |
Beta Was this translation helpful? Give feedback.
-
|
I don't believe you can use such kind of wildcard. You need the exact ip. |
Beta Was this translation helpful? Give feedback.
-
In non native mode the wildcard works. |
Beta Was this translation helpful? Give feedback.
-
Also, I added the exact ips. |
Beta Was this translation helpful? Give feedback.
-
|
I am testing again with CR1 and I (also) added every host ip from my pods :
Also I don't agree about this issue is about network access. This is the properties I am using now : Is it normal not to find any reference to 8.8.8.8 in the logs ? |
Beta Was this translation helpful? Give feedback.
-
|
Also, in non native mode everything also works ... so again, this is not a network issue ... |
Beta Was this translation helpful? Give feedback.
-
|
@cescoffier
|
Beta Was this translation helpful? Give feedback.
-
|
so the vert.x is disabled only during the "deploying" via kubernetes client, the runtime itself is not impacted ... ok that's strange anyway, the only common point seems to be kubernetes so far since I can reproduce the issue in JVM mode in the kubernetes cluster now ... I am going crazy xD |
Beta Was this translation helpful? Give feedback.
-
|
Sorry things are difficult with Mongo in Kubernetes... Another thing I should mention to try even more to dispell any lingering doubt about the PR above, is the the Mongo Client does not use Vert.x for IO so even if the PR did have effect on runtime (which it doesn't), it would have no effect on Mongo usage. |
Beta Was this translation helpful? Give feedback.
-
|
https://quarkus.io/guides/mongodb states that mongo client may use vert.x for native resolution of srv addresses ... it is also true that I can reproduce the issue in JVM mode too ... |
Beta Was this translation helpful? Give feedback.
-
|
Then I admit I did not know we had such an integration |
Beta Was this translation helpful? Give feedback.
-
|
No, the mongo extension uses the Vert.x DNS client, unrelated to the mentioned PR. It might be due to your DNS configuration on your machine. |
Beta Was this translation helpful? Give feedback.
-
|
I surrender, for the moment I'll switch back to the old url string format, even if this is not good for an autoscaling microservice deployment. Maybe SRV dns resolution fails only in combination with kubernetes environment. Anyway this is not working for me :( I'll try waiting for this to stop being an experimental feature |
Beta Was this translation helpful? Give feedback.
-
|
This is my kubernetes descriptor : |
Beta Was this translation helpful? Give feedback.
-
I just tried from an ubuntu helm chart inside the same kubernetes namespace. From that pod I can resolve SRV addresses and telnet my ports. So you tried with a quarkus application, hosted on two different kubernete environments, and it manages to connect to MongoDB Atlas using SRV records ? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I tried on OpenShift and it worked. |
Beta Was this translation helpful? Give feedback.
-
I can't test on OpenShift atm. This is the current status of my investigation :
(*) Failed looking up SRV record / io.smallrye.mutiny.TimeoutException I feel like I made you waste your time but in my defense this issue seems to be really tricky ... I can give you access on my private repository on github to have a look at the code, if you want. Thank you in advance |
Beta Was this translation helpful? Give feedback.
-
|
Ok, that's interesting! I may have an idea. If you can provide a simple, standalone reproducer, I can have a look. Not for 2 weeks, unfortunately, as I will be preparing talks and giving talks |
Beta Was this translation helpful? Give feedback.
-
|
@amoscatelli @cescoffier I'm curious, did you find any solution to this issue? was it an issue at all? I seem to have similar issues, but in a more constrained environment, so reproduction locally is a difficult issue. It's quarkus in Kubernetes and MongoDB atlas that we are having issues with, but not every time. |
Beta Was this translation helpful? Give feedback.
-
|
Until we find a proper solution to the issue (which is our goal), a temporary workaround is the following: quarkus.naming.enable-jndi=true
quarkus.class-loading.removed-resources."io.quarkus\:quarkus-mongodb-client"=META-INF/services/com.mongodb.spi.dns.DnsClientProviderThis means that JNDI will be enabled (which it's not by default in Quarkus) and the Mongo client will use our Mongo DNS resolver. |
Beta Was this translation helpful? Give feedback.
-
|
Just a note to this, I suppose this is a build-time configuration and that means that the application has to be built for that, right? |
Beta Was this translation helpful? Give feedback.
-
|
Correct, they both are |
Beta Was this translation helpful? Give feedback.
-
|
#43222 should fix this. It will be available in the next 3.15 release. |
Beta Was this translation helpful? Give feedback.
-
Hi guys !
I am trying to enable the experimental support for SRV address in native mongodb without any success.
I tried enabling the following without any success :
quarkus.mongodb.dns.server-host=8.8.8.8
quarkus.mongodb.native.dns.server-host=8.8.8.8
quarkus.mongodb.native.dns.use-vertx-dns-resolver=true
quarkus.naming.enable-jndi=true
The documentation seems a bit confusing about this, even more quarkus complains about some of those properties :
[io.quarkus.config.build] The 'quarkus.mongodb.native.dns.server-host' config property is deprecated and should not be used anymore
[io.quarkus.config.build] The 'quarkus.mongodb.native.dns.use-vertx-dns-resolver' config property is deprecated and should not be used anymore
Can anybody paste a working properties example ?
Thank you in advance
p.s. I am using Alpha4
Beta Was this translation helpful? Give feedback.
All reactions