Kubernetes Borg/Omega history topic 5: Asynchronous controllers. Borgmaster had synchronous, transactional, edge-triggered state machines. We had challenges scaling, evolving, and extending them.
Show this thread
-
The spec vs status thing was always there from the start. It was just called desiredstate vs currentstate in early versions of the API. I never intended these to have the same schema. This was a big lesson learned from the GCE API.
In the pre-released code, only Task (which became Pod) had CurrentState, which was indeed the same schema as DesiredState. The other resource types did not. So the intended pattern wasn't obvious to others working on the codebase. And GET called out to Kubelet.
-
-
Yeah. The kubelet flow was inconsistent. Wish I had that original API design doc. Don't remember what we had specd back then at this point.
-
I think I found the doc you're referring to. It has spec and status as completely separate objects, with different schemas. It appears to be talking about a combined replica set & pod hybrid.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.