Description of problem:
Continuous triggers on the UpgradeBackupController on every z-upgrades caused out of space issues for some customers. We decided in a meeting to remove the (undocumented) z-stream upgrade triggers. In addition we're going to add a retention mechanism by deleting all files and folders in /etc/kubernetes/cluster-backup before taking a y-stream upgrade backup.
Version-Release number of selected component (if applicable):
4.10 -> 4.14
How reproducible:
always
Steps to Reproduce / expected results:
* do a z-upgrade * observe that no backup should be taken anymore * do a y-upgrade * observe that a backup is still taken * note that any previous backups should not exist anymore in /etc/kubernetes/cluster-backup
Additional info:
- blocks
-
OCPBUGS-27776 [4.12] Remove z-upgrades from UpgradeBackupController
- Closed
- clones
-
OCPBUGS-22477 [4.14] Remove z-upgrades from UpgradeBackupController
- Closed
- is blocked by
-
OCPBUGS-22477 [4.14] Remove z-upgrades from UpgradeBackupController
- Closed
- is cloned by
-
OCPBUGS-27776 [4.12] Remove z-upgrades from UpgradeBackupController
- Closed
- links to
-
RHBA-2024:0660 OpenShift Container Platform 4.13.z bug fix update
(1 links to)