---
title: "Kubernetes Deployment FAQ"
slug: "kubernetes-deployment-faq"
updated: 2026-10-21T15:42:31Z
published: 2026-10-21T15:42:31Z
canonical: "docs.rocket.chat/kubernetes-deployment-faq"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Kubernetes Deployment FAQ

****Why is my MongoDB operator pod failing to start?****

The MongoDB operator deploys and manages your replica set. If the operator is not running, the replica set is not deployed. Common causes are insufficient RBAC permissions and failures pulling the operator image from the registry.

To debug, check the logs and inspect the deployment with these commands:

```bash
kubectl logs deployment/mongodb-kubernetes-operator -n rocketchat
kubectl describe deployment mongodb-kubernetes-operator -n rocketchat
```

****Why is my MongoDB pod failing to start?****

To find the cause, run these checks:

1. Check the MongoDB operator logs:

```bash
kubectl logs deployment/mongodb-kubernetes-operator -n rocketchat
```
2. Check the MongoDB pod logs:

```bash
kubectl logs mongodb-0 -n rocketchat
```
3. Verify that the persistent volumes have enough space:

```bash
kubectl get pvc -n rocketchat
```
4. Check whether the MongoDBCommunity resource reports errors:

```bash
kubectl describe mongodbcommunity mongodb -n rocketchat
```

****The** `mongodb-svc` **exists, but has no endpoints. Why?****

If the endpoints are empty, the selector on the service doesn't match the labels on the pods. The MongoDB Kubernetes operator manages service selectors and pod labels automatically. If you encounter this issue, verify that you haven't overridden the `serviceName`, `selector`, or template labels in the `statefulSet` spec.

To verify:

```bash
kubectl get svc mongodb-svc -n rocketchat -o yaml | grep selector -A 5
kubectl get pod mongodb-0 -n rocketchat -o yaml | grep labels -A 5
```

The selector values in the service must match the labels on the pod.

****Why can’t Rocket.Chat connect to MongoDB?****

If Rocket.Chat can’t connect to MongoDB, run these checks:

1. Verify that MongoDB is running:

```bash
kubectl get pods -n rocketchat | grep mongodb
```
2. Test the connection string manually. Replace `<password>` with the password of the `rocketchat` database user:

```bash
kubectl run -it --rm debug --image=mongo:8.2.3 --restart=Never -n rocketchat -- mongosh "mongodb://rocketchat:<password>@mongodb-0.mongodb-svc.rocketchat.svc.cluster.local:27017/rocketchat?authSource=rocketchat"
```
3. Check the Rocket.Chat logs for connection errors:

```bash
kubectl logs <rocketchat-pod-name> -n rocketchat
```
4. Verify that the MongoDB service is accessible:

```bash
kubectl get svc -n rocketchat | grep mongodb
```
5. Confirm that the MongoDB service endpoints exist:

```bash
kubectl get endpoints mongodb-svc -n rocketchat
```

****My old Bitnami MongoDB pod is still running after the upgrade. Should I delete it?****

The Helm upgrade usually removes it, but legacy persistent volume claims (PVCs) can remain. If the old Bitnami MongoDB pod is still running:

1. Verify that your data is in the new MongoDB instance.
2. Look for orphaned volumes:

```bash
kubectl get pvc -n rocketchat
```
3. After you confirm the migration succeeded, delete the old PVCs manually.

> [!CAUTION]
> Deleting a PVC permanently removes the data on it. Confirm that the new MongoDB instance has all your data first.