OpenShift中跨Pod访问MongoDB连接失败求助

Let's break down your problem and walk through actionable fixes step by step:

First, that browser error when accessing the MongoDB Route is totally expected—MongoDB uses a native TCP protocol, not HTTP, so hitting it with a browser will always throw that message. We can ignore that and focus on the inter-Pod connection issue.

1. Use the Cluster Service Name in Your Connection String #

Your MongoDB Service is of type ClusterIP, which means it's only accessible within the OpenShift cluster. Instead of using the Route's host (designed for HTTP traffic), use the Service name mongodb as the host in your Mongoose connection string:

mongoose.connect('mongodb://[username]:[password]@mongodb:27017/[dbname]');

OpenShift's internal DNS automatically resolves mongodb to the Service's ClusterIP, so this works for any Pod in the same namespace. If your Node.js app is in a different namespace, use mongodb.[your-namespace].svc.cluster.local instead.

2. Verify MongoDB is Listening on All Interfaces #

Red Hat's MongoDB image should configure bindIp: 0.0.0.0 by default (to allow external container connections), but let's confirm:

• SSH into your MongoDB Pod:

  oc rsh <mongodb-pod-name>
  

• Check the mongod config:

  cat /etc/mongod.conf | grep bindIp
  

If it shows 127.0.0.1, add an environment variable to your Deployment Config's container spec to override this:

env:
  - name: MONGODB_CONFIG_OPTIONS
    value: "--bind_ip_all"

This forces MongoDB to listen on all network interfaces, enabling connections from other Pods.

3. Validate User Permissions and Database Existence #

Ensure your MONGODB_USER has the correct permissions to access MONGODB_DATABASE:

• Inside the MongoDB Pod, run:

  mongo -u $MONGODB_USER -p $MONGODB_PASSWORD $MONGODB_DATABASE
  

If this fails, log in as the admin user to grant permissions:

mongo -u admin -p $MONGODB_ADMIN_PASSWORD admin

Then execute this MongoDB command:

db.grantRolesToUser("$MONGODB_USER", [{ role: "readWrite", db: "$MONGODB_DATABASE" }])

4. Check for Network Policies Blocking Traffic #

If Network Policies are enabled in your cluster, they might be blocking traffic between your Node.js Pod and MongoDB Service. List existing policies:

oc get networkpolicy

If there's a policy restricting access to MongoDB, update it to allow traffic from your Node.js app's namespace or Pod labels. For example:

apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: allow-mongodb-access
spec:
  podSelector:
    matchLabels:
      name: mongodb
  ingress:
  - from:
    - podSelector:
        matchLabels:
          app: your-nodejs-app-label
    ports:
    - protocol: TCP
      port: 27017

5. Test Connectivity from the Node.js Pod #

Narrow down the issue with these quick tests from your Node.js Pod:

• Resolve the MongoDB Service:

  nslookup mongodb
  

  You should see the Service's ClusterIP in the output.
• Test port accessibility:

  telnet mongodb 27017
  

  If this connects, the network path is good—your issue is likely with the connection string or user permissions. If it fails, revisit Network Policies and Service configuration.

After making any changes, restart your MongoDB Deployment to apply updates:

oc rollout latest mongodb

内容的提问来源于stack exchange，提问作者relief.melone