Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Versioning in Helm Chart releases #155

Open
commx opened this issue Sep 10, 2024 · 4 comments
Open

App Versioning in Helm Chart releases #155

commx opened this issue Sep 10, 2024 · 4 comments

Comments

@commx
Copy link

commx commented Sep 10, 2024

In bc14dac we have seen a version bump for the Helm Chart version (6.21.0 to 6.21.1) but a minor downgrade for the actual app version (6.10.5 to 6.8.6). That doesn't look right to me.

Can someone confirm if this is the intended behaviour?

Background: I performed an upgrade for a Rocketchat instance via Helm from 6.21.0 to 6.21.1. The retention configuration was broken (opening the Retention Policy settings always resulted in Application GUI crash; all DMs older than 1 day were pruned. After performing a rollback to Chart version 6.21.0 the Retention Policy settings worked again.

@ben-ganley
Copy link

Also noticed the same issue, the newer chart versions seem to have varying supported releases in them. Upgrading the chart version can easily result in a downgrade of app version and a broken application.

@lyz-code
Copy link

The management of the appVersion between helm-chart version promotion is quite worrisome:

Chart version appVersion
6.22.0 6.12.1
6.22.1 6.11.3
6.22.2 6.9.7
6.23.0 6.10.6
6.23.1 6.8.7
6.23.2 6.13.0

I'm shocked by the lack of consistency, I'm sure that each of these upgrades would break the application.

Please amend your release process to fix this bug, as for right now it gives us sysadmins absolutely zero trust to upgrade

@commx
Copy link
Author

commx commented Dec 6, 2024

@debdutdeb can you bring some light into this?

@debdutdeb
Copy link
Member

I can tell that this happened due to a bug in automation. Until that is fixed, I have disabled it, and further releases will be made manually when needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants