Upgrade for patch releases

General recommendations

Be sure to read the Everyware Cloud release notes and the planning the upgrade section.

Preparing to upgrade

Before upgrading to a patch release be sure to follow these steps:

backup the databases
backup your existing configuration exporting all project configurations

Upgrade steps

Patch releases of Everyware Cloud usually do no introduce configuration or database changes. If any change is required it will be described pointing to the Everyware Cloud version that requires it.

The process to upgrade Everyware Cloud is the following:

migrate from OpenShift templates to Helm Charts. This is described more in detail in the following section Migration to Helm Charts.
edit the charts' property files changing the image version for Everyware Cloud
upgrade the common EC configurations using Helm

helm upgrade -n everyware-cloud -f ec-configs.yaml ec-configs charts/01-prerequisites/ec-configs

upgrade the standard EC components using Helm

# Deploy the Events Broker
helm upgrade -n everyware-cloud -f ec-events-broker.yaml ec-events-broker charts/02-components/ec-events-broker

# Deploy the Message Broker
helm upgrade -n everyware-cloud -f ec-broker.yaml ec-broker charts/02-components/ec-broker

# Deploy the RESTful API
helm upgrade -n everyware-cloud -f ec-api.yaml ec-apicharts/02-components/ec-api

# Deploy the Web Console
helm upgrade -n everyware-cloud -f ec-console.yaml ec-console charts/02-components/ec-console

upgrade the optional EC components using Helm

❗️
Versions 5.7.2 and 5.7.3 of the Remote Access Service container image (eurotech/ec-vpn) contain a regression preventing the containers to work correctly. Don't use these particular versions of the 5.7 release.

# Upgrade the VPN Service if installed
helm upgrade -n everyware-cloud -f ec-vpn.yaml ec-vpn charts/02-components/ec-vpn

# Upgrade the Monitoring Service if installed
helm upgrade -n everyware-cloud -f ec-monitoring.yaml ec-vpn charts/02-components/ec-monitoring