# Stack Upgrade Procedure

**URL:** <https://forums.suse.com/t/stack-upgrade-procedure/2002>\
**Category:** Rancher 1.x\
**Created:** [March 11, 2016, 2:48pm UTC](https://forums.suse.com/t/stack-upgrade-procedure/2002 "2016-03-11T14:48:56Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hwinkel](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/hwinkel/32/951_2.png) [@hwinkel](https://forums.suse.com/u/hwinkel)\
**Post date:** [March 11, 2016, 2:48pm UTC](https://forums.suse.com/t/stack-upgrade-procedure/2002/1 "2016-03-11T14:48:56Z")

</div>

HI,

was looking a while at the docs, but I still have no clear picture how Rancher handles Stack and Service Upgrades.

In the Stack UI is a upgrade button, but I cant see who is triggering the activation of this button?

- a updated image in the repo linked by a docker compose file?
- a updated Template in the Catalog?

Once this triggger hits, and the “upgrade” button is active, what exactly happens while upgrading? Is the strategy  
already defined per stack or service and just executed?

Many thanks,  
Holger

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [March 11, 2016, 4:27pm UTC](https://forums.suse.com/t/stack-upgrade-procedure/2002/2 "2016-03-11T16:27:09Z")

</div>

The upgrade button is for new versions (the numbered directories) of a catalog template. Performing the upgrade sends the updated YAML and answers to the stack’s `upgrade` action, which sends it to rancher-compose-executor and calls rancher-compose upgrade. There are no strategy/other options exposed.

---

<div class="post-metadata">

**Author:** ![hwinkel](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/hwinkel/32/951_2.png) [@hwinkel](https://forums.suse.com/u/hwinkel)\
**Post date:** [March 11, 2016, 7:34pm UTC](https://forums.suse.com/t/stack-upgrade-procedure/2002/3 "2016-03-11T19:34:47Z")

</div>

many thanks, makes sense, the updated YAML and stack is therefore responsible for defining the update procedure. Will try to make some tests after 0.6x is released.