Giters

mongodb / mongodb-kubernetes-operator

MongoDB Community Kubernetes Operator

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Connectivity and Authentication Issues with MongoDB Community Operator (v0.8.2) in ReplicaSet Configuration

shradha-doru opened this issue · comments

commented

Description:

Issue Overview:
I am encountering connectivity and authentication issues while using MongoDB Community Operator version 0.8.2 with a MongoDB ReplicaSet configuration of version 6.0.8. This issue seems to be related to the setup of hostnames via the service file created by the operator, and there are also problems with logging into the MongoDB shell.

Steps to Reproduce:

  1. Deploy MongoDB Community Operator version 0.8.2.
  2. Configure a MongoDB ReplicaSet of version 6.0.8.
  3. Observe that the MongoDB pods are not establishing connectivity due to conflicting hostnames set up by the service file created by the operator.

Details:

Connectivity Issue:
The MongoDB pods are unable to establish connectivity between each other due to differing hostnames set up by the service file, which is generated by the operator itself. These hostnames cannot be overridden manually. An attempt was made to utilize the connectionStringSecretName field, which is intended to point to an alternate secret file containing the required hostnames. Unfortunately, this approach did not resolve the issue.

Authentication Issue:
Additionally, there is an authentication problem when trying to access the MongoDB shell. Upon using the mongosh --host command, the following error is encountered: MongoServerError: Received authentication for mechanism SCRAM-SHA-1 which is not enabled.

Expected Behavior:

  1. The MongoDB pods should be able to establish connectivity with one another using the provided hostnames.
  2. The connectionStringSecretName field should successfully override the conflicting hostnames.
  3. The authentication mechanism SCRAM-SHA-1 should be enabled to allow successful authentication.

Environment:

  • MongoDB Community Operator version: 0.8.2
  • MongoDB ReplicaSet version: 6.0.8

Additional Information:

  • Screenshots of any relevant configurations or errors encountered.
  • Logs or error messages related to the connectivity and authentication issues.
  • Any troubleshooting steps that have been attempted before submitting this issue.

Note:
I have searched the repository's existing issues and documentation, but I did not find a similar problem reported. If this issue has already been addressed or discussed, please provide a link to that discussion.

I appreciate your assistance in resolving these connectivity and authentication issues. Please let me know if any further information is needed to diagnose and address these problems effectively. Thank you for your time and support.

commented

This issue is being marked stale because it has been open for 60 days with no activity. Please comment if this issue is still affecting you. If there is no change, this issue will be closed in 30 days.

commented

This issue was closed because it became stale and did not receive further updates. If the issue is still affecting you, please re-open it, or file a fresh Issue with updated information.