Resources following the KRMA framework used in Kubernetes to define and manage the various entities or resources.
pattern describes the desired states (or digital twinsA virtual representation of a physical object, system, or process that is continuously updated with real-time or near-real-time data to mirror its real-world counterpart.
) of real-world elements, which are controlled by actuatorsControllers that map real-world capabilities into the virtual-world.
. They read the desired state from the resourceA document defining the desired state of a capability and capturing its actual state. See also Kubernetes Resource Model (KRM).
and the actual state from the real-world.
The actuator then aligns the actual state according to the described desired state. This means that changes on both sides may trigger modification operations on the real-world side (even if the desired state has not been modified).
This is in stark contrast to imperative REST APIs. The KRMA framework used in Kubernetes to define and manage the various entities or resources.
does not foresee issuing explicit operations to mutate the real world. The executed operations are completely determined by the discovered delta between the desired and actual state. At the same time a projection of the real-world is reported back to the respective resources, making the real-world observable by means of the KRM's control plane.
Actuators work in a bi-directional manner with the common, shared repository.
The term real-world element is used in a very abstract manner. It does not necessarily mean that the elements correlated to actuatorsControllers that map real-world capabilities into the virtual-world.
and resourcesA document defining the desired state of a capability and capturing its actual state. See also Kubernetes Resource Model (KRM).
in the KRM are physical objects, or even exist outside the control plane. Those elements might just be "virtual" resources. Residing in the same or even another control plane.
The KRMA framework used in Kubernetes to define and manage the various entities or resources.
may be cascaded, resources may be used to create and manipulate other resources, which again may cascade to more resources (it is even not necessary, that there is a real-world element at the end of the chain).
For example, in Kubernetes a Deployment resource orchestrates a ReplicaSet resource, both of which are useful higher-level virtual-only abstractions. ReplicaSet further orchestrates a Pod resource, which finally spawns a real-world set of containers.