Helm-chart versioning strategy

[StefanKert]

One of our goals at fiskaltrust is providing a stable upgrade path and a clear schema on what has changed in our products.

Whats the problem?

The current versioning strategy for our helm-charts (https://github.com/fiskaltrust/helm-charts/tree/master/bring-your-own-datacenter) does not really follow that strategy and it is very hard to notice breaking / larger changes.

Currently the versioning strategy for our helm-chart is matching with the middleware release versions. This leads to the fact that we are mostly only changing the patch, even though there are bigger changes in the manifests like the Migration to v1.2.26. This coupling leads to the mentioned difficulties in detecting breaking / larger changes.

One of the benefits of this approach is the clarity about the used Middleware version which is also very important since it does affect the legal compliance if a wrong version is used.

For this reason, we should find a versioning strategy that fits both these needs.

How can we solve it?

Since we have various options to change this, we should collect some insights and discuss on the potential changes. I will adapt this first initial post to summarize the findings potential solutions.