2 ms·
It should be named Open Kubernetes Application Model. If I'm understanding correctly, it should be "portable" to other orchestrators or even bare metal. However
by withinboredom 6y ago
It should be named Open Kubernetes Application Model. If I'm understanding correctly, it should be "portable" to other orchestrators or even bare metal. However, it seems to be quite leaky of the underlying Kubernetes stuff.
- rektide 6y agoYeah, well, survival instinct. They could never compete in a void. They need to borrow/interop with what everyone already enjoys.
- resouer 6y agoReusing Kubernetes Resource Model to build app-centric platform have many benefits: 1. Work seamlessly with any CI CD solutions which work with Kubernetes. 2. Clarity in api versions in the spec entity. 3. Adopt widely used best practices such as metadata, spec & status. Overall, we should be aware that the complexity of Kubernetes does NOT lie in its api model (Group, Version, Kind etc). Also, an abstraction adopts this model does not leak anything in underlying Kubernetes runtime.