News for hackers. Stuff that matters.
Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by cpitman on Thursday March 17, 2016 @05:06PM (#11307611)
Yes, I've been following that! GitLab Deploy is also looking like it could be exciting. I was disappointed though that the merge request that added Kubernetes support to the GitLab CI MultiRunner was rejected. Right now Jenkins is usually the default choice for our customers that use OpenShift, but being able to dynamically provision testing containers would be an amazing feature.
Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by sytse on Thursday March 17, 2016 @05:35PM (#11307805)
Glad to hear you're following that. Can you link to the Kubernetes merge request? I think it introduced too many dependencies but I'm happy to have another look.
Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by cpitman on Thursday March 17, 2016 @05:43PM (#11307861)
Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by sytse on Thursday March 17, 2016 @06:03PM (#11307996)
Thanks! It was closed in favor of autoscaling with Docker Machine https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_r... it seems that Docker Machine doesn't support Kubernetes https://github.com/docker/machine/tree/master/drivers

https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_r... introduces many dependencies. Not sure how to solve it. Maybe something like https://github.com/deric/gitlab-ci-mesos ?

Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by sytse on Thursday March 17, 2016 @06:55PM (#11308319)
Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by ayufan on Thursday March 17, 2016 @05:29PM (#11307767)
You shouldn't be. Executing builds on Kubernetes is not the same as deploying an application :) We will solve that need with plugins :)

GitLab CI Lead

Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by cpitman on Thursday March 17, 2016 @05:49PM (#11307898)
That would be great, I'm not married to the implementation as much as the convenience of using the cluster manager we already have (kubernetes) to distribute builds.

I currently am using a VM with a docker runner, and there are two (somewhat obvious) issues:

* It requires root access to the machine to be able to spin up containers

* Every VM with a docker runner needs enough storage to handle every docker image used for builds, instead of centralizing the images. I really need to put in a cron job or something to clean these up.

Kubernetes should fix both of these, without introducing another technology in our environment like Docker Machine.

Re:IaaS vs. PaaS vs. CaaS  – Which Cloud Architecture Is Rig... by ayufan on Thursday March 17, 2016 @06:05PM (#11308006)
I understand your reasoning.

At this point it doesn't make sense to introduce support for another clustering manager. The GitLab Runner does support docker-machine (you can pretty easily configure it to create machines on-demand on any cloud provider). These machines will be pretty much self-managed. Soon the Runner will be also compatible with Docker Swarm, the implementation is already on separate branch.

From my perspective Kubernetes is great as platform for deploying applications, but I'm not so sure if it comes for distributing builds.

The problem with cleaning old images and caches is also addressed. You may be interested in checking out this application: https://gitlab.com/gitlab-org/gitlab-runner-docker-cleanup

What is important that GitLab Runner is being constantly improved and at some point with more convincing (for example coming from You) we can get back to native Kubernetes executor :)

GitLab CI Lead