-
Notifications
You must be signed in to change notification settings - Fork 998
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Version 2.14 - MongoDB Atlas scheme #5760
Comments
Nice catch! Are you willing to open a PR with the fix? |
@JorTurFer I would love to but I'm not sure I have the time, many tasks ahead in my company 😅 |
no worries! Let's see if anyone wants to help here, I'd say that it should be easy |
Hi @JorTurFer I was able to replicate OP error in
|
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh <53863619+Rishikesh01@users.noreply.github.com>
Have opened an pr: #5773 please take a look when you have time :) |
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh Betigeri <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh Betigeri <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh Betigeri <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh Betigeri <53863619+Rishikesh01@users.noreply.github.com>
This commit fixs issue kedacore#5760. where OP was facing problem with +srv schema Signed-off-by: Rishikesh Betigeri <53863619+Rishikesh01@users.noreply.github.com>
Report
I'm trying to use the latest version's feature of MongoDB Atlas scheme support (mongodb+srv), and getting conflicting requirements -
Keda scale-handler requires a port to be given, otherwise it's failing with:
failed to parsing mongoDB metadata, because of missing required field in scaler config: no port given
But if I'm supplying a port, MongoDB driver itself is failing with the following message:
URI with srv must not include a port number
which comes from this piece of code -
keda/vendor/go.mongodb.org/mongo-driver/x/mongo/driver/topology/topology.go
Lines 390 to 403 in c55e306
Expected Behavior
Scaler defined with the
+srv
scheme should not require a port number.Actual Behavior
Scaler defined with the
+srv
scheme requires a port number, even though it conflicts with the driver's requirements.Steps to Reproduce the Problem
Logs from KEDA operator
KEDA Version
2.14.0
Kubernetes Version
None
Platform
Google Cloud
Scaler Details
MongoDB
Anything else?
No response
The text was updated successfully, but these errors were encountered: