Wercker Blog

So before this weekend I'd only setup continuous deployment of a simple Rails app & database to a cluster using CircleCI [0]. This was quite a lot more complicated than I'd have liked and this weekend I thought I'd give wercker and distelli a go (based on seeing this post).

I found the wercker docs a little lacking. The wercker.yml docs in particular felt incomplete [1] - I already know how to write yaml... However, when I looked around a little with the help of Google I found they had some better tutorial style content on their blog and followed this guide [2]. While the guide might be easier to follow basically that was what I needed and I've been able to get one of their sample apps up and running ok on a test cluster.

After this being a little awkward/unclear at times I thought I'd give distelli a go at the same task:

- Nice being able to take containers from different repos

- Good to be able to create clusters but I wasn't able to connect to an existing cluster on GKE.

- Wasn't able to find anything in the documentation [3] (but managed all the same - credit to the UI?)

- Not clear how I create other Kubernetes artefacts (services etc)

- I actually quite like the kubernetes yml file system; distelli seems to abstract this away.

[0]: https://github.com/charlieegan3/kubernetes-examples/blob/master/circle.yml
[1]: http://devcenter.wercker.com/docs/wercker-yml
[2]: http://blog.wercker.com/Deploying-a-Microservice-to-GKE-with-GCR
[3]: http://imgur.com/a/Qdto5

Ansible and Chef are tools that provision your servers. Wercker is a continuous delivery platform that tests, builds and deploys your applications. All of this packaged in an easy to use interface where you can also collaborate with others.

You can leverage tools such as Ansible, Puppet and Chef on wercker to create the environment (a wercker box) that mimics your production system, again to build, test and deploy your app, keeping dev/prod parity in true 12factor fashion:

http://12factor.net/dev-prod-parity

We've written up a post on provisioning wercker boxes which you can deploy to the wercker directory (http://app.wercker.com/#explore) here:

http://blog.wercker.com/2013/08/21/Overview-of-provisioning-boxes.html

Feel free to contact me if you have any questions!

cheers

Thank you. So there is a DNAT to get to the Ingress Controller but from there at least it's direct routing to the service endpoint(s)? Does that mean the Virtual IP given to the Service is basically bypassed when using Ingress Controller?

TLS termination at the Ingress Controller and by default unencrypted from there to the service endpoint?

I found this useful: http://blog.wercker.com/troubleshooting-ingress-kubernetes

Interesting discussion here: https://github.com/kubernetes/ingress/issues/257

It seems like a lot of overhead before even starting to process a request!

Wercker has a post on continous integration for containers to Kubernetes which Micha, their CEO, did back in June: http://blog.wercker.com/2015/06/23/Deploying-minimal-containers-to-kubernetes.html, which uses Google's Container Registry for pushing images.

If anyone is interested, I just wrapped up a similar post for deploying containers to Giant Swarm from Wercker, no Docker required: I just got done doing a continuos integration post for containers using Wercker and Giant Swarm: https://github.com/giantswarm/swarm-wercker.