> 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.3.0.md).

# 1.3.0

2026-08-19

**App version**: 6.4.4

## Secrets Management

* **GitOps-safe secrets** — A new `secrets-init` job (Helm pre-install/pre-upgrade, ArgoCD PreSync) creates the Redis, RabbitMQ, and admin passwords in the cluster. Rendered manifests no longer contain random values, so ArgoCD does not detect drift.
* **Automatic migration** — On upgrade, existing passwords are copied from the old secrets, so credentials are not rotated.
* **Externally managed secrets** — `redis.auth.existingSecret`, `rabbitmq.auth.existingPasswordSecret`, `rabbitmq.auth.existingErlangSecret`, and `userInit.existingSecret` can point to your own secrets, for example ones managed by External Secrets Operator. You can turn off the job with `secretsInit.enabled: false`.
* **Plaintext admin password** — `userInit.password` is now plaintext. The init job hashes it before storing it.
* **Narrower RBAC** — The chart's Role can only `get` the secrets it reads.

## Multi-tenant Deployments

* **Legacy DNS** — `multitenant.keepDns: true` keeps the old `api.` / `my.` / `backoffice.<legacyHost>` hostnames for a migrated tenant. `multitenant.legacyHost` sets the base domain.

## Workloads

* **Graceful shutdown** — Engine API and Engine Worker run Node with `exec`, so it receives SIGTERM. They also wait 5 seconds in `preStop`. `terminationGracePeriodSeconds` is now 70.
* **Configurable startup probes** — New `engine.api.startupProbe` and `engine.worker.startupProbe`. The default `failureThreshold` is now 120, so pods have up to 20 minutes to start.
* **RabbitMQ credentials from the secret** — When `config.BROKER_URL` is not set, `BROKER_URL` is built from the RabbitMQ secret. It is no longer a hard-coded `user:bitnami`.

## Exposure

* **ALB annotations overridable** — The default ALB annotations (scheme, target type, health check path) are merged with `ingress.annotations`, so you can override them.
* **OpenShift Kibana route** — The Kibana route uses `route.baseDomain` instead of a hard-coded host.

## Logging

* **Logstash TLS verification** — Logstash verifies the Elasticsearch certificate against the cluster CA instead of skipping verification.
* **Logstash credentials** — Logstash reads the RabbitMQ password from the RabbitMQ secret. The separate `rabbitmq-logstash-credentials` secret was removed.

## Other Changes

* **`extraDeploy` rendered once** — Fixed duplicate rendering of `extraDeploy` items.
* **ECK RBAC** — The ECK RBAC resources are rendered only when `elasticsearch.enabled: true`. The unused `elastic-job` RBAC was removed.
* **Release pipeline** — The chart is now published to ECR by a manual GitHub Actions run.

## Upgrade Notes

* **Passwords** — The passwords are now stored in the `appmixer-redis-auth`, `appmixer-rabbitmq-auth`, and `appmixer-user-init` secrets. A password set explicitly in your values (`redis.auth.password`, `rabbitmq.auth.password`, `userInit.password`) is enforced, and changing it rotates the secret. If you don't set it, the existing value is kept.
* **Admin password** — If you set `userInit.password`, change it to plaintext. Previously it had to be a bcrypt hash.
* **Logstash values** — `logstash.rabbitmq.secretName`, `usernameKey`, and `passwordKey` were replaced by `logstash.rabbitmq.username`.


---

# 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.3.0.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.
