-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[enterprise-4.4] Issue in file updating/updating-restricted-network-cluster.adoc #24812
Comments
@wking, will you remind me what the best way to get the SHA for a particular release is? |
#19266 covers getting a digest for a given release. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Which section(s) is the issue in?
https://docs.openshift.com/container-platform/4.4/updating/updating-restricted-network-cluster.html#update-oc-configmap-signature-verification_updating-restricted-network-cluster
The same also applies to the equivalent page in the Openshift 4.5 documentation at;
https://docs.openshift.com/container-platform/4.5/updating/updating-restricted-network-cluster.html#update-oc-configmap-signature-verification_updating-restricted-network-cluster
What needs fixing?
The instructions in step 1 of the Procedure state;
Upon following the link to mirror.openshift.com, the user is presented with a lengthy list of files, and absolutely NO idea which one to select.
The instructions leading up to this step should include specific guidance on how to figure out which one of those signature files to select.
The text was updated successfully, but these errors were encountered: