Thoughts on the Buildkite Aug 25 incident – Surfing Complexity
The other day, I wrote about a GitHub Actions incident. But GitHub Actions isn’t the only CI-as-a-service out there. Buildkite, which is another CI company, recently released a public write-u…
The other day, I wrote about a GitHub Actions incident. But GitHub Actions isn’t the only CI-as-a-service out there. Buildkite, which is another CI company, recently released a public write-up of an incident they experienced last week. It’s a great one: their incident report contains a lot more detail than GitHub’s. Here I’ll discuss my own observations. The failure mode The write-up describes what I found to be a fascinating failure mode. Here I’m going to do my best to explain it in my own words. A bit about Kubernetes First, some Kubernetes terminology to get us all on the same page.…
saved by
related reading
- k8s-1m Overviewbchess.github.io
- Kubernetestheswissbay.ch
- More Than DNS: The 14 hour AWS us-east-1 outage – Jonathon Belotti [thundergolfer]thundergolfer.com
- Kubernetes production readiness checklistlearnk8s.io
- Cluster Architecture | Kuberneteskubernetes.io
- Paul Butler – The hater’s guide to Kubernetespaulbutler.org
- Scaling App Infrastructure with Kubernetes & Microservicesrtinsights.com
- The feedback loops behind Kubernetes — PlanetScaleplanetscale.com
- From bare metal to a 70B model: infrastructure set-up and scripts - Imbueimbue.com
- Kubernetes Exposed: One Yaml away from Disasteraquasec.com
- Deploying R with kubernetes – Notes from a data witchblog.djnavarro.net
- 2410.21680arxiv.org