Bug 1402550 - [DOCS] Securing registry instructions incorrect
Summary: [DOCS] Securing registry instructions incorrect
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.3.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Ashley Hardin
QA Contact: ge liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-07 19:32 UTC by Matthew Whitehead
Modified: 2017-07-20 20:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-20 20:35:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Matthew Whitehead 2016-12-07 19:32:40 UTC 
Document URL: https://docs.openshift.com/container-platform/3.3/install_config/registry/securing_and_exposing_registry.html#securing-the-registry

Section Number and Name: "Securing the Registry"

Describe the issue: Step 8 (and probably step 9) do not work. I had to do an 'oc edit' as a workaround.

$ oc patch dc/docker-registry --api-version=v1 -p '{"spec": {"template": {"spec": {"containers":[{
    "name":"registry",
    "livenessProbe":  {"httpGet": {"scheme":"HTTPS"}}
  }]}}}}'

Suggestions for improvement: 

Additional information:
Comment 2 Ashley Hardin 2017-07-14 21:17:02 UTC 
Hi, Matthew.
Can you please provide me more details on this so that I can update the steps? 

1. What kind of error did you get?
2. Did you just substitute oc patch with oc edit to resolve the issue? 

Thanks!
Comment 3 Matthew Whitehead 2017-07-14 22:01:35 UTC 
I switched to version 3.5 and that documentation works. I am not able to switch back to 3.3.
Comment 4 Ashley Hardin 2017-07-20 17:39:19 UTC 
Looks like the docs for 3.3 now match what is there for 3.5, so I am closing this since we confirmed that the 3.5 docs provide accurate guidance.
Comment 8 Ashley Hardin 2017-07-20 20:35:57 UTC 
Okay, thanks.
Note You need to log in before you can comment on or make changes to this bug.