Added Docker caching support for CoreOS-based cluster. #4378
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@thockin next step would be to get the same behavior in the "official way to bootstrap a cluster". Pointers where I should look at? |
|
This seems reasonable for CoreOS clusters. We already install a cache for GCE based clusters. We can use that as a model for other cloud providers. |
|
I would be interested in the same support being an optional add-on for salt based environments. |
|
@brendanburns @derekwaynecarr yes, I'd like to add this as an optional add-on for salted clusters. Some pointers would be great :-) |
|
@thockin are you the best person to assign this to? |
|
an update to this PR can be seen in #5254. (basically it comes from AntonioMeireles/kubernetes-vagrant-coreos-cluster) |
AntonioMeireles
added a commit
to AntonioMeireles/kubernetes
that referenced
this pull request
Mar 13, 2015
a more idiomatic take on kubernetes#4378. as a bonus, and to be nice on resources, an ultra lightweight docker-registry container is consumed. Signed-off-by: António Meireles <antonio.meireles@reformi.st>
rootfs
pushed a commit
to rootfs/kubernetes
that referenced
this pull request
Mar 13, 2015
a more idiomatic take on kubernetes#4378. as a bonus, and to be nice on resources, an ultra lightweight docker-registry container is consumed. Signed-off-by: António Meireles <antonio.meireles@reformi.st>
|
#5254 was merged. Closing. |
akram
pushed a commit
to akram/kubernetes
that referenced
this pull request
Apr 7, 2015
a more idiomatic take on kubernetes#4378. as a bonus, and to be nice on resources, an ultra lightweight docker-registry container is consumed. Signed-off-by: António Meireles <antonio.meireles@reformi.st>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is meant primarily to speed-up Docker images (re)download across a Kubernetes cluster that sits on top of CoreOS nodes.
In the future, this can trivially evolve to a combo of private registry and mirror of public registry.
docker-registrywill run on master node withmirroringconfigured. Minions will rundockerwith mirror set to the registry running in the master.