-
Task
-
Resolution: Done
-
Undefined
-
ACM 2.8.0
-
False
-
None
-
False
-
doc-ack
-
-
-
None
Describe the changes in the doc and link to your dev story
Provide info for the following steps:
1. - [ ] Mandatory Choose the documentation release (Published releases are refreshed ~weekly after publication).
- [ ] ACM 2.4
- [ ] ACM 2.5
- [ ] ACM 2.6
- [ ]ACM 2.7
- [x]ACM 2.8
- [ ] MCE 2.0
- [ ] MCE 2.1
- [ ] MCE 2.2
2. - [ ] Mandatory Choose the type of documentation change.
- [ ] New topic in an existing section or new section
- [ X] Update to an existing topic
3. - [ ] Mandatory for bugs: What is the diff? Clearly define what the problem is, what the change is, and link to the current documentation:
4. - [ ] Mandatory for GA content:
- [x ] Add steps and/or other important conceptual information here:
There will be a new to prevent OLM from upgrading ACM when the MCH is in the middle of an upgrade. This is done using the operatorcondition resource. The user can check whether ACM is able to be upgraded by looking at the status of the operatorcondition (which shares a name with the ACM CSV) in determining whether it's field of "upgradable" is true or false
- [ ] Add Required access level for the user to complete the task here:
- [ ] Add verification at the end of the task, how does the user verify success (a command to run or a result to see?)
- [ ] Add link to dev story here:
https://issues.redhat.com/browse/ACM-3319?filter=-1
- Errata release note version, this is NOT for regular refreshes:
(published with Errata release)
- [ ] ACM 2.4.x
- [ ] ACM 2.5.x
- [ ] ACM 2.6.x
- [ ] MCE 2.0.x
- [ ] MCE 2.1.x
5. Optional: Get back to issue templates to create more issues for the doc team: https://github.com/open-cluster-management/backlog/issues/new/choose