Unleash
Document upgrade/downgrade processes #2546
-
|
After reading the documentation I have the following questions regarding upgrade/downgrade processes:
Also, could be quite useful to know about compatibility guarantees between releases. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
It is possible only if you spin up another instance while the old one is still running and move traffic. We don't have it out of the box, since it's just a NodeJS app. Migrations, both up and down, are automatic (we had one issue in the past, 4.12, this was patched after a day). All data related to new features can be lost when downgrading.
We follow semantic versioning. Only in major releases you can expect breaking changes. We provide migration guides when needed. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the CC, @Tymek! I think you covered this quite well; I don't have anything else to add 🙌🏼 |
Beta Was this translation helpful? Give feedback.
-
|
actually, I would like to add something 😅 You can have a setup using Unleash Proxy where it's OK if your main instance and DB are down for maintenance. SDKs also cache the toggles. Depending of course on requirements. If you mostly care about end-user SLA it's a fairly resilient and scalable system. |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, would be great to document the regular (w/ downtime) upgrade process for the helm chart installation. Just tried it from 2.7.2 to 2.8.0 and it fails because postgresql version changed and requires db upgrade. I tried to perform the upgrade and keep the postgresql version 11 as documented https://docs.bitnami.com/kubernetes/infrastructure/postgresql/administration/upgrade/, but it also failed because app couldn't connect to the db although the db pod was running, not sure where it went wrong... |
Beta Was this translation helpful? Give feedback.
-
|
Oh, interesting. @chriswk, do you know anything about this? |
Beta Was this translation helpful? Give feedback.
-
|
Hey, @mbsimonovic 👋🏼 Firstly, I apologize for the delayed response. We acknowledge that the update to 2.8.0 ideally should have been marked as a major update. That was an oversight on our part, and I appreciate your understanding. Regarding your setup, did you manage to get everything running smoothly? If you're using the embedded postgres, I'd like to point out that we currently don't have a direct upgrade path. It also doesn't have any backups and isn't optimized for persistent storage. Therefore, we advise running a separate instance of postgres instead, to ensure a smoother experience. Let me know if you need any further assistance or guidance! |
Beta Was this translation helpful? Give feedback.
-
|
Hey no worries, just wanted to point out a potential issue. I've moved from embedded to a managed postgres instance so no problems for me anymore. |
Beta Was this translation helpful? Give feedback.
-
|
Great to hear! And yeah, we appreciate it. I'll have a look and make sure to call the issues with the embedded postgres out explicitly in the docs if it isn't already there. |
Beta Was this translation helpful? Give feedback.
It is possible only if you spin up another instance while the old one is still running and move traffic. We don't have it out of the box, since it's just a NodeJS app. Migrations, both up and down, are automatic (we had one issue in the past, 4.12, this was patched after a day). All data related to new features can be lost when downgrading.
We follow semantic versioning. Only in major releases you can expect breaking changes. We provide migration guides when needed.