> For the complete documentation index, see [llms.txt](https://notebook.iuriioapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notebook.iuriioapps.com/containers-and-microservices/kubernetes/storage-in-kubernetes.md).

# Storage in Kubernetes

* Storage and stateful workloads are harder in all systems
* Containers make it both harder and easier than before
* StatefulSets is a new resource type, making Pods more sticky
* Avoid stateful deployments for first few deployments until you're good at the basics
* Use Database-as-a-Service whenever you can
* Creating and connecting volumes: 2 types
  * Volumes
    * Tied to a lifecycle of a Pod
    * All containers in a single pod can share them
  * PersistentVolumes / PersistentVolumeClaims
    * Created at a cluster level, outlives a Pod
    * Separates a storage config from Pod using it
    * Multiple Pods can share them
* CSI (Container Storage Interface) plugins are the new way to connect to storage


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://notebook.iuriioapps.com/containers-and-microservices/kubernetes/storage-in-kubernetes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.