Upgrades Overview
Upgrade guides cover changes tied to a version boundary: platform release upgrades and component migrations that ship with a specific release. Recurring procedures that are not tied to a release (certificate rotation, datastore maintenance) will live in a separate Maintenance section as they are documented.
General Procedure
Every upgrade follows the same shape; the individual guide fills in the specifics.
- Read the guide end to end first, including its Verification and Rollback sections, before starting the rollout.
- Confirm prerequisites: the platform image versions, chart versions, and any feature support the change depends on. Confirm with your DynamoAI deployment engineer if you are unsure whether your release line includes a prerequisite.
- Mirror artifacts: pull the new chart and container images into your registry before the window.
- Back up state the change touches: snapshot databases before any change described as a one-way migration.
- Schedule a maintenance window when the guide calls for one; component restarts and cleared sessions are listed per guide.
- Apply values through your GitOps flow and reconcile; avoid imperative
kubectledits that drift from the values files. - Verify using the guide's Verification section before declaring the upgrade done.
- Keep the Rollback path ready: know before you start what reverting requires (usually a values revert plus, for one-way migrations, a database restore).
Upgrade Guides
| Guide | Version Boundary | What Changes |
|---|---|---|
| Upgrade Keycloak from 24 to 26 | Platform release 3.27 | Bundled Keycloak major-version upgrade with breaking configuration changes and a one-way database migration |
| Enable Redis Authentication & TLS | Platform release 3.26.4 or later | Opt-in authenticated and TLS-encrypted Redis connections, for in-cluster Redis and managed providers |