Configuration settings catalog

Here is a catalog of the settings to use when configuring and managing Mission Control.

Topology configuration

Configure the deployment mode for Mission Control.

Name Type Default Value Description

control plane

Boolean

TRUE

Specifies whether to deploy Mission Control in control plane mode rather than data plane mode.

Ingress configuration

Configure ingress settings for platform services access.

Name Type Default Value Description

ingress.enabled

Boolean

FALSE

Enables ingress for all platform services (Mission Control UI, Grafana, and Vector aggregator). When enabled, the system creates Ingress objects for unified access through domain-based routing.

ingress.regionDomain

string

Primary domain for Mission Control UI access (for example, mc.example.com). The system uses this domain to create the main ingress endpoint for the UI.

ingress.wildcardDomain

string

Wildcard domain for service subdomains (for example, *.mc.example.com). The system uses this domain to create ingress endpoints for Grafana (grafana.mc.example.com) and Vector aggregator (vector.mc.example.com).

When you enable ingress, the system automatically creates a ConfigMap named mission-control-ingress-config containing the domain configuration. Operators can read this configuration at runtime for dynamic ingress management.

For OpenShift environments, the system automatically creates Route objects instead of standard Ingress objects, with proper SSL passthrough configuration.

Observability

The following settings configure observability components for monitoring and logging.

Advanced

Configure advanced settings for the monitoring component deployment in the control plane.

Name Type Default Value Description

Allow the monitoring process to run on the control plane

Boolean

Allows the deployment of monitoring components on the Kubernetes control plane. Only required in constrained environments where the control plane is tainted but should host these components.

Allow monitoring components on DataStax Enterprise (DSE) nodes

Boolean

Whether to deploy monitoring components, such as Vector, Mimir, and Loki, on database worker nodes. Only enable this for constrained environments.

Storage backend

Configure the object storage backend for the observability stack.

Name Type Default Value Description

Storage backend

string

Specifies which object storage backend to use for the observability stack (Mimir and Loki).

Accepted values are S3 or GCS.

Region

string

us-east-1

Region where the bucket is located.

Access Key ID

string

AWS access key ID.

Secret Access Key

Password

AWS secret access key.

Bucket endpoint URL

string

URL to reach the S3 compatible object storage service.

Observability Bucket Insecure Access

Boolean

TRUE

Controls whether calls made to the storage backend use TLS. Disable only when your storage backend does not support HTTPS.

GCS storage

Configure Google Cloud Storage (GCS) service account credentials.

Name Type Default Value Description

Service Account

Password

Key file content for the service account accessing the GCS buckets storing Mimir and Loki data. JSON format expected.

Mimir topology

Configure Mimir topology and replication settings.

Name Type Default Value Description

Tune Mimir Topology

Boolean

Change the replication factor and the number of replicas for each Mimir component.

Number of Ingester instances

number

1

Must be 1 or more.

Number of Distributor instances

number

1

Must be 1 or more.

Number of Querier instances

number

1

Must be 1 or more.

Number of Query Frontend instances

number

1

Must be 1 or more.

Number of Ruler instances

number

1

Must be 1 or more.

Number of Alert Manager instances

number

2

Must be 2 or more. A minimum of 2 instances are required for the alertmanager component.

Number of Store Gateway instances

number

1

Must be 1 or more.

Number of Query Scheduler instances

number

1

Must be 1 or more.

Ingester replication factor

number

1

Must be 1 or more.

Alert manager replication factor

number

2

Must be 2 or more. Mimir cannot handle a replication factor of 1 for the alertmanager component.

Mimir resources

Configure CPU and memory resource allocation for Mimir microservices.

Name Type Default Value Description

CPU Requests

100m

Minimum available CPU cores requested to allow scheduling a Mimir microservice. 100m = 100 millicores = 0.1 core.

CPU Limits

Quantity

This is not a literal or updatable value

Maximum number of cores allocated to a Mimir microservice. In order to maximize resource utilization do not set this value.

Memory Requests

128Mi

Minimum available RAM requested to allow scheduling a Mimir microservice on a worker node.

Memory Limits

2Gi

Maximum allowed RAM usage per Mimir microservice. Any service using more than this value is terminated and rescheduled.

Mimir series limits

Configure advanced Mimir settings for series limits.

Name Type Default Value Description

Max Global Series Per User

number

0

The maximum allowed number of series that are accepted per tenant. 0 means unlimited. Mission Control uses a single tenant.

Mimir storage

Configure Mimir storage buckets, retention, and persistent volumes.

Bucket Name Type Default Value Description

Bucket Name

string

Name of the bucket (S3 or GCS) storing Mimir’s metrics data.

Storage retention

string

7d

Set the retention period for metrics data in milliseconds, seconds, hours, days, months, weeks, or years.

The expected format is an integer followed by a time unit in the format Nms Ns Nh Nd Nm Nw Ny.

Unused units can be omitted.

Values can be combined, such as 11m 7d to specify an eleven month and seven day retention period.

Use Persistent Volumes

Boolean

TRUE

Secures data which is local to specific Mimir’s microservices by using persistent storage. Required for production deployments.

Storage Class

Storage Class

The default for the Kubernetes cluster

When using your own Kubernetes cluster, set this to one of your available storage classes that allows dynamic provisioning.

Accepted values are all storage classes available in your Kubernetes cluster.

Access Modes

string

ReadWriteOnce

Set to ReadWriteOnce to allow a single node with multiple pods simultaneous access to the volume mount in read or write mode.

Alert Manager Volume Size

1Gi

Use 10GB for production deployments.

You cannot modify this size after the initialization of the cluster without deleting the existing Persistent Volumes and statefulsets, which can result in data loss.

Compactor Volume Size

2Gi

Use at least 300GB for production deployments.

You cannot modify this size after the initialization of the cluster without deleting the existing Persistent Volumes and statefulsets, which can result in data loss.

Store Gateway Volume Size

2Gi

Use 50GB for production deployments.

You cannot modify this size after the initialization of the cluster without deleting the existing Persistent Volumes and statefulsets, which can result in data loss.

Ingester Volume Size

Quantity

2Gi

Use at least 100GB for production deployments.

If this resource is too small, metrics aren’t ingested.

You cannot modify this size after the initialization of the cluster without deleting the existing Persistent Volumes and statefulsets, which can result in data loss.

Loki instances

Configure Loki instances and replication settings.

Name Type Default Value Description

Loki Reader Instances

number

1

Loki Writer Instances

number

1

Loki Replication Factor

number

1

The number of ingesters to which Loki forwards writes. This should be less than or equal to the number of write instances.

Loki storage

Configure Loki storage retention, buckets, and persistent volumes.

Name Type Default Value Description

Storage retention

string

7d

Set the retention period for metrics data in milliseconds, seconds, hours, days, months, weeks, or years.

The expected format is an integer followed by a time unit in the format Nms Ns Nh Nd Nm Nw Ny.

Unused units can be omitted.

Values can be combined, such as 11m 7d to specify an eleven month and seven day retention period.

Force Path-Style Addressing

Boolean

FALSE

Forces requests to use AWS S3 path-style addressing, which does not prefix the endpoint URL with the bucket name. This is useful when using S3-compatible storage backends.

Use Persistent Volumes

Boolean

TRUE

Required for production deployments.

Persistent Volumes size

string

10Gi

Use at least 50GB for production deployments.

You cannot modify this size after the initialization of the cluster without deleting the existing Persistent Volumes and statefulsets, which can result in data loss.

Storage Class

Storage Class

The default for your Kubernetes cluster

When using your own Kubernetes cluster, set this to one of your available storage classes that allows dynamic provisioning.

Accepted values are all storage classes available in your Kubernetes cluster.

Chunks Bucket Name

string

Name of the bucket to store the log entries sent to Loki.

Ruler Bucket Name

string

Name of the bucket to store the alerting rules for Loki.

User Interface (UI)

The following settings configure the Mission Control UI.

Admin user

Configure the temporary admin user for initial authentication.

Name Type Default Value Description

Create temporary admin user

Boolean

TRUE

Creates an admin user that authenticates to Mission Control without setting up LDAP or OpenID.

Email

string

admin@example.com

Email address of the admin user.

Password hash

string

The bcrypt hash of the password. On Linux and Unix systems, generate this by running:

echo yourPassword | htpasswd -BinC 10 admin | cut -d: -f2

Username

string

admin

Name of the admin user

Identity provider connector type

Select the authentication connector type for the UI.

Name Type Default Value Description

Dex Connector

string

Defines which connector to be configured for authentication and authorization in Mission Control’s UI.

Can be one of None, LDAP, or OpenID Connect.

LDAP connector

Configure LDAP authentication settings including host, TLS, and user/group mappings.

Name Type Default Value Description

Host

string

Host and optional port of the LDAP server.

No SSL

Boolean

FALSE

Required if the LDAP host is not using TLS (port 389).

This option inherently leaks passwords to anyone on the same network as Mission Control, do not use outside of explorative phases.

Skip TLS verify

Boolean

FALSE

Whether to turn off Transport Layer Security (TLS) certificate verification.

This is not secure, do not use outside of explorative phases.

Start TLS

Boolean

FALSE

When connecting to the server, connect using the ldap:// protocol and then issue a StartTLS command. If unspecified, connections use the ldaps:// protocol.

Root CA

string

A trusted root certificate file content (base64-encoded Privacy Enhanced Mail (PEM) file).

Bind DN

string

The DN to bind with when performing the search. When not provided, the search is performed anonymously.

Bind password

string

The password with which to bind when performing the search. When not provided, the search is performed anonymously.

Username prompt

string

The prompt the user sees when requesting their username. When unspecified, the default is Username.

User base DN

string

BaseDN from which to start the search. It translates to the following query:

(&(objectClass=person)(uid=<username>))

User filter

string

BaseDN from which to start the search. It translates to the following query:

(&(objectClass=person)(uid=<username>))

Username attribute

string

uid

Username attribute used for comparing user entries. This is translated and combined with the other filter as (<attr>=<username>).

User id attribute

string

uid

User email attribute

string

email

User display name attribute

string

uid

Preferred username attribute

Group base DN

string

BaseDN from which to start the search. It translates to the following query:

(&(objectClass=person)(uid=<username>))

Group filter

string

(objectClass=group)

Optional filter to apply when searching the directory.

Group/user matchers

string

- userAttr: uid groupAttr: member

A list of field pairs that matches a user to a group. It adds an additional requirement to the filter that an attribute in the group must match the user’s attribute value.

Expected format: multi-line YAML list of objects with userAttr and groupAttr keys.

Group name attribute

string

name

OIDC connector

Configure OpenID Connect (OIDC) authentication settings including issuer, client credentials, and claims.

Name Type Default Value Description

Issuer URL

string

Canonical URL of the provider, also used for configuration discovery.

This value MUST match the value returned in the provider config discovery.

Client ID

string

Client Secret

Password

Basic auth unsupported

Boolean

FALSE

Some providers require passing client_secret via POST parameters instead of basic auth, despite the OAuth2 RFC discouraging it. Many of these cases are caught internally, but you might need to check this setting.

Scopes

string

  - profile
  - email

List of additional scopes to request in token response. See Full list.

Expected format: multi-line YAML list of strings.

Skip email verified

Boolean

FALSE

Not recommended. Some providers return claims without email_verified when they did not use emails verification in the enrollment process or if they are acting as a proxy for another IDP. An example is AWS Cognito with an upstream SAML IDP. Checking this box forces email_verified to TRUE.

Enable groups

Boolean

FALSE

Not recommended. Groups claims only refresh when the ID token is refreshed; meaning that the regular refresh flow does not update the groups claim. By default the OIDC connector does not allow groups claims. If it is satisfactory to have potentially stale group claims then use this option to enable groups claims through the OIDC connector on a per-connector basis.

Get user info

Boolean

FALSE

When enabled, the OpenID Connector queries the UserInfo endpoint for additional claims. UserInfo claims take priority over claims returned by the IDToken. Use this option when the IDToken does not contain all of the claims requested. See OpenID user information.

User ID key

string

The claim used as user id. Defaults to sub. See full claims list.

Username key

string

The claim used as username.

Defaults to name.

ACR values

string

The Authentication Context Class values within the Authentication Request that the Authorization Server is being requested to process.

Expected format: multi-line YAML list of strings.

Prompt type

string

For offline_access, the prompt parameter is set by default to prompt=consent. However, this is not supported by all OIDC providers; some of them support a different value for prompt, like login or none.

Preferred username claim

string

The claim used as preferred username.

Defaults to preferred_username.

Email claim

string

email

The claim used as email.

Preferred groups claim

string

groups

The claim used as groups.

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2026 | Privacy policy | Terms of use |  Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: Contact IBM