Kubernetes Patterns : The Stateful Service Pattern

twitter logo ・1 min read

Kubernetes Patterns (8 Part Series)

1) Kubernetes Patterns : The DaemonService Pattern 2) Kubernetes Patterns : The Stateful Service Pattern 3 ... 6 3) Kubernetes Patterns : The Stateful Service Pattern 4) Kubernetes Patterns : The Stateful Service Pattern 5) Kubernetes Patterns : The Cron Job Pattern 6) Kubernetes Patterns - The Batch Job Pattern 7) Kubernetes Patterns : The Reflection Pattern 8) Kubernetes Patterns : The Ambassador Pattern

Stable Network Identity.
If you have a pet, you must give it a name so that you can call it. Similarly, a stateful application node must have a well-defined hostname and IP address so that other nodes in the same application knows how to reach it. A ReplicaSet does not offer this functionality as each Pod receives a random hostname and IP address when it starts or is restarted. In stateless applications, we use a Service that load-balances the Pods behind it and offers a URL through which you can reach any of the stateless Pods. In a stateful app, each node may want to connect to a specific node. A ReplicaSet cannot serve this purpose.
Learn more about Kubernetes Stateful Service Patterns: https://www.magalix.com/blog/kubernetes-patterns-the-stateful-service-pattern

twitter logo DISCUSS
Classic DEV Post from Nov 7

What Are the Most Important CS Principles to Learn as a New Dev from a Non-Traditional Background?

Ahmed Atef profile image