v5.3 (Kubernetes)
Upgrading on Kubernetes
When it comes time to upgrade your various components, you can do so by updating the version number in your configuration files and applying the changes in ArgoCD.
danger
Prerequisites
info
If you have made custom changes to your deployment file structure, please contact your Support team before you upgrade your environments.
- Download the latest Cinchy Artifacts from the Cinchy Releases Table > Kubernetes Artifacts column. For this upgrade, please download the Cinchy v5.3 k8s-template.zip file.
Depending on your current version, you may need to:
- Run the 5.2 upgrade script
| Current Version | Run the 5.2 Upgrade Script |
|---|---|
| 5.0 | Yes |
| 5.1 | Yes |
| 5.2 | X |
Configure to the newest version
- Navigate to your cinchy devops.automation repository
- Navigate to your deployment.json (You may have renamed this during your original Kubernetes deployment)
- In the cinchy_instance_configs section, navigate to the image tags. Replace the version number with the instance that you wish to deploy (Ex: v5.2.0 > 5.3.0).
// The component image tags are specified below to define which versions to deploy
"connections_image_tag": "v5.3.0",
"event_listener_image_tag": "v5.3.0",
"idp_image_tag": "v5.3.0",
"maintenance_cli_image_tag": "v5.3.0",
"meta_forms_image_tag": "v5.3.0",
"web_image_tag": "v5.3.0",
"worker_image_tag": "v5.3.0"
- Rerun the deployment script by using the following command in the root directory of your devops.automations repository:
dotnet Cinchy.DevOps.Automations.dll "deployment.json"
3. Commit and push your changes.
Apply the configurations
If your environment isn't set-up to automatically apply upon configuration, complete the following the apply the newest version:
- Navigate to the ArgoCD portal.
- Refresh your component(s). If that doesn't work, re-sync.