Bug 1878830
| Summary: | The flow under "Mirroring the OpenShift Container Platform image repository" is confusing | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Frederic Giloux <fgiloux> |
| Component: | Documentation | Assignee: | Brandi Munilla <bmcelvee> |
| Status: | CLOSED EOL | QA Contact: | Johnny Liu <jialiu> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 4.6 | CC: | aos-bugs, bmcelvee, jialiu, wking, wzheng |
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-09-09 14:13:44 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
Frederic Giloux
2020-09-14 15:34:51 UTC
Raised bug 1878972 to clarify whether the removal of the architecture information is desired or not Discussing with QE, dev suggested that release images should be consumed via sha256 hash instead of tag names, which is not the way described in the documentation. [1] has been recently revived to move away from tags and towards by-digest pullspecs, which will address that portion of this ticket. I'm also still pretty sure we don't actually need the locally-extracted installer, we just don't have CI to prove that yet. I will look into reviving [2]. [1]: https://github.com/openshift/openshift-docs/pull/19266 [2]: https://github.com/openshift/release/pull/5567 > [1] has been recently revived to move away from tags and towards by-digest pullspecs, which will address that portion of this ticket. +1, Once that, doc will does not need `${OCP_RELEASE}-${ARCHITECTURE}` tag name any more. QE already switch our internal testing to using digest instead of tag name. > I'm also still pretty sure we don't actually need the locally-extracted installer, we just don't have CI to prove that yet. I will look into reviving [2]. Per my understanding, if user do not need the locally-extracted installer, user still need to download oc binary from internet which is aligned with target release payload image which user want to install, then move it to Intranet where installation will begin. OCP 4.6 is no longer on full support [1]. Marking this bug as CLOSED EOL. If you have a customer case with a support exception or if you think this issue still applies on 4.8+, please reopen and include those details or open a new Jira issue [2] with updated information. When reopening, please set the Target Release to the appropriate version where needed. [1]: https://access.redhat.com/support/policy/updates/openshift [2]: https://issues.redhat.com/projects/OCPBUGS |