Plan Storage

Plan storage for Confluent Platform components deployed with Confluent for Kubernetes. CFK requires a Kubernetes Storage Class to provision persistent volumes for most Confluent Platform components, using block-level storage solutions such as AWS EBS, Azure Disk, GCE Disk, Ceph RBD, and Portworx. Object storage and network file storage are not supported.

Component	Persistent volumes	Notes
Apache Kafka®	1 per broker	Block storage only; network-attached storage (NAS) is not recommended
ZooKeeper	2 per node	Uses the same storage solution as Kafka
Connect	None	Stateless; no Storage Class required
Schema Registry	None	Stateless; no Storage Class required
ksqlDB	One	Maintains working state during the component’s lifetime
Confluent Control Center	one, or two if you have configured services.prometheus.	The optional services.prometheus block adds a second, dedicated Prometheus data volume in addition to the component’s own data volume.

For storage class configuration steps and vendor-specific setup details, see Configure Storage for Confluent Platform Using Confluent for Kubernetes.