Upgrade and rollback
Treat runtime upgrades and pipeline changes as separate, versioned operations.
Before upgrading
- Read What's New, known issues, and breaking changes.
- Confirm the supported upgrade path and compatibility matrix.
- Export or record the active configuration revision.
- Identify the last known-good software and configuration versions.
- Test the upgrade with representative traffic.
Upgrade
Use the supported console or installation workflow. Observe runtime health, active version, active pipeline revision, connection behavior, and application errors before expanding traffic.
Rollback
Rollback may require one or both actions:
- reactivate a known-good pipeline revision;
- restore the previous supported runtime release through the documented deployment workflow.
Do not assume configuration created by a newer release is readable by an older release. Check release notes first.
After rollback, verify data-path health and record the reason, affected versions, and follow-up action.