Skip to main content
The desktop app updates itself. In a cluster, KubeStacks is upgraded like anything else Helm installed: you upgrade its chart. The chart is released with KubeStacks itself, so the chart’s version is the app’s.

​
Upgrade

1

See what's new

Each version’s changes are in the changelog and on GitHub releases.
2

Upgrade the chart

Without --version, Helm installs the latest. The image’s tag follows the chart unless you set image.tag.
3

Check it started

The first line of the log names the version that’s running.

​
What people see

Sessions live in KubeStacks’ memory, so a new pod signs everyone out. Open pages reconnect to the new pod by themselves, and show the sign-in page. With single sign-on, signing in again is a click; with tokens, people paste one again. Behind an authenticating proxy, KubeStacks keeps no sessions of its own, so nobody notices more than a reconnect. The same goes for any change that replaces the pod: changing a setting, or the views everyone sees.
For the same reason the chart runs one replica. More than one would need sticky sessions, and each replica would still keep its own sessions.

​
Roll back

Helm keeps the previous revision, so going back is one command:
helm history kubestacks --namespace kubestacks lists the revisions, and helm rollback kubestacks <revision> --namespace kubestacks goes back to a particular one.

Changelog

What changed in each version.

Helm values

Every setting the chart has.