Posted on Wednesday February 1, 2017

.NET Core continous integration and deployment with Gitlab, Docker, Kubernetes and Google Cloud

Over the past few months I’ve put Roadkill on hold in my free time, to get some .NET core projects working inside Docker. They’re mostly sandbox websites for exploring the tech stack, and are hosted privately in Gitlab. Gitlab gives you a decent CI server for free, which works really well with CI and deployment of .NET core apps (both websites and console apps).

How the build works

As .NET core runs in Linux, you no longer have to worry about spinning up an over-powered Windows server. What’s more you can do it all inside a Docker container. I plan to do a series of posts on my learnings with .NET core and Kubernetes, in the meantime below is the YAML build definition build I used. It does the following:

  1. Build and publish (publish is just creating a clean bin folder with assets) the .NET Core app in release mode
  2. Build the Docker image in the repository: docker build -t
  3. The tag I use for each Docker image is the short Git commit ID.
  4. Finally push to the Google Cloud Docker registry.

One final step you could easily add is performing a kubectl edit deployments/... to update the Docker image to the latest tag, but it’s not in the YAML build definition file.

What does the app do?

The app has a website, and then a Google Cloud Pub/Sub part that is used for updating data that the website uses periodically. The Pub/Sub part is a publisher and a poller-based subscriber. I tried using push but Google Cloud had a habit of denial of servicing my endpoint, even with throttling enabled inside Nginx.

All three bits are Docker containers running as seperate pods inside a Kubernetes cluster.

How can I change the file so it works with Bitbucket Pipelines/Travis/Appveyor/CI-service XYZ

You could convert it really easily to another build service YAML format. Appveyor wouldn’t make much sense, but other services would be trivial to do.