The Kubernetes project introduces PetSets, a new block management abstraction designed to run stateful applications. This is an alpha feature currently (starting with version 1.4) and is moving fast. A list of different questions when switching to the beta version is presented here . Quote from the section when to use billboards :
PetSet ensures that a certain number of "pets" with unique identifiers will work at any given time. Pet identity consists of:
- stable hostname available in DNS
- ordinal index
- stable storage: associated with serial number and host name
In addition to the above, it can be associated with several other features that help deploy and manage state-supported cluster applications. For example, in combination with dynamic volume backup , it can be used to automatically store storage.
Several YAML configuration files are available (for example, the ones you referenced) using ReplicaSets and Deployments for MySQL and other databases that can be run in production and probably also run this way. However, PetSets is expected to greatly facilitate the execution of these types of workloads by supporting updates, maintenance, scaling, etc.
The following are examples of distributed pet databases here .
The advantage of providing persistent volumes that are network and non-local (such as GlusterFS) is realized on a scale. However, for relatively small clusters, there is a proposal that allows future local storage in the future.
Anirudh ramanathan
source share