Currently, if a new CRD version is created after a Rancher upgrade, BRO adds that version to spec.storedVersion with storage: false and modifies the restore to include it when rolling back Rancher. This results in a different CRD from the original, which may cause issues during another Rancher upgrade if the controller is not prepared for it.
Acceptance Criteria
- Investigate a way for the rollback to not modify the original CRD without violating the
spec.storedVersion constraint k8s enforces
Currently, if a new CRD version is created after a Rancher upgrade, BRO adds that version to
spec.storedVersionwithstorage: falseand modifies therestoreto include it when rolling back Rancher. This results in a different CRD from the original, which may cause issues during another Rancher upgrade if the controller is not prepared for it.Acceptance Criteria
spec.storedVersionconstraint k8s enforces