Rebuilding Linkerd's continuous integration (CI) with Kubernetes in Docker (kind) and GitHub Actions
This post is a writeup of a talk I gave last month at KubeCon EU 2020. Introduction In mid-2019, the Linkerd project’s continuous integration (CI) took 45 minutes, all tests were serialized on a single Kubernetes cluster, and multi-hour backups were common. A migration onto one-off Kubernetes in Docker (kind) clusters and GitHub Actions got CI below 10 minutes, and made it parallelizable. This post will detail Linkerd’s CI journey from a single, persistent Kubernetes cluster to theoretically unlimited one-off kind clusters.