Bug 1994420
| Summary: | Include hyperlinks to Red Hat upgrade labs from the OpenShift upgrade documentation | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jatan Malde <jmalde> |
| Component: | Documentation | Assignee: | Samantha Gidlow <sagidlow> |
| Status: | CLOSED WONTFIX | QA Contact: | liujia <jiajliu> |
| Severity: | high | Docs Contact: | Vikram Goyal <vigoyal> |
| Priority: | unspecified | ||
| Version: | 4.8 | CC: | aos-bugs, jokerman, sagidlow, wking, xtian |
| Target Milestone: | --- | Flags: | jiajliu:
needinfo-
jiajliu: needinfo- |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-08-30 13:10:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Jatan Malde
2021-08-17 08:59:36 UTC
We do link the labs page from the mirroring doc: $ git --no-pager grep access.redhat.com/labs/ocpupgradegraph modules/update-mirror-repository.adoc:. Use the link:https://access.redhat.com/labs/ocpupgradegraph/update_channel[Red Hat {product-title} Upgrade Graph visualizer and update planner] to plan an upgrade from one version to another. The OpenShift Upgrade Graph provides channel graphs and a way to confirm that there is an update path between your current and intended cluster versions. But that's a use-case that lacks an alternative, convenient UX for Cincinnati/Update-Service update recommendations. There is some existing discussion in [1], where I could see a link to the labs page being helpful for folks getting a clearer picture. But oc and the web console exposing the next-hop available updates are ideally sufficient for most cluster-admin-driving-a-cluster use-cases, and if they aren't there should be a product RFE around closing that gap. Because in-cluster tools will help admins regardless of the upstream service they're using, while the labs page will only help folks using the central Red-Hat-hosted Update Service, and will miss future cluster-specific things like phased rollouts [2] or targeted edge blocking [3]. [1]: https://docs.openshift.com/container-platform/4.8/updating/updating-cluster.html#upgrade-version-paths [2]: https://github.com/openshift/enhancements/pull/427 [3]: https://github.com/openshift/enhancements/pull/821 AFAIK, https://access.redhat.com/labs/ocpupgradegraph/update_channel is an out-of-cluster tool. From QE side, the link is not needed anywhere. I left more comments in above pr too. |