Navigation

MongoDB Enterprise Kubernetes Operator Helm Installation Settings

To provide optional settings, edit the Helm values YAML file that corresponds to your deployment type in the directory where you cloned the Kubernetes Operator repository:

  • Vanilla Kubernetes: helm_chart/values.yaml
  • OpenShift: helm_chart/values-openshift.yaml

If the setting that you want to add doesn’t exist in the values YAML file, add its key and value:

Example

registry:
  appDb: quay.io/mongodb

Tip

Alternatively, you can pass these values as options when you apply the Helm Chart:

helm upgrade <chart-name> helm_chart \
     --values helm_chart/values.yaml \
     --set namespace=<testNamespace>
helm upgrade <chart-name> helm_chart \
     --values helm_chart/values-openshift.yaml \
     --set namespace=<testNamespace>

managedSecurityContext

Flag that determines whether or not the Kubernetes Operator inherits the securityContext settings that your Kubernetes cluster manages.

This value must be true if you want to run the Kubernetes Operator in OpenShift or in a restrictive environment.

The default value is false.

Example

# Set this to true if your cluster is managing SecurityContext for you.
# If running OpenShift (Cloud, Minishift, etc.), set this to true.
managedSecurityContext: false

The default value is true.

Example

# Set this to true if your cluster is managing SecurityContext for you.
# If running OpenShift (Cloud, Minishift, etc.), set this to true.
managedSecurityContext: true

namespace

namespaces in which you want to deploy the Kubernetes Operator.

To use a namespace other than the default, specify the namespace in which you want to deploy the Kubernetes Operator.

The default value is mongodb.

Example

# Name of the Namespace to use
namespace: mongodb

operator.env

Label for the Kubernetes Operators deployment environment. This value affects the default timeouts and the logging level and format:

If the value is Log Level is set to Log Format is set to
dev debug text
prod info json

The default value is prod.

Example

operator:
  # Execution environment for the operator, dev or prod.
  # Use dev for more verbose logging
  env: prod

operator.watchNamespace

Namespace that the Kubernetes Operator watches for MongoDB Kubernetes resource changes. If this namespace differs from the default, ensure that the Operator’s ServiceAccount can access this namespace.

Use * to specify all namespaces. To watch all namespaces, you must also assign the ClusterRole to the mongodb-enterprise-operator ServiceAccount, which is the ServiceAccount used to run the Kubernetes Operator.

Important

To deploy Ops Manager and MongoDB Kubernetes resources in a namespace other than the one where you deploy the Kubernetes Operator, see Kubernetes Operator Deployment Scopes for values you must use and additional steps you might have to perform.

The default value is <metadata.namespace>.

Example

operator:
  watchNamespace: *

operator.watchedResources

Custom resources that the Kubernetes Operator watches.

The Kubernetes Operator installs the CustomResourceDefinitions for and watches only the resources you specify.

The Kubernetes Operator accepts the following values:

Value Description
mongodb Install the CustomResourceDefinitions for and watch database resources.
mongodbusers Install the CustomResourceDefinitions for and watch MongoDB user resources.
opsmanagers Install the CustomResourceDefinitions for and watch Ops Manager resources.

Example

operator:
  watchedResources:
    - mongodbusers
    - mongodb
    - opsmanagers

registry.appDb

URL of the repository from which the Kubernetes Operator downloads the Application Database image.

The default value is quay.io/mongodb.

Example

registry:
  appDb: quay.io/mongodb

The default value is registry.connect.redhat.com/mongodb.

Example

registry:
  appDb: registry.connect.redhat.com/mongodb

registry.imagePullSecrets

secret that contains the credentials required to pull images from the repository.

Important

OpenShift requires this setting. Define it in this file or pass it when you install the Kubernetes Operator using Helm.

Example

registry:
# The pull secret must be specified
  imagePullSecrets: <openshift-pull-secret>

registry.initAppDb

URL of the repository from which the initContainer image that contains the Application Database start-up scripts and the readiness probe is downloaded.

The default value is quay.io/mongodb.

Example

registry:
  initAppDb: quay.io/mongodb

The default value is registry.connect.redhat.com/mongodb.

Example

registry:
  initAppDb: registry.connect.redhat.com/mongodb

registry.initOpsManager

URL of the repository from which the initContainer image that contains the Ops Manager start-up scripts and the readiness probe is downloaded.

The default value is quay.io/mongodb.

Example

registry:
  initOpsManager: quay.io/mongodb

The default value is registry.connect.redhat.com/mongodb.

Example

registry:
  initOpsManager: registry.connect.redhat.com/mongodb

registry.operator

Repository from which the Kubernetes Operator image is pulled. Specify this value if you want to pull the Kubernetes Operator image from a private repository.

The default value is quay.io/mongodb.

Example

registry:
  operator: quay.io/mongodb

The default value is registry.connect.redhat.com/mongodb.

Example

registry:
  operator: registry.connect.redhat.com/mongodb

registry.opsManager

URL of the repository from which the image for an Ops Manager resource is downloaded.

The default value is quay.io/mongodb.

Example

registry:
  opsManager: quay.io/mongodb

The default value is registry.connect.redhat.com/mongodb.

Example

registry:
  opsManager: registry.connect.redhat.com/mongodb