|
|
|
|
|
|
by leetbulb
3722 days ago
|
|
|
I do! The hardware layer consists of physical machines running XenServer. Networking layer is 1Gbit WAN interfaces and 10Gbit LAN interfaces on "virtual switches" all wired together with pfSense. Gitlab-CI takes care of deploying just about all of the fabric on top of that including the images and app / system components / resources. Ingress is currently being overhauled, but right now it's essentially exposed HAProxy (pfSense) on top of dedicated, HA ingress VM's. Oh and it's all CoreOS. We're running three sites on it each with dev environments. Maybe a couple random API's, too. I haven't looked through all of the namespaces in a bit. 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... |
|
|