Goal
Use the template lifecycle path instead of treating updates as blind redeploys.Prerequisites
- A template-backed stack
- A newer published template version
Workflow
Preview before you apply
The update panel on the stack detail page previews the upgrade before anything changes: the diff against the running stack and a check for any inputs the newer version requires but the stack does not have yet.Apply and watch
- Applying the update produces a new release and moves the stack to the newer template version.
- Watch the recovery state through the upgrade rather than assuming it finished.
- A template upgrade can be rolled back if the new version misbehaves.
Status meanings
- up_to_date: the stack matches the latest published template version.
- update_available: a newer version exists and can be previewed.
- upgrade_blocked: the upgrade cannot apply safely as-is — resolve the blocking reason first.
- unknown: provenance could not be resolved; investigate before forcing changes.
Expected result
The stack moves to a new template version with upgrade history preserved.
Related guides
Template upgrade safety and service notes
Understand why an upgrade is safe, risky, or blocked, and how template readiness notes should influence operator decisions.
Template inputs and secrets
Understand which template values are required, which are sensitive, and how they affect rendering and upgrades.
Stack troubleshooting
Common stack-side failures around placement, logs, health, template drift, and restore behavior.