Managing Stateful Apps with the Operator Pattern; Orchestration Considerations

December 6, 2018

(This blog is the fourth installment of a four-part series) The Operator Pattern The Operator Pattern stipulates a process that is registered with the Kubernetes system layer, listening to Kubernetes system events with the responsibility to manage a particular set of resources. All the logic that initializes and maintains a service is thereby encapsulated into a Kubernetes deployment, which we’ll call the “Operator” hereafter. This pattern aligns with many of the requirements for stateful apps, so the Operator Pattern is a popular implementation choice.

Previous
Provisioning Stateful Kubernetes Containers that Work Hard and Stay Alive
Provisioning Stateful Kubernetes Containers that Work Hard and Stay Alive

(This blog is the second installment of a four-part series) By default, all containers are free from limits...

Next
Stateful Apps in Kubernetes
Stateful Apps in Kubernetes

Kubernetes is available across all public clouds nowadays, including Pivotal’s own PKS, which runs in the c...