> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/kubernetes/configs-and-secrets.md).

# Configs and Secrets

ConfigMaps and Kubernetes Secrets for managing configuration and sensitive data.

**ConfigMaps** store non-sensitive configuration data — feature flags, connection strings, application settings — as key-value pairs that workloads can consume as environment variables or mounted files.

**Secrets** store sensitive data such as passwords, API keys, and TLS certificates. Secrets are base64-encoded in Kubernetes and can be consumed by workloads in the same way as ConfigMaps.

## ConfigMaps

| Field         | Description                             |
| ------------- | --------------------------------------- |
| **Name**      | The ConfigMap name                      |
| **Namespace** | The Namespace this ConfigMap belongs to |
| **Data**      | Key-value pairs of configuration data   |

## Secrets

| Field         | Description                                          |
| ------------- | ---------------------------------------------------- |
| **Name**      | The Secret name                                      |
| **Namespace** | The Namespace this Secret belongs to                 |
| **Type**      | The Secret type (e.g. `Opaque`, `kubernetes.io/tls`) |
| **Data**      | Key-value pairs of sensitive data                    |

## Dependencies

ConfigMaps and Secrets require an **Environment** and a **Namespace**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/marketplace-agents/aws-extension/policy-model/kubernetes/configs-and-secrets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
