Skip to content

registry daemonset option #2118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bfallonf merged 1 commit into from
Jun 9, 2016
Merged

registry daemonset option #2118

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions install_config/install/docker_registry.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,6 +78,23 @@ $ oadm registry --help
----
endif::[]

=== Deploying the Registry as a DaemonSet

You may use the `oadm registry` command to deploy the registry as a
link:http://kubernetes.io/docs/admin/daemons/[DaemonSet] with
the `--daemonset` option.

A link:http://kubernetes.io/docs/admin/daemons/[DaemonSet] will run a pod
on every node. For more information on
link:http://kubernetes.io/docs/admin/daemons/[DaemonSets] please see the
link:http://kubernetes.io/docs/admin/daemons/[DaemonSet documentation].

[NOTE]
====
Updating of DaemonSets is still a work in progress.
It is recommended that a DeploymentConfig be used to deploy the registry.
====

ifdef::openshift-enterprise,openshift-origin[]
[[registry-compute-resource]]
=== Registry Compute Resources
Expand Down