Skip to content
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

Support for MongoDB secured connection #108

Closed
maximilianb28 opened this issue Oct 7, 2023 · 3 comments
Closed

Support for MongoDB secured connection #108

maximilianb28 opened this issue Oct 7, 2023 · 3 comments

Comments

@maximilianb28
Copy link

maximilianb28 commented Oct 7, 2023

Reason/Context

At this moment, the operator does not support ssl based connections to MongoDB

Description

It would be good to have a support for providing SSL certificates when the MongoDB server is configured to only allow SSL connections. There is no way to provide a SSL certificate with the current configuration.

Implementation ideas

The idea would be to pass the certificates in secrets as described below.

mongodb:
  install: false
  uri: mongodb-svc:27017
  database: mongodb
  ssl:
    enabled: true
    certificateSecret: tls-certificate
    certificateAuthoritySecret: tls-ca-key-pair
@lbroudoux
Copy link
Member

Hey!

Thanks for opening this issue. This is a good suggestion as it is asked by many different users for the Operator and for the Helm chart. I think we'll not be able to include this into the next 1.8.0 release that should land next week but I propose to include it just after in the 1.8.1. It will also be pushed on a nightly image as soon as committed.

What's your timeframe on this one? Any urgency?

@maximilianb28
Copy link
Author

Thanks for the quick response.

We are in some kind of hurry. We were looking for something before mid November. The nightly image would be wonderful for testing purposes as well. As long as this can be fully addressed in the future, we should be fine. Thanks again for taking this into consideration.

Copy link

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

@github-actions github-actions bot added the stale State due to inactivity label Sep 21, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants