forked from rook/rook
Sébastien Han
087d71106b
On rare occasion, the ceph checks might not be 100% correct and the user might decide to force an upgrade anyway. Correctly, if we are in an upgrade, we perform `ok-to-stop` check for each daemon, if one of them fails, we retry and eventually fail. They are corner-cases where users would like to force the upgrade anyway. Enhance the new CR property: "skipUpgradeChecks: true". Closes: https://github.com/rook/rook/issues/3872 Signed-off-by: Sébastien Han <seb@redhat.com>
32 lines
537 B
Markdown
32 lines
537 B
Markdown
# Major Themes
|
|
|
|
## Action Required
|
|
|
|
## Notable Features
|
|
|
|
|
|
### Ceph
|
|
|
|
- A new CR property `skipUpgradeChecks` has been added, which allows you force an upgrade by skipping daemon checks. Use this at **YOUR OWN RISK**, only if you know what you're doing. To understand Rook's upgrade process of Ceph, read the [upgrade doc](Documentation/ceph-upgrade.html#ceph-version-upgrades).
|
|
|
|
### EdgeFS
|
|
|
|
|
|
### YugabyteDB
|
|
|
|
|
|
|
|
## Breaking Changes
|
|
|
|
### <Storage Provider>
|
|
|
|
|
|
## Known Issues
|
|
|
|
### <Storage Provider>
|
|
|
|
|
|
## Deprecations
|
|
|
|
### <Storage Provider>
|