Upgrade
Before upgrading Obcerv components you must ensure you have the latest helm charts and docker images. If you have chosen to maintain your own docker repository you must first ensure it is up to date with the ITRS repository, to do this follow the steps in Docker images.
When a new version of Obcerv is released, a new version of the Operator typically comes with it. The Operator must be upgraded first before upgrading any Obcerv instances in the cluster.
- Update the Helm repository to get the new charts:
helm repo update itrs
- Upgrade the operator:
helm upgrade obcerv-operator itrs/obcerv-operator -n <namespace> --version <new-version> --wait
The --version flag is not required - if omitted, Helm will use the latest version available. However, it is
recommended to explicitly provide the desired version.
- Upgrade an Obcerv instance using the same configuration file used during installation:
helm upgrade -f config.yaml <instance> itrs/obcerv -n <namespace> --version <new-version>
The --version flag is not required - if omitted, Helm will use the latest version available. However, it is
recommended to explicitly provide the desired version.
The Operator will stop, upgrade, and restart the workloads in the correct order. To monitor the progress, run:
kubectl describe obcerv <instance> -n <namespace>
While the upgrade is in progress, the Obcerv status shows as DEPLOYING. Once completed, the status is set to DEPLOYED.
Note
You cannot downgrade an instance that has already been upgraded.