Repository navigation
Add testing to ensure data integrity for upgrades #8003
Description
Area for Improvement
Upgrade testing needs to be implemented for Radius to ensure continued data integrity during upgrades.
Observed behavior
Currently, it is unknown whether the data containing the state of your Radius deployments will be carried over when you upgrade your installation of Radius to a newer version. There are anecdotal observations that indicate that the data does appear to persist across upgrades, but this has not been explicitly tested and confirmed.
Desired behavior
If, after testing and verification, it's determined that Radius does maintain the state of deployments across upgrades, then functional tests must be added to ensure we continuously test for and validate this upgrade behavior. If not, then there needs to be a work item in the backlog tracking the implementation of this behavior to maintain state across upgrades.
Proposed Fix
IF Radius does maintain the state of deployments across upgrades: add tests to the pipeline to continuously validate this behavior
ELSE if Radius does not maintain the state of deployments across upgrades: log an issue in our backlog to add this functionality
rad Version
RELEASE VERSION BICEP COMMIT
0.38.0 v0.38.0 0.30.3 cf376db253a010c32a72ae38f9b967e84d4e92f9
Operating system
MacOS 15.0.1 M1 chip
Additional context
No response
Would you like to support us?
- Yes, I would like to support you
Activity
radius-triage commentedon Oct 17, 2024
👋 @willtsai Thanks for filing this issue.
A project maintainer will review this issue and get back to you soon.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
radius-triage commentedon Oct 21, 2024
👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.
We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.
For more information on our triage process please visit our triage overview
nithyatsu commentedon Feb 24, 2025
Upgrade testing should include the case where an upgrade introduces new CRDs, similar to #8001. Calling this out, since helm tooling seems to not identify new CRDs for some of its commands today.