Image & Helm Versioning

Frequently asked questions about container versioning and Helm Charts for Capacity Private Cloud.

How do I use semantic versioning in my Helm Charts when installing or upgrading?

The Helm Charts are semantically versioned, so you should install the version of the chart that matches the container version you want to deploy.

See Semantic Versioning 2.0.0 for more information. The platform follows this versioning structure:

• Major — A change that breaks backward compatibility (e.g. an API change)
• Minor — An update to functionality without breaking backward compatibility
• Patch — No change to functionality; a fix applied to an earlier minor release

View full size

How can I prevent updating to the latest version?

Simply don’t run helm repo update. You can then use the regular install commands. If you accidentally run helm repo update and a newer chart version is downloaded, any subsequent helm install command may use that later version. If you want to remain on a specific version, explicitly specify it:

helm install lumenvox lumenvox/lumenvox --version 6.1.0

How can I test a later version before upgrading my production stack?

Set up a separate stack or cluster and test there before rolling changes into production.

Can I roll back to an older version 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, but rollback is not guaranteed for all version jumps.

How does Capacity Private Cloud manage versions in Helm Charts?

Charts are semantically versioned and match the container versions they deploy.

How do I pin my production cluster to a specific release version?

Specify the version explicitly in the helm install command:

helm install lumenvox lumenvox/lumenvox --version 6.1.0

You can also control version behaviour through the image pull policy in your values file:

• If your image tag is 6.1 and pull policy is set to Always, restarting a pod will pull the latest patch version of that image (e.g. 6.1.0 → 6.1.1).
• If pull policy is Never or IfNotPresent, updates will not be fetched on restart.
• If your image tag is pinned to a full version such as 6.1.0, your images will remain stable regardless of what patches are released.

The default pull policy is IfNotPresent. To automatically receive the latest patches, set the pull policy to Always and leave the image tag at the minor version (e.g. 6.1).