We have just released Stackspin version 2.0!

Why another major release?

Soon after releasing version 1.0, we noticed that the new version of k3s (the software responsible for running all the other software that makes up Stackspin) has a bug that destabilized the platform. To reconfigure k3s to work around this bug, Stackspin cluster administrators need to manually re-run the Ansible script that sets up Stackspin installations. To signify this need, we’ve increased the version number from 1.0 to 2.0.

How do I upgrade?

Follow the instructions in the documentation to upgrade your Stackspin cluster to version 2.0.

What’s new in 2?

You can find the full changelog here. In this post we will highlight the most important changes:

  • K3s was upgraded to version v1.25.2+k3s1 and configured to work around a k3s bug.
  • The Stackspin Dashboard now only shows installed applications. If you have used custom URLs when setting up your applications, the dashboard will now show the correct URLs.
  • Nextcloud now uses Redis for caching, which should improve its speed.

Why not Version 2.0.0?

We stepped away from semver because the patch version number does not make sense in the Stackspin context. From now on, we’ll have two release types:

  • Minor release, updates y in a version number formatted x.y. These releases occur regularly (we aim for every 2 weeks). Clusters will auto-update when we do minor releases.
  • Major release, updates x in a version number formatted x.y. These releases indicate that you need to manually run an upgrade script, because auto-upgrade is not possible. We aim for a major release around every 6 months, but we could do one earlier if it includes an important security or other big bug fix that we cannot apply through auto-updates.

As always, please make sure to upgrade your Stackspin as soon as possible, and let us know about your experiences!