Here at InVision, we have a unique challenge. We don’t just have a single Kubernetes cluster, but several, all completely independent of each other and all needing automated updates via our CI/CD process. And although these clusters generally run the same code, the configurations differ. Things needed to work smoothly and automatically as we couldn’t afford to add friction to the deploy process or encumber our engineering teams. This led us to building and open sourcing our own continuous deployment solution for Kubernetes that we called kit.
Read more about our experience with Docker, Kubernetes and the tooling we created around multi-cluster deployments on the Kubernetes.io blog!