The document discusses the difference between stateful and stateless applications, highlighting how stateful services track sessions while stateless services do not. It introduces StatefulSets as an API object used to manage stateful applications, providing guarantees about pod ordering and uniqueness. Additionally, it outlines the limitations of traditional deployments regarding pod management and identity.

1. S T A T E F U L S E T S
W H A T , W H Y , H O W ?

2. Stateful and Stateless applications
01
We have Deployments, then what's the issue?
02
What are StatefulSets?
03
Demo
04
T O D A Y ' S A G E N D A

3. Stateful services keep track of sessions or transactions and
perform operations based on that history.
Stateless services don't keep the state of the previous
session.
S T A T E F U L & S T A T E L E S S

4. S T A T E F U L & S T A T E L E S S

5. W E H A V E D E P L O Y M E N T S ,
T H E N W H Y ? ?
A Deployment provides declarative updates
for Pods and ReplicaSets.
Deployments create pods with the random hash attached
to its name ( no persistent name)
Deletion of pods will be done randomly, so can't trust the
connection using their DNS name.
Each Pod shares the same PV
Ungraceful termination

6. S T A T E F U L S E T S
StatefulSet is the workload API object used to manage stateful
applications.
Manages the deployment and scaling of a set of Pods, and provides
guarantees about the ordering and uniqueness of these Pods.
Creates and terminates Pods one by one
Every Pod has an Persistent Identity
Each pod has saparate PV

7. D E M O
h t t p s : / / g i t h u b . c o m / k a r n a t i s r i n i v a s / D o k - S t a t e f u l S e t s

8. E-mail srinivas@srinivaskarnati.in
Twitter twitter.com/__karnati
T H A N K Y O U
Linkedin linkedin.in/in/srinivas-karnati