Upgrade to 1.5.0
Last updated
Was this helpful?
v0.7
Last updated
Was this helpful?
This document outlines the step-by-step process to be followed before upgrading Devtron to version 1.5.0.
The upgrade process consists of three sequential Kubernetes jobs:
devtron-pre-upgrade: Prepares the environment for the upgrade.
devtron-upgrade-init: Scales down Devtron and takes the backup.
devtron-upgrade: Performs the restoration of data and scales up Devtron.
After the completion of the above jobs, you may proceed to upgrade Devtron using the UI or command line.
Ensure that you have and that at least one backup has been pushed successfully. to know more about the backups chart.
You must have administrative access to the cluster where Devtron is running, along with kubectl configured.
PVC creation must not be blocked by any policy. If it is, exclude the devtroncd namespace from it.
The devtron-pre-upgrade job creates the necessary resources and prepares for the database backup.
This job will:
Create a ConfigMap named devtron-postgres-upgrade in the devtroncd namespace.
Determine the StorageClass and size of the existing PostgreSQL PVC.
Create a new PVC named devtron-db-upgrade-pvc with additional storage (+5Gi).
Automatically apply the upgrade-init job.
To monitor the progress of this job:
Wait for this job to complete successfully before proceeding.
The devtron-upgrade-init job is automatically triggered by the devtron-pre-upgrade job:
It scales down all Devtron components to ensure database consistency.
Terminates active database connections.
Starts the Postgres migration process.
To monitor the progress of this job:
Ensure this job completes successfully before proceeding to the next step.
Once the backup is confirmed, apply the final upgrade job:
This job will:
Verify if the devtron-upgrade-init job was successful.
Extract any nodeSelectors or tolerations from the existing PostgreSQL StatefulSet.
Remove PostgreSQL 11 components.
Install PostgreSQL 14 with the same configuration.
Migrate the data.
Scale up all Devtron components.
To monitor the progress of this job:
After the upgrade job completes, verify the PostgreSQL migration:
The value of POSTGRES_MIGRATED should be "14" if the migration was successful.
If the devtron-upgrade-init or the devtron-upgrade job fails, check the logs of job and the ConfigMap for error messages:
Look for any entries with "ERROR" in the keys.
To reapply the devtron-upgrade-init job, delete the PVC named devtron-db-upgrade-pvc, recreate it with the same configurations and then reapply the devtron-upgrade-init job.
If the devtron-upgrade-init job is in a pending state, check for the PVC named devtron-db-upgrade-pvc, ensure that the PVC is successfully created.
Update the Helm repository
Run the upgrade command for Devtron
Once the database migration is complete, you can proceed with upgrading the Devtron application through the UI as mentioned in the final message of the upgrade job. Alternatively, you may use the mentioned below.