Reusing 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.
Comments
Reusing 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.