Upgrading Tines with Helm

Last updated November 9, 2026

Use Helm to upgrade an existing Tines installation or apply changes to its values.yaml. This guide also covers selecting a chart version and rolling back a Helm release.

The examples use release tines-app in namespace tines. Replace these names if your installation uses different ones.

Before you begin

Review the upgrade requirements for your current and target Tines versions, and confirm that your database backup is available.

If your chart version is earlier than 39.0.0, follow Upgrading Helm from charts before v39.0.0 before using the commands below.

A chart upgrade does not migrate an existing PostgreSQL 14 database to PostgreSQL 18. If you need to migrate the database, follow Upgrading from PostgreSQL 14 to PostgreSQL 18.

Choose a chart version

Refresh the repository index and list available versions:

helm repo update
helm search repo tines/tines --versions

Review the defaults for your target version:

helm show values tines/tines --version <chart-version>

Update your values.yaml as needed. Keep the existing APP_SECRET_TOKEN and settings required by your installation. See Configuring Tines with Helm for configuration examples.

Upgrade Tines

Upgrade to your selected chart version:

helm upgrade tines-app tines/tines \
  -n tines \
  -f values.yaml \
  --version <chart-version>

To use the latest chart version available in the repository, omit --version:

helm upgrade tines-app tines/tines \
  -n tines \
  -f values.yaml

Apply configuration changes

Edit your values.yaml and run helm upgrade with the version already installed. Pinning the version applies your configuration changes without also selecting a newer chart:

helm list -n tines

Use the version shown for your release:

helm upgrade tines-app tines/tines \
  -n tines \
  -f values.yaml \
  --version <installed-chart-version>

Note: Changing initialTenantConfiguration does not update an existing tenant or administrator. Those settings are used to seed the first tenant and user.

Verify the upgrade

Check the setup jobs and pods:

kubectl get jobs -n tines -l app=tines-app-setup
kubectl get pods -n tines

Inspect the logs for the setup job created by this upgrade:

kubectl logs -n tines job/<setup-job-name>

Confirm that setup completed successfully, the application pods are ready, and you can access Tines.

Roll back a release

Review the release history:

helm history tines-app -n tines

Roll back to the previous revision:

helm rollback tines-app -n tines

To select a particular revision:

helm rollback tines-app <revision> -n tines

Check the pods and verify access to Tines after the rollback.

Note: A Helm rollback restores the release configuration and Kubernetes resources. It does not restore a database backup or undo database migrations. Confirm that the target Tines version supports your current database state before rolling back.