> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/changelog/helm-chart/1.2.2.md).

# 1.2.2

2026-05-13

**App version**: 6.4.2

## Multi-tenant Deployments

* **Sensitive config moved out of the ConfigMap** — With `multitenant.enabled: true`, `BROKER_URL`, `BROKER_SERVER_API`, `DB_CONNECTION_URI`, `ELASTIC_URL`, `AUTH_HUB_TOKEN`, `NEWRELIC_LICENSE_KEY`, and `MINIO_ACCESS_KEY`, `MINIO_SECRET_KEY`, and `MINIO_SESSION_TOKEN` are no longer rendered into `appmixer-config`. All workloads load them from the Secret named in `multitenant.secretName` instead.

## Workload Configuration

* **Per-component ServiceAccounts** — `engine.api`, `engine.worker`, `quota`, `backoffice`, and `frontend` each accept a `serviceAccount` block (`create`, `name`, `annotations`), for example for IRSA.
* **Per-component metadata and scheduling** — Each component also accepts `annotations` (Deployment metadata), `tolerations`, and `extraEnvFrom` (extra Secret or ConfigMap sources).
* **Global labels and annotations** — New `commonLabels` (all resources), `podLabels`, and `podAnnotations` (all pod templates).

## Ingress

* **Ingress class** — The Ingress now sets `spec.ingressClassName` from `ingress.className` instead of the deprecated annotation.
* **Existing TLS secret** — With `certManager.enabled: false` and `ingress.tls: true`, the Ingress uses the secret named in `ingress.tlsSecretName`, for example a wildcard certificate.

## Upgrade Notes

* **Deployment selectors changed** — `spec.selector` of all Deployments now includes `app.kubernetes.io/name` and `app.kubernetes.io/instance`. This field is immutable. Before you upgrade from 1.2.1 or older, delete the `engine-api`, `engine-worker`, `backoffice`, `frontend`, and `quota` Deployments, or sync them with Replace.


---

# 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.appmixer.com/changelog/helm-chart/1.2.2.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.
