How to Perform an Upgrade or Downgrade of the Capacity Private Cloud Software
This guide covers upgrading and downgrading the Capacity Private Cloud platform with Helm. Both operations change the running deployment in place, so treat them as controlled changes: before you begin, take a current backup of your values.yaml file and review the release notes for the target version. The release notes are where breaking changes and version-specific migration steps are called out — read them first.
Helm upgrade
Step 1 — Update the Helm charts. Refresh your local chart repository so the new chart version is available:
| helm repo update -n lumenvox |
Step 2 — Delete the existing persistent-volume-directory-setup job. This job is immutable once created, so it must be removed before the upgrade can recreate it:
| kubectl delete job persistent-volume-directory-setup -n lumenvox |
Step 3 — Run the Helm upgrade.
Note: if the image tag is pinned in your values.yaml, make sure it has been updated to the target version first (for example, tag: "7.0"). Otherwise the upgrade will redeploy the version the tag still points at.
| helm upgrade lumenvox lumenvox/lumenvox -f values.yaml -n lumenvox |
A successful upgrade produces output similar to:
| Release "lumenvox" has been upgraded. Happy Helming! NAME: lumenvox LAST DEPLOYED: Thu Feb 19 16:59:20 2026 NAMESPACE: lumenvox STATUS: deployed REVISION: 2 TEST SUITE: None |
Helm downgrade
Warning: the move to v7 is a breaking change, which affects downgrades from v7 (and newer) back to v6.x and older. Such a downgrade is still supported, but it cannot be done with helm rollback — it must be performed using helm uninstall and helm install, as described in How to Rollback from Version 7.0 to Version 6.x. The steps below apply to a helm rollback within the same major version.
Step 1 — Check the Helm revision history to identify the revision you want to roll back to:
| helm list -n lumenvox |
Example output:
| NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION lumenvox lumenvox 4 2026-02-19 14:58:09.605952471 +0000 UTC deployed lumenvox-6.3.0 6.3.0 |
Step 2 — Delete the existing persistent-volume-directory-setup job (as in the upgrade, the immutable job must be removed first):
| kubectl delete job persistent-volume-directory-setup -n lumenvox |
Step 3 — Roll back to the target revision. To return to the immediately preceding deployment, use the revision N-1 (one before the current). In the example above the current revision is 4, so the rollback target is 3:
| helm rollback lumenvox 3 -n lumenvox |
A successful rollback reports:
| Rollback was a success! Happy Helming! |