My team at Zendesk look after around 30 Kubernetes clusters. These are all self managed, meaning we maintain the API servers, and as you may guess: etcd.

Recently, I had a task to do some performance analysis on our etcd clusters. It had been a while since we ran any sort of benchmarking. Plus I wanted to get my hands dirty as I haven’t got much experience in tuning databases.

While I ended up getting about a 30% increase in performance, I learnt a lot about how databases, and by extension; how disks work together.

CoreDNS is a DNS add-on for Kubernetes environments. It is one of the components running in the control plane nodes, and having it fully operational and responsive is key for the proper functioning of Kubernetes clusters. Learning how to monitor CoreDNS, and what its most important metrics are, is a must for operations teams.

We’ve all done it — deleted a graph from a dashboard, realised we still need it but have forgotten the query. Use Terraform to go back in time and save yourself the headache

The greatest irony is that DevOps aimed to help developers talk with operations, and vice versa, yet developers are even further away from understanding how their code operates at runtime.

Regardless of the replication mechanism you must fsync() your data to prevent global data loss in non-Byzantine protocols.

snips.sh is a free, anonymous, open source, snippet hosting service

TL;DR: in this article, you will learn how ClusterIP services and kube-proxy work in Kubernetes.