OpenShift Registry Operations: Difference between revisions
| Line 19: | Line 19: | ||
oc project <''project-name''> | oc project <''project-name''> | ||
If you intend to use "registry" as service account, it will be created by default by the registry creation procedure. Otherwise [[OpenShift_Security_Operations#Create_a_New_Service_Account|create the desired service account]]. | |||
If the current context was changed to contain a different project than "default", for the account used to execute [[oadm]], restore the "default" project context: | If the current context was changed to contain a different project than "default", for the account used to execute [[oadm]], restore the "default" project context: | ||
Revision as of 00:58, 19 October 2017
External
- https://docs.openshift.com/container-platform/3.6/install_config/registry/deploy_registry_existing_clusters.html
- https://docs.openshift.com/container-platform/3.6/install_config/install/stand_alone_registry.html#install-config-installing-stand-alone-registry
Internal
Overview
Deploy a Registry
Normally, this is not required as the standard installation procedure installs an integrated registry as part of the "default" project. In case the registry was not installed as part of the procedure, or we want to deploy a registry dedicated to a project, use the following procedure.
If the registry needs to be deployed into a project other than "default", change the current context by running oc project from the same account used to run oadm:
oc project <project-name>
If you intend to use "registry" as service account, it will be created by default by the registry creation procedure. Otherwise create the desired service account.
If the current context was changed to contain a different project than "default", for the account used to execute oadm, restore the "default" project context:
oc project default