# ConfigMap

Very similarly to the [PeristentVolumeClaim module](/acorn-0.12/kubernetes-plugins/module-types/persistentvolumeclaim.md), you can also mount Kubernetes ConfigMaps on `container` modules using the `configmap` module type ([see here for the full reference](/acorn-0.12/reference/module-types/configmap.md)).

Example:

```yaml
kind: Module
name: my-configmap
type: configmap
data:
  config.properties: |
    some: data
    or: something
---
kind: Module
name: my-module
type: container
services:
  - name: my-service
    volumes:
      - name: my-configmap
        module: my-configmap
        containerPath: /config
    ...
```

This mounts all the keys in the `data` field on the `my-configmap` module under the `/config` directory in the container. In this case, you'll find the file `/config/config.properties` there, with the value above (`some: data ...`) as the file contents.

You can do the same for tests and tasks using the [`tests.volumes`](/acorn-0.12/reference/module-types/container.md#testsvolumes) and [`tasks.volumes`](/acorn-0.12/reference/module-types/container.md#tasksvolumes) fields. `configmap` volumes can of course also be referenced in `kubernetes` and `helm` modules, since they are deployed as standard ConfigMap resources.

Take a look at the [`configmap` module type](/acorn-0.12/reference/module-types/configmap.md) and [`container` module](/acorn-0.12/reference/module-types/container.md#servicesvolumes) docs for more details.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.garden.io/acorn-0.12/kubernetes-plugins/module-types/configmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.