You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Through the read me, i notice three special param that allowConnectionsWithoutCertificates: true
、allowInvalidHostnames: true、 allowInvalidCertificates: true。
That means sidecar want to connect mongo without using any CAs. But the problem comes when the server security police is very high, and don't allow anyone without CA to access.
So if there any solutions like we can mount all the CA in mongo container in a special path and with a special name. Or just mount it to sidecar. Anyway, make sure that sidecar can use correct CAs to run commend .e.g.
Through the read me, i notice three special param that allowConnectionsWithoutCertificates: true
、allowInvalidHostnames: true、 allowInvalidCertificates: true。
That means sidecar want to connect mongo without using any CAs. But the problem comes when the server security police is very high, and don't allow anyone without CA to access.
So if there any solutions like we can mount all the CA in mongo container in a special path and with a special name. Or just mount it to sidecar. Anyway, make sure that sidecar can use correct CAs to run commend .e.g.
mongo --host localhost:27017 --ssl --sslPEMKeyFile /xxx --sslCAFile /xxx --sslAllowInvalidHostnames
The text was updated successfully, but these errors were encountered: