3 ms·
Disclaimer: I work for Red Hat on OpenShift v3, an open-source enterprise-ready distribution of Kubernetes. We have solved #2 by deploying an internal docker r
by xkarga00 10y ago
Disclaimer: I work for Red Hat on OpenShift v3, an open-source enterprise-ready distribution of Kubernetes.
We have solved #2 by deploying an internal docker registry [1], push to it once a build succeeds, and automatically (or not) trigger deployments once an expected image lands in it [2].
In the future we will support webhooks so you can trigger deployments from external registries such as quay.io or DockerHub.
You can have a look at the all-in-one VM we have:
git clone https://github.com/openshift/origin https://github.com/openshift/origin
cd origin
vagrant up
vagrant ssh
oc cluster up
The last command will spin up a cluster with a docker registry, a HTTP router, and a bunch of images for you to play around with.
https://asciinema.org/a/49402 https://asciinema.org/a/49402
[1] The same underlying registry thay powers DockerHub: https://github.com/docker/distribution https://github.com/docker/distribution
[2] A Kubernetes controller loop that watches for new images and triggers new deployments.