Migrate to Kubernetes Operator

Upgrade to v1.33 of the MongoDB Enterprise Kubernetes Operator.

Scale down the MongoDB Enterprise Kubernetes Operator to 0 replicas.

This prevents both it and Kubernetes Operator from running in parallel.

Perform the following two tasks if you have deployed resources across multiple Kubernetes clusters:

1. Back up the kubectl plug-in binary. This makes it easier for you to reverse the migration to Kubernetes Operator if you encounter problems.

2. Configure the member clusters by either following the multi-cluster setup documentation (ensuring that you use the kubectl plugin from the MongoDB Controllers for Kubernetes Operator release) or manually using Helm templating.

   Important

   Kubernetes Operator's RBACs must be deployed to the member clusters before deploying Kubernetes Operator in step 5. The new RBAC resources begin with mongodb-kubernetes-operator-. You must also ensure that the mongodb-kubernetes-operator-member-list is present on your operator cluster after running the newest version of the kubectl plug-in binary.

Install the Kubernetes Operator CRDs manually.

kubectl apply -f https://raw.githubusercontent.com/mongodb/mongodb-kubernetes/1.0.0/public/crds.yaml

To verify that the CRDs are installed on your Kubernetes cluster, search for the mongodbcommunity CRD:

kubectl get crds | grep mongodbcommunity

Install the new Kubernetes Operator Helm chart.

helm repo add mongodb https://mongodb.github.io/helm-charts && \
helm repo update && \
helm upgrade --install mongodb-kubernetes-operator mongodb/mongodb-kubernetes --namespace <your-namespace>

The Kubernetes Operator reconciler runs and processes the existing custom resources.

Kubernetes Operator applies updated images, ServiceAccounts, and other resources.

Wait for the resources to reconcile (reach the Running phase) and become healthy.

Kubernetes Operator deploys one operator replica by default. If you want to run more than one replica, see https://github.com/mongodb/mongodb-kubernetes/blob/master/public/mongodb-kubernetes.yaml#L263 for details on scaling up the operator.

Remove old assets.

You can now remove the Helm chart for the MongoDB Enterprise Kubernetes Operator, as well as the RBACs on all Kubernetes clusters and any backed-up kubectl plug-in binaries.

If you have deployed resources across multiple Kubernetes clusters, you can now safely remove the mongodb-enterprise from the member clusters and delete your backed-up kubectl plug-in binary.

Delete the existing MongoDB Enterprise Kubernetes Operator Subscription.

Replace <subscription-namespace> and <subscription-name> with the values that correspond to your resource.

kubectl -n <subscription-namespace> delete subscription <subscription-name>

Delete the ClusterServiceVersion (CSV) of the old MongoDB Enterprise Kubernetes Operator.

You can usually find the CSV name by listing the CSVs in the operator's namespace. Replace <operator-namespace> and <csv-name> with the appropriate values.

kubectl -n <operator-namespace> delete csv <csv-name>

Install Kubernetes Operator from a catalog available on your cluster.

Kubernetes Operator is available in Red Hat's certified operators catalog, as well as the operatorhub.io catalog.

kubectl create -f <path-to-bundle>