# Mount Additional ConfigMaps/Secrets

Optional ConfigMaps and/or Secrets can be mounted to all pods in the deployed SingleStore cluster. These can be mounted on a per-cluster basis, or, in the case of ConfigMaps, mounted to all SingleStore clusters in the same Kubernetes namespace.

A ConfigMap or Secret will be mounted automatically (which may take a minute or two) when created as per the following instructions.

## Mount a ConfigMap to a Cluster

When a ConfigMap is created with the name `<cluster-name>-additional-files`, the ConfigMap will be mounted automatically on `/etc/memsql/extra` for all pods in the cluster.

## Mount a Secret to a Cluster

When a Secret is created with the name `<cluster-name>-additional-secrets`, the Secret will be mounted automatically on `/etc/memsql/extra-secret` for all pods in the cluster.

## Mount a ConfigMap to All Clusters in the Same Kubernetes Namespace

When a ConfigMap is created with the name `global-additional-files`, the ConfigMap will be mounted automatically on `/etc/memsql/share` for all pods in the cluster within the same Kubernetes namespace.

***

Modified at: July 5, 2022

Source: [/db/v9.1/reference/singlestore-operator-reference/mount-additional-configmaps-secrets/](https://docs.singlestore.com/db/v9.1/reference/singlestore-operator-reference/mount-additional-configmaps-secrets/)

(An index of the documentation is available at /llms.txt)
