-
Bug
-
Resolution: Done
-
Minor
-
rhos-18.0.7
-
3
-
False
-
-
False
-
?
-
rhos-workloads-evolution
-
None
-
-
-
Workload Evolution Sprint 3, Workload Evolution Sprint 4
-
2
-
Low
Procedure provided in "Creating the Optimize service in an existing RHOSO control plane" section of "Optimizing infrastructure resource utilization" guide will benefit from second look:
- steps are not ordered: first two steps for watcher.yaml; next three steps are for watcher-certificates.yaml, then remaining steps are for watcher.yaml. It could be useful to create certificates first, then focus on watcher instance
- it may be useful to refactor steps for watcher-certificates.yaml: on step 3 guide provides an overview for certificates that will be created, but overview is not structured (for example, certificate name is only provided for watcher-public-route, while we will check all certificate names at step 5). On top of that, we provide some recommendations for watcher-public-route definition: to choose proper project and to set proper domain. Later we will repeat recommendation to set proper project in step 4, but will not repeat recommendation to set proper domain.
- in code block in step 2 we use bold font to highlight definitions that should be modified, but we don't use similar approach in other code blocks;
- in watcher.yaml code blocks attached to steps 2 and 6 we use ellipsis at the end to highlight its WIP status. It looks like final form is not provided at the end;