How to rollback from Version 7.0 to version 6.x

With the introduction of version 7.0, it is no longer possible to roll back to a previous version using the Helm Rollback command.

In the Helm Charts for 6.x and prior version releases, Persistent Volume Claims were used for every required volumeMount, as shown below:

List of Persistent Volume Claims:

For the release of version 7, the Helm Charts were updated to make use of subPaths. A subPath is a configuration property used in container orchestration that allows you to mount a specific file or directory from a volume into a specific path within a container, rather than mounting the entire volume.

The key benefits of this approach are:

Shared Storage, Segregated Data: You can use a single large Persistent Volume (PV) to store data for multiple microservices. Each service is assigned its own subPath, ensuring they don't overwrite each other's files while keeping storage management simple.

Reduced Resource Overhead: Provisioning dozens of small cloud storage volumes for dozens of microservices can be expensive and hit cloud provider limits. Consolidating into one volume and partitioning it via subPaths is much more efficient.

Refactored list of Persistent Volume Claims:

In the event that a rollback to version 6.x is required, perform a helm uninstall lumenvox -n lumenvox command followed by a helm install with the specific version of the required Helm Charts, for example: helm install lumenvox lumenvox/lumenvox --version 6.3 -f <values.yaml> -n lumenvox