Bug 1296605 - [SME] registry deployment documentation missing update/delete and missing service account info
[SME] registry deployment documentation missing update/delete and missing ser...
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation (Show other bugs)
3.1.0
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Vikram Goyal
Vikram Goyal
Vikram Goyal
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-07 11:10 EST by Josh Preston
Modified: 2016-01-07 11:10 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh Preston 2016-01-07 11:10:17 EST
Document URL: 

Section Number and Name: 

Section 2.5.1 Overview
Section 2.5.2 Deploying the Registry

Describe the issue: 

After jacking up my registry because I created the registry user as described in 2.5.1 Overview and following 2.5.2 Deploying the Registry section, I required a reinstall.  However, it is not intuitive how to remove a registry that was deployed with oadm registry …

Suggestions for improvement: 

The docs should include some reference to redeploying / removing a registry.  This was actually solved by performing an oc delete|create, but it would be better if it were in the original ‘oadm registry’ command:

‘oadm registry … -o yaml | oc delete -f -’
‘oadm registry … -o yaml | oc create -f -’

Section 2.5.1 Overview, should use 'registry' not 'reguser' for the registry!

Section 2.5.2 Deploying the Registry, should include the “--service-account=registry” as listed in Section 2.5.1, because following the directions creates a registry that does not utilize a service account.

Additional information: 

Documentation aside, we should include some sort of --update or --delete option to either give me the option to update a previously deployed registry or delete it so I can start over.

Note You need to log in before you can comment on or make changes to this bug.