Bug 1375034 - [DOCS] Missed configuration explanation for Satellite or other mirror registry
Summary: [DOCS] Missed configuration explanation for Satellite or other mirror registry
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Brandi Munilla
QA Contact: Johnny Liu
Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-12 01:35 UTC by Kenjiro Nakayama
Modified: 2019-12-16 06:43 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-18 17:50:15 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Kenjiro Nakayama 2016-09-12 01:35:46 UTC
Document URL: 

  https://docs.openshift.com/enterprise/3.2/install_config/install/disconnected_install.html#overview

  or other new section as title "Using millar registry outside of registry.access.redhat.com"

Describe the issue:

  To specify Satelite or other millar registry, users need to specify "oreg_url", "openshift_examples_modify_imagestreams" and "openshift_docker_additional_registries" during the installation.

  (As for "oreg_url" and "openshift_examples_modify_imagestreams", please see also[1])

Suggestions for improvement: 

  Documentation should mention that how to specify Satelite or other millar registry, as far as I researched, three variables "oreg_url", "openshift_examples_modify_imagestreams" and "openshift_docker_additional_registries".

Additional information: 

  https://bugzilla.redhat.com/show_bug.cgi?id=1374890

Comment 1 Kenjiro Nakayama 2016-09-12 02:02:29 UTC
I'm sorry for my typo. "millar->mirror"

Comment 6 Johnny Liu 2017-06-06 06:39:58 UTC
Beside specify "oreg_url" and "openshift_examples_modify_imagestreams" to use a mirror registry, we also need specify "openshift_docker_additional_registries" and "openshift_docker_insecure_registries", especially "openshift_docker_insecure_registries". But I did not see that is mentioned in the PR.

Comment 7 Kenjiro Nakayama 2017-06-07 06:23:45 UTC
If the mirror registry is secured registry, openshift_docker_insecure_registries would be necessary. However, It is not mandatory, for example when server side is NOT secured registry, or when client side installed cert corectory.

So, how about adding side-note like:

~~~
note: Depends on your requirement, other options such as openshift_docker_insecure_registries or openshift_docker_additional_registries might be worth to configure.
~~~

(Sorry Brandi, please correct my bad English...)

> Jonny,

Do you have an objection or any other idea?

Comment 8 Johnny Liu 2017-06-08 03:33:33 UTC
> > Jonny,
> 
> Do you have an objection or any other idea?

Looks good to me.

Comment 11 Brandi Munilla 2017-06-26 20:16:42 UTC
Thanks! 

I updated the PR. Could you help me clarify the purpose statements for `openshift_docker_additional_registries` and `openshift_docker_insecure_registries`?

Comment 12 Johnny Liu 2017-06-27 03:49:16 UTC
Once set openshift_docker_additional_registries, its value will be added into "ADD_REGISTRY" line in /etc/sysconfig/docker, here I will reference the explanation for "ADD_REGISTRY".

# If you want to add your own registry to be used for docker search and docker
# pull use the ADD_REGISTRY option to list a set of registries, each prepended
# with --add-registry flag. The first registry added will be the first registry
# searched.
ADD_REGISTRY='--add-registry registry.access.redhat.com --add-registry example.com'


Once set openshift_docker_insecure_registries, its value will be added into "INSECURE_REGISTRY" line in /etc/sysconfig/docker, here I will reference the explanation for "INSECURE_REGISTRY".

# If you have a registry secured with https but do not have proper certs
# distributed, you can tell docker to not look for full authorization by
# adding the registry to the INSECURE_REGISTRY line and uncommenting it.
INSECURE_REGISTRY='--insecure-registry example.com'

Comment 13 Brandi Munilla 2017-06-27 20:32:31 UTC
Thank you! I updated the PR with the explanations.

Comment 14 Johnny Liu 2017-06-28 15:14:10 UTC
Seem good to me now.

Comment 15 openshift-github-bot 2017-07-06 15:14:26 UTC
Commits pushed to master at https://github.com/openshift/openshift-docs

https://github.com/openshift/openshift-docs/commit/6a969faa8f2125da2bc48b039a9dcef1398f3612
Bug 1375034 Added Configuring a Regsitry Location

https://github.com/openshift/openshift-docs/commit/74696b1f0b45be7022a343a05a963cd574a4ebe3
Merge pull request #4466 from bmcelvee/BZ1375034

Bug 1375034 Added Configuring a Regsitry Location


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