Upgrade Nected Version

This guide explains how to upgrade your self-hosted Nected instance to a newer version using Helm. The upgrade process applies to any Kubernetes-based deployment and ensures that your services, configuration, and data remain intact during the version transition.

Before proceeding, ensure that you have:

• Backed up your nected-values.yaml file.

• Verified that all services are healthy using kubectl get pods.

• Taken a backup of your PostgreSQL and Redis databases if upgrading across major versions.

Step 1: Update the Latest Helm Chart

To make sure you're using the latest Helm chart for Nected:

helm repo update nected

Step 2: Review the Change Log

Before upgrading, review the Nected Release Notes to:

• Identify new configuration keys

• Check for breaking changes

• Note any deprecations or removals

Update your values files accordingly.

Step 3: Apply the Upgrade

To upgrade the Nected core application, run:

helm upgrade nected nected/nected -f values/nected-values.yaml

This command will pull the latest Helm charts and apply them to your running cluster while preserving your configuration.

---

Step 4: Verify the Upgrade

After the upgrade completes:

1. Run kubectl get pods to ensure all pods are in Running or Completed state.

2. Visit your UI domain (e.g., https://app.yourdomain.com) and verify the platform is accessible.

3. Optionally, inspect logs to validate post-upgrade stability:

kubectl logs -l app=nected-nalanda
kubectl logs -l app=nected-vidhaan-router

Rollback (if needed)

If an issue occurs after upgrading, you can roll back to the previous stable release:

helm rollback nected <REVISION_NUMBER>

Use helm history <release-name> to list past revisions:

helm history nected

Need Help?

If you encounter issues or have upgrade-specific questions, contact the Nected team at [e-mail].