Skip to main content

Upgrades

Conncentric supports rolling upgrades with no downtime. Old and new versions of the platform can run side-by-side during the rollout, so your sessions stay active throughout.

Before You Upgrade​

Read the release notes for every version between your current version and the target. Look for:

  • Any changed Helm value names
  • Any steps that must be done manually (these are rare and always called out explicitly)

Upgrade Steps​

1. Update the image tags​

In your values file, set the new version for all three components:

orchestrator:
  image:
    tag: "1.5.0"

adapter:
  image:
    tag: "1.5.0"

portal:
  image:
    tag: "1.5.0"

2. Run Helm upgrade​

helm upgrade conncentric ./deployment/charts/conncentric \
  -n conncentric \
  -f my-values.yaml \
  --atomic \
  --timeout 5m

--atomic rolls back automatically if pods don't start successfully within the timeout.

3. Verify​

kubectl rollout status deployment/conncentric-orchestrator -n conncentric
kubectl rollout status deployment/conncentric-adapter -n conncentric
kubectl rollout status deployment/conncentric-portal -n conncentric

Then check that adapters are back up by opening the Portal and navigating to the Adapters list. All adapters that were ACTIVE before the upgrade should return to ACTIVE within a few seconds of each pod restarting.

Rolling Back​

If something goes wrong:

helm rollback conncentric -n conncentric

This restores the previous version. Because the platform only adds to the database schema (never removes columns during a version upgrade), rolling back the code is safe. The old version simply ignores any new columns it doesn't know about.

Updating One Component at a Time​

To patch just the Orchestrator without touching anything else:

helm upgrade conncentric ./deployment/charts/conncentric \
  -n conncentric \
  --set orchestrator.image.tag=1.5.1 \
  --reuse-values

--reuse-values keeps all other settings from the current release.

Upgrading With a Maintenance Window​

While Conncentric supports live rolling upgrades, some organizations prefer to upgrade during a scheduled window. To do a clean, controlled upgrade:

  1. Disable all adapters in the Portal: go to Adapters, select all, click Disable
  2. Wait for all sessions to show INACTIVE
  3. Run the upgrade
  4. Verify the new version is running
  5. Re-enable adapters in the Portal: select all, click Enable

This approach ensures active sessions disconnect cleanly rather than being interrupted mid-message.