July 21, 2017 | by Stefan Schimanski and Michael Hausenblas Welcome to the second installment of our Kubernetes API Server deep dive series. Last time we, Stefan and Michael, had a look at what the API Server is, introduced the terminology, and discussed how the request flow works. This time around we’ll focus on a topic we only mentioned in passing: Where and how the state of Kubernetes objects i
![Kubernetes Deep Dive: API Server – Part 2](https://cdn-ak-scissors.b.st-hatena.com/image/square/ce76d1e23544e3f4cf4c6f88bcf1135e938d9b76/height=288;version=1;width=512/https%3A%2F%2Fcloud.redhat.com%2Fhubfs%2Fimages%2Fbgs%2FRed-Hat-Hybrid-Cloud_OG_1200x630.png)