Image: smallimprovements/teamcity-agent-docker Here’s an example for our replication controller: Now that you have a three node Kubernetes cluster running, it is time to start-up some containers. In Kubernetes a group of containers and their resources (volumes, ports…) form a pod (as in: a pod of dolphins). To ensure that n pods are always running, you can use a replication controller. Almost anything you do in a Kuberntes cluster you do through kubectl which is hidden under:īy the way, your life will be a bit easier when you setup an alias first:Īlias kubectl='gcloud alpha container kubectl' I recommend using the command line tool gcloud because there are almost no Kubernetes features implemented in the GUI yet.įor our use case we figured two CPU cores should be enough and used a n1‑standard‑2 machine: The setup of a Kubernetes cluster on the Google Cloud Platform is quite easy (and fast as a Google engineer will happily demonstrate) with the Google Cloud Container Engine. So in this post, we’ll show you how to set things up, what pitfalls to avoid, and how we managed to create a robust and easy to set up solution. Although we liked it, we were quite curious how a cluster setup with Kubernetes (K8S if you like) performs. We already experimented with CoreOS for our internal logging system. Since other developers were already unhappy with the fact, that the CI could only be reached from within the office, we took that as an incentive to give building on the Google Cloud Platform a shot. We recently moved to a new office and discovered that one of our bare metal Continuous Integration build agents didn’t survive the move.
0 kommentar(er)
