LumenVox Container Versioning & Helm Charts
FAQ regarding container versioning and associated helm charts
How do I use semantic versioning in my Helm Charts when installing or upgrading LumenVox?
The Helm Charts themselves are versioned semantically, so customers should thus install the relevant version of the chart matching the LV Container version they would like to install.
See Semantic Versioning 2.0.0 | Semantic Versioning for more information on Semantic versioning.
In a nutshell, LumenVox follows the following versioning structure:
Major : A change that breaks backward compatibility (i.e. some API change)
Minor : An update to the functionality without breaking backward compatibility
Patch: No change to functionality, but a patch or fix applied to an earlier minor release
How can I prevent updating to the latest version if I don't want to?
Simply don’t run helm repo update, you can then use the regular install commands. If you accidently run helm repo update, then any further helm install commands, may use a later version of the charts if a new version is downloaded. If that is the case and you want to remain on an older version, you must specify the version when running helm install e.g.
helm install lumenvox lumenvox/lumenvox --version 6.1.0
How can I test a later version before upgrading my production stack?
Set up a new stack/cluster and test with it there
Can I go back to an older version of LumenVox safely if I don't like an upgrade?
This may not be possible depending on the version. When releasing a new version we generally test downgrading to the previous version.
How does LumenVox manage versions in Helm Charts?
Its semantically versioned and matches the containers
I was to use a specific release version of LumenVox in my production cluster, how can I do this?
Just specify the version in the version tag
install helm install lumenvox lumenvox/lumenvox --version 6.1.0
You can also specify pull policy in the values file.
If your image tag in the charts is 6.1 and you have a pull policy set to Always, then when you restart a pod, it will be upgraded to the latest patch version of that image i.e. 6.1.0 > 6.1.1
If your pull policy is set to Never or IfNotPresent, the update will not be fetched.
If your image tag is 6.1.0 your images will remain stable no matter what patches are released
The default setting is IFNotPresent.
To reiterate if you want to pull the latest patches you should set the pull policy to Always and leave the image tag as is