Updated on 2019-12-06: Added a GitOps Diagram.

Running this blog on Kubernetes. The question is … why?

There are a few reasons for this.

  1. Getting more hands on experience
  2. Eating your own dog food (I recommend it to my Partners where it makes sense, why wouldn’t I use it then ?)

One question that I get all of the time: isn’t this just overkill ? Yes, potentially, but look at points 1) and 2). For me, this ties really well with my learning objectives - and really, this is how I retain knowledge the best. You can read all you want on this topic (or any topic) but watching Julia Child’s cooking does not make me a good cooker, right ? ;)

How is this blog setup ?

Mostly, this is an experiment around GitOps.

For that, I’m using the following:

  • Hugo as the blog engine
  • Source code lives in my github repo: https://github.com/dcasati/dcasati.net
  • Github Actions for the CI
  • FluxCD
  • Cluster running in Azure (Azure Kubernetes Services)
  • Images are pushed into a private repository (Azure Container Registry)

I will blog about how this blog came to be as well. This is how it looks like.

gitops