Document URL: https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#securing-the-registry Section Number and Name: 2.6.6 Securing the Registry Describe the issue: After having secured several registries on my own, I have noticed that every time I get to step 8, which does nothing more than validate step 7, we indicate that the user should run `oc log <name_of_docker_registry_pod>` and every time it returns the message below: log is DEPRECATED and will be removed in a future version. Use logs instead. Suggestions for improvement: Simply add an s to the command so that we are not perpetuating the usage of `oc log` when we plan to remove it at some point.
https://github.com/openshift/openshift-docs/pull/1530 @Eric - Please review my edits and let me know if this satisfies your request. Thanks!
@Ashley Yup that was the only one that I was able to find, and that is the simple change that was necessary. Thanks for fixing it!
@Eric Yeah, this was the only instance I was able to find as well. Thanks!
Commits pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/7af59d9091ee259ab926a7be4f942950c17454a0 Bug 1303159, changed oc log to oc logs https://github.com/openshift/openshift-docs/commit/cb414eadfe37bb8648b962a77702f6a30c22691d Merge pull request #1530 from ahardin-rh/oc-log Bug 1303159, changed oc log to oc logs
Content is published: https://docs.openshift.com/enterprise/3.1/install_config/install/docker_registry.html#viewing-logs https://access.redhat.com/documentation/en/openshift-enterprise/version-3.1/installation-and-configuration/#viewing-logs