Release notes
Where to find what changed, and what to read before upgrading.
Release notes for each version are published alongside the release and are listed in the console under Software for versions your deployment can see.
An air-gapped site has no version listing — keep the notes with the bundles you bring in, because you cannot look them up afterwards.
Reading them before an upgrade
Look for four things:
- Behaviour changes — anything that works differently after the upgrade.
- Required steps — actions to take before or after, in order.
- Deprecations — things still working now that will not be.
- API changes — if you automate against the REST API.
Versions in a deployment
A deployment carries several versions, and they move together during an upgrade:
| Component | Where |
|---|---|
| OS bundle | Every node |
| Packages | Every node |
| Agent | Every host |
| Orchestrator | Controllers |
Hyperion[vsnode1]> show version
Controller version: 2.0.0
A host’s agent version is on its detail page in Infrastructure, and the fleet’s versions are under Software.
Upgrade order
Warning — Controllers before hosts. A newer agent talking to an older control plane is not a combination to discover during a maintenance window.
See Upgrading the fleet.
Before any upgrade
- A backup that completed.
- Every controller
ALIVEandSYNC OK. - Spare capacity in each zone, because hosts are emptied one at a time.
- The release notes.
Restoring across versions
A backup restores onto the same or a newer version. A newer archive onto an older control plane is refused — it would replace the database and then fail to start.
So a backup taken before an upgrade restores onto the upgraded control plane, which is the direction you need.
Getting support
Quote:
- your installation identity, from Settings → Licensing,
- the version each component is running,
- the error ID or task ID, if there is one.
Your support contact is the one on your agreement with Velarion Systems.