Gerenciamento de aplicações com estado usando StatefulSets
Implante e gerencie aplicações com estado, como bancos de dados, usando StatefulSets e garantindo identidades de rede estáveis e armazenamento persistente.
Gerenciamento de aplicações com estado usando StatefulSets é uma aula grátis de Docker & Kubernetes for Developers no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Docker & Kubernetes for Developers, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Docker & Kubernetes for Developers inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
Stateful Applications in K8s
When deploying applications in Kubernetes, some applications are stateless, meaning they don't store data locally and can be easily scaled or replaced.
However, many critical applications, like databases or message queues, are stateful. They need persistent storage and stable network identities.
This lesson introduces StatefulSets, a Kubernetes API object designed specifically to manage these stateful workloads.
Why StatefulSets?
Traditional Kubernetes Deployments are great for stateless apps. They create Pods with arbitrary names and can replace them freely.
Stateful applications, however, require:
- Stable, unique network identities: Each instance needs a consistent name.
- Stable, persistent storage: Data must survive Pod restarts or rescheduling.
- Ordered deployment and scaling: Sometimes, instances need to start or stop in a specific sequence.
StatefulSets provide these crucial capabilities.
Key Features of StatefulSets
StatefulSets offer several powerful features for managing stateful applications:
- Stable Network ID: Each Pod gets a predictable name (e.g.,
web-0,web-1) and DNS hostname. - Stable Persistent Storage: Integrates with Persistent Volumes (PVs) and Persistent Volume Claims (PVCs) to give each Pod its own persistent storage.
- Ordered Guarantees: Ensures Pods are created, scaled, and deleted in a strict, ordinal order.
- Graceful Deployment: Pods are only created after their storage is ready, and only deleted after they've gracefully shut down.
StatefulSet Components
A StatefulSet typically works in conjunction with other Kubernetes resources:
- Headless Service: Provides stable network identities for the Pods. It doesn't load-balance traffic, but creates unique DNS entries for each Pod.
- Pod Template: Defines the specification for the Pods, including containers, resources, etc.
- Volume Claim Templates: Generates a unique Persistent Volume Claim (PVC) for each Pod, ensuring dedicated storage.
Defining a Headless Service
Before creating a StatefulSet, you often define a Headless Service. This service is crucial for assigning stable network identities to your stateful Pods.
Notice clusterIP: None, which tells Kubernetes not to assign a cluster IP, making it 'headless'.
apiVersion: v1
kind: Service
metadata:
name: my-app-service
labels:
app: my-app
spec:
ports:
- port: 80
name: web
clusterIP: None # This makes it a Headless Service
selector:
app: my-appCreating a Basic StatefulSet
Now, let's look at a basic StatefulSet definition. It links to our Headless Service using serviceName and defines a volumeClaimTemplates for persistent storage.
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: my-app
spec:
serviceName: "my-app-service" # Link to Headless Service
replicas: 3
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: my-container
image: nginx
ports:
- containerPort: 80
volumeMounts:
- name: www
mountPath: /usr/share/nginx/html
volumeClaimTemplates:
- metadata:
name: www
spec:
accessModes: [ "ReadWriteOnce" ]
resources:
requests:
storage: 1GiUnderstanding Pod Identity
When the StatefulSet from the previous scene is deployed, it will create three Pods named my-app-0, my-app-1, and my-app-2.
Each Pod also gets its own stable DNS entry, like my-app-0.my-app-service.default.svc.cluster.local. This allows other services to reliably connect to specific instances.
Crucially, each Pod will also get its own unique Persistent Volume Claim (e.g., www-my-app-0), ensuring dedicated storage.
Ordered Deployment & Scaling
StatefulSets enforce a strict order for Pod creation, scaling, and deletion. This is vital for applications where sequence matters (e.g., a primary database and its replicas).
- Creation: Pods are created in ascending ordinal order (
my-app-0, thenmy-app-1, etc.). Each Pod is fully running and ready before the next is created. - Deletion: Pods are terminated in descending ordinal order (
my-app-2, thenmy-app-1, etc.). Each Pod is fully shut down before the next is deleted. - Scaling: Similarly, scaling up adds Pods in order, and scaling down removes them in reverse order.
Updating StatefulSets
StatefulSets support controlled updates to their Pods, typically used for rolling out new versions of your application.
- RollingUpdate (default): Pods are updated in reverse ordinal order (
my-app-2, thenmy-app-1, etc.). Each Pod is updated and ready before the next one starts. - OnDelete: This strategy requires manual intervention. The StatefulSet controller will not automatically update Pods. You must manually delete Pods for the new template to take effect.
Rolling updates ensure minimal downtime and maintain the application's state during upgrades.
StatefulSet Features Check
Which of the following are key characteristics or requirements for Kubernetes StatefulSets?
StatefulSets Recap
Congratulations! You've learned about Kubernetes StatefulSets.
- StatefulSets manage stateful applications, ensuring stable identities and persistent storage.
- They provide stable network IDs, ordered operations, and leverage Volume Claim Templates for dedicated storage.
- A Headless Service is often used to provide stable DNS entries for StatefulSet Pods.
- They support controlled updates with strategies like
RollingUpdate.
StatefulSets are essential for running databases, message queues, and other stateful services reliably on Kubernetes.
Aprenda Docker & Kubernetes for Developers com um tutor de IA — grátis
Escreva e execute código real no seu navegador, obtenha ajuda instantânea de um tutor de IA 24/7 e continue de onde parou na web ou no app.
- Cursos
- 12
- Aulas
- 48
Perguntas Frequentes
A aula “Gerenciamento de aplicações com estado usando StatefulSets” é grátis?
Sim — o texto completo de “Gerenciamento de aplicações com estado usando StatefulSets” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Docker & Kubernetes for Developers, atualize para CoddyKit PRO. O curso de Docker & Kubernetes for Developers inclui 4 aulas no total.
O que vou aprender em “Gerenciamento de aplicações com estado usando StatefulSets”?
Implante e gerencie aplicações com estado, como bancos de dados, usando StatefulSets e garantindo identidades de rede estáveis e armazenamento persistente. Você pratica Docker & Kubernetes for Developers com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Docker & Kubernetes for Developers?
Nenhuma experiência prévia é necessária. Docker & Kubernetes for Developers no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.
Quanto tempo leva a aula “Gerenciamento de aplicações com estado usando StatefulSets”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Docker & Kubernetes for Developers?
Sim. Cada aula de Docker & Kubernetes for Developers inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Volumes persistentes e solicitações de volumes persistentes
- Gerenciamento de aplicações com estado usando StatefulSets
- ConfigMaps e Secrets para configuração
- Classes de armazenamento e provisionamento dinâmico