Upgrade Guide
Upgrading to 1.8 from an Earlier Release
Version 1.8 cannot be installed over 1.6 or any earlier release. The platform’s Helm charts were rearranged, and the cluster is now built and managed by deploy, so an earlier cluster cannot be upgraded in place.
To move to 1.8:
- Install 1.8 on a new cluster, on new or reinstalled machines, with the Quickstart.
- Set up its users and configuration. Contact AgileTV support to plan moving your existing configuration.
- Point your CDN Directors at the new manager, then retire the old cluster.
Upgrading from 1.8 to a Later Release
From 1.8 on, an upgrade is a deploy run with the new release’s ISO: deploy upgrades k3s on each machine, one server at a time, then upgrades the cdn-platform release.
Read the Release Notes for the new release, for any step it needs before or after the upgrade.
Check that the cluster is healthy:
acd-admin statusReplace the ISO at
/mnt/esb3027with the new one, on the first server:umount /mnt/esb3027 mount -o loop,ro /root/esb3027-cdn-manager-<new version>.iso /mnt/esb3027The preset link in
/etc/acd/deploypoints into/mnt/esb3027, so mount the new ISO at the same path.Run
deploy initfrom the new ISO. It is safe to run again: it replaces the installed Ansible collections with the new ISO’s versions, installsansible-coreonly if it is missing, keeps your preset, and leaves the files you have edited alone./mnt/esb3027/deploy initRun
deploy:/mnt/esb3027/deploy
deploy takes a backup of the configuration before it changes anything, including an etcd snapshot of the cluster. That backup does not include the data stored in the cluster, such as the PostgreSQL databases: back that up first, as described in Backup Procedures. See Backups.