by the_gigi on 4/6/16, 11:16 PM with 14 comments
by leetbulb on 4/7/16, 1:14 AM
Edit: Gitlab-CI runners run on kubernetes as well using the dind images. Ingress nodes will soon be given public IP's. Public IP's are currently on CARP failover. After the gitlab-ci-multi-runner 1.1.1 release (allowing shared artifacts) and Kubernetes Deployment resources (providing a way easier deployment workflow and orchestration of pods), CI/CD is a breeze. We have dedicated nodes for MySQL (PXC) and ZooKeeper because these don't play well in the Kubernetes network environment - don't ask me to look at the examples ;) Currently running with Flannel for the overlay, but we're evaluating Calico and waiting on new Docker features to pull the trigger on something else... Multicast, isolated namespaces, VLAN's would be awesome :)
Edit2: I don't know why I keep saying "we" ... I've built and run this thing solo on top of programming... Not enough hours in a day...
by AkihiroSuda on 4/7/16, 1:14 AM
by chews on 4/7/16, 2:46 AM
by techthumb on 4/7/16, 3:16 AM
by hijinks on 4/7/16, 3:31 AM
AWS with kubernetes 1.2.1 and calico as the overlay network. We have all our web apps in kubernetes and working on our background job apps next.
by TheIronYuppie on 4/7/16, 4:10 AM
Disclosure: I work at Google on Kubernetes.
by nethier on 4/7/16, 3:44 AM
Internal adoption seems to be going well so hopefully this grows.
by cweagans on 4/7/16, 5:36 AM
by yuvipanda on 4/7/16, 3:26 AM
by trungonnews on 4/7/16, 1:22 AM