Kubernetes Borg/Omega history topic 7: The Kubernetes Resource Model: why we (eventually) made it uniform and declarative. A topic even deeper than watch. More details can be found here: https://github.com/kubernetes/community/blob/master/contributors/design-proposals/architecture/resource-management.md …
-
-
For the most part, controllers know which fields to propagate from one resource instance to another and wait gracefully on declarative object (rather than field) references, without assuming referential integrity, which enables relaxed operation ordering.
Show this thread -
There are some gaps in the model (e.g., http://issues.k8s.io/34363 , http://issues.k8s.io/30698 , http://issues.k8s.io/1698 , http://issues.k8s.io/22675 ), but for the most part it facilitates generic operations on arbitrary resource types.
Show this thread -
In the next thread, I’ll cover more about configuration itself, such as the origin of kubectl apply
Show this thread -
BTW, when I was digging through old docs/decks, I found a diagram from the Dec 2013 API proposal. Sunit->Pod, SunitPrototype->PodTemplate, Replicate->ReplicaSet, Autoscale->HorizontalPodAutoscaler.pic.twitter.com/oOd84Lzw3B
Show this thread
End of conversation
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.