Skip to content

MongoDB Community Operator (self-managed)

This page describes how to install a Customer Application

You are solely responsible for Customer Applications.

If you are an Elastisys Managed Services customer, please review your responsibilities in ToS 5.2.

Specifically, you are responsible for performing due diligence for the project discussed in this page. At the very least, you must:

  • assess project ownership, governance and licensing;
  • assess project roadmap and future suitability;
  • assess project compatibility with your use-case;
  • assess business continuity, i.e., what will you do if the project is abandoned;
  • subscribe to security advisories related to the project;
  • apply security patches and updates, as needed;
  • regularly test disaster recovery.

This page is a preview for self-managed cluster-wide resources

Compliant Kubernetes restricts application developers to manage CustomResourceDefinitions (CRDs) and other cluster-wide resources for security purposes. This means that some applications that require such cluster-wide resources are not possible to install for you as an application developer. As a trade-off, we are launching this preview feature that allows for self-management of specific cluster-wide resources required for certain popular applications. It is disabled by default, so please ask your platform administrator to enable this preview feature.

For Elastisys Managed Services Customers

You can ask for this feature to be enabled by filing a service ticket. This is a preview feature. For more information, please read ToS 9.1 Preview Features.

This page will help you to install MongoDB Community Operator, so that you are allowed to install the cluster-wide resources that are required by MongoDB.

This guide is a complement to the MongoDB Community Operator's own documentation.


The self-managed cluster-wide resources feature adds specific Roles, ServiceAccounts, etc. for you. This enables you to install and manage the resources that the MongoDB Community Operator needs. These pre-installed resources are propagated via HNC from your root Namespace (recall the documentation of this feature).

First create a new Namespace using HNC, using the snippet below. If you do not know which root namespace you should use, ask your platform administrator.

kind: SubnamespaceAnchor
  name: mongodb
  namespace: <root namespace>

Install MongoDB Community Operator

Supported versions

This installation guide has been tested with MongoDB Community Operator version 0.8.3.

Please follow the official documentation for the MongoDB Community Operator. Be sure to read through the documentation fully.

If default configuration choices are to your liking, you should be able to install the MongoDB Community Operator as follows:

helm repo add mongodb
helm upgrade --install community-operator mongodb/community-operator --namespace mongodb --version 0.8.3

Further Reading

Please refer to the official documentation how to operate and connect to MongoDB.