Update the Chart always to the latest stable

[rhizoet]

Can we update the Chart to the latest stable version i.e. v2.27.2 and not stay on 2.23.1 for a long time. I don't think it makes sense that we stay on old releases.

The version bump in the workflow doesn't seem to function properly.

I've set the latest stable in the deployment on k8s but after that the dashboard and the cluster aren't any more reachable. I think the Chart itself need some adjustments to work properly with any higher version than 2.23.1.

[rhizoet]

Ok, I saw a few Minutes ago that 5.0.0 was released with the latest Zitadel App version. But a upgrade from 4.6.0 to 5.0.0 breaks on my Installation. I've get no error but the dashboard does not load anymore. A fresh install function properly.

Did you test the upgrade from 2.23.1 to 2.28.1?

[fforootd]

Ok, I saw a few Minutes ago that 5.0.0 was released with the latest Zitadel App version. But a upgrade from 4.6.0 to 5.0.0 breaks on my Installation. I've get no error but the dashboard does not load anymore. A fresh install function properly.

Did you test the upgrade from 2.23.1 to 2.28.1?

Hm interesting, this could also relate to this observation here https://discord.com/channels/927474939156643850/1019895518383583323/threads/1116872146883444877

[rhizoet]

I don't have discord, so I can't look into this. But I'm happy that not only my installation have some issues.

[rhizoet]

Ok, I've set up a new instance, imported my Database and installed first the 4.6.0 version. After that I've done an upgrade to 5.0.0 and the instance isn't loading anymore.
Can you provide a fix for this? I think a jump from 2.23.x to 2.28.x is too much and breaks stuff. Or you need integrate a migration tool or something else. I don't know. But we can't upgrade at the moment.

[fforootd]

@livio-a @adlerhurst do we have an idea why this happens.

I actually could produce a weird state this way as well but I have no clue what broke.

[jessebot]

Agree that keeping the appVersion of this chart up to date would be a great idea, so everyone is always installing the latest. You can set this up with renovateBot, but I'm not sure dependabot can handle appVersion in Chart.yaml yet. For renovateBot, you'd probably see a great improvement over your current use of dependabot by installing the github app. Renovate is open source and works across more git providers and software types than dependabot. When you install it for an organization, it will automatically create a dashboard in each of your repos to track dependencies. I use it to keep a matrix chart's appVersion up to date with the following config.js.

Edit: updated link to old config.js.

[rhizoet]

Any news on this? I saw that a version bump has added to the workflows. But since 10 months the run failed. So the version will not be updated automatically just manually. Zitadel is by now on version 2.49.x. And the chart stays since multiple chart updates on 2.46.0.