Introduction
Kubernetes Resource Modeling is the technique of building declarative APIs in the style of the APIs provided by the core Kubernetes Platform. There are expectations and conventions that are assumed throughout the Kubernetes API that allow tooling and automation to be built around it because it is consistent.
The declarative aspect of the API comes with the assumption that the user’s request will be continually monitored and fulfilled as other factors in the environment change. This is one reason why Kubernetes has gained as much traction as it has over the last several years: less stable code can provide a much higher level of reliability than it would otherwise be able to. The Kuberetes platform actively monitors and reacts to application failures, scale changes, and config updates.
This is relevant today because companies are now starting to enable their developer and operation teams to start attempting to build their own platforms for their own applications and finding a catered source of information for this topic is impossible. There are good resources but they are scattered across many media types and don’t tend to be in-depth enough to help when the work gets hard.