Upgrading
We follow semantic versioning; minor and major version increases can have significant changes
These steps also apply to downgrading
It is generally safe to upgrade the controller while VMs are running and nodes are joined. However, we do recommend temporarily pausing CI/CD jobs or assigning to agents and letting the currently running jobs drain before moving forward if you want to be extra careful
If upgrade the Anka Virtualization package:
- Block CI/CD jobs from starting or being assigned to agents
- Wait for all CI/CD jobs to complete on your nodes
- Run
sudo ankacluster disjoinon each nodeYou can then safely install the latest Anka Build Virtualization CLI
If your existing Anka Virtualization version is noted in the Anka Virtualization Upgrade Matrix:
- Upgrade the guest addons inside existing VM templates with
anka start -u- Push the newly upgraded VM templates to registry with
anka registry push {vmNameOrUUID} --tag <tag>
Before upgrading, check if your current version is noted in the Pre-Upgrade Considerations and adjust your upgrade plan accordingly.
Go to your Controller & Registry server:
- Docker:
- Make a backup of your
docker-compose.yml. - Download and extract the latest package.
- Configure the values in the
docker-compose.ymlor copy your previousdocker-compose.ymlto the new directory. - Run
docker-compose buildto prepare the new docker tag. - Run
docker-compose downto take down the older version. - Run
docker-compose up -din the newer version directory.
- Make a backup of your
- Native macOS package:
- Make a backup of your
/usr/local/bin/anka-controllerd. - Install the new .pkg (see the MacOS Guide).
- Run
sudo anka-controller restart.
- Make a backup of your
- Docker:
Run
curl -O http://**{controllerUrlHere}**/pkg/AnkaAgent.pkg && sudo installer -pkg AnkaAgent.pkg -tgt /on your nodes to pull the latest Anka Agent binary and ensure proper communication between the CLI and the Controller API.
Pre-Upgrade Considerations
| Existing Version | Target Version | Recommendation |
|---|---|---|
| 1.2.1 | 1.5.2 | Upgrade Anka CLI package on all the hosts to atleast 2.1.X |
| 1.2.1 | 1.5.2 | Recommended to upgrade Anka Registry to version 1.5.2, if you want to use cache builder |
| 1.2.1 | 1.5.2 | Recommended to upgrade Anka Jenkins Plugin to version 1.22.2 |
| 1.2.1 | 1.5.2 | Recommended to upgrade Anka TeamCity Plugin to version 1.7.0 |
| Existing Version | Target Version | Recommendation |
|---|---|---|
| 1.3.0 | 1.5.2 | Upgrade Anka CLI package on all the hosts to atleast 2.1.X |
| 1.3.0 | 1.5.2 | Recommended to upgrade Anka Registry to version 1.5.2, if you want to use cache builder |
| 1.3.0 | 1.5.2 | Recommended to upgrade Anka Jenkins Plugin to version 1.22.2 |
| 1.3.0 | 1.5.2 | Recommended to upgrade Anka TeamCity Plugin to version 1.7.0 |
| Existing Version | Target Version | Recommendation |
|---|---|---|
| 1.4.0 | 1.5.2 | No need to upgrade Anka CLI package on hosts |
| 1.4.0 | 1.5.2 | Recommended to upgrade Anka Registry to version 1.5.2, if you want to use cache builder |
| 1.4.0 | 1.5.2 | Recommended to upgrade Anka Jenkins Plugin to version 1.22.2 but not necessary |
| 1.4.0 | 1.5.2 | Recommended to upgrade Anka TeamCity Plugin to version 1.7.0 1.22.2 but not necessary |
| Existing Version | Target Version | Recommendation |
|---|---|---|
| 1.5.0 | 1.5.2 | No need to upgrade Anka CLI package on hosts |
| 1.5.0 | 1.5.2 | Recommended to upgrade Anka Registry to version 1.5.2, if you want to use cache builder |
| 1.5.0 | 1.5.2 | Recommended to upgrade Anka Jenkins Plugin to version 1.22.2, but not necessary |
| 1.5.0 | 1.5.2 | Recommended to upgrade Anka TeamCity Plugin to version 1.7.0, but not necessary |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.