In this talk Kim-Norman Sahm and Alexander Trost dive into the challenges of storage for containerized applications on Kubernetes. We'll see how the current state is and how Rook can help with that. We are going to especially look at Ceph run through Rook here, but nonetheless trying not to lose sight of the whole picture. There is a lot to keep in mind storage as is, but everything gets more complex with storage for containers. From what type of storage to how much and how "safe" it should, all questions that should be asked and most of them which should be answered as well. Rook's project site https://rook.io/ Kim-Norman Sahm is CTO of Cloudical. He also works as Executive Cloud Architect at Cloudical. Previously, he was OpenStack Cloud Architect at T-Systems (operational services GmbH) and noris network AG. He is an expert of the technologies OpenStack, Ceph and Kubernetes (CKA). Alexander Trost works as a DevOps Engineer at Cloudical Deutschlang GmbH and is a Certified Kubernetes Administrator (CKA). He is one of four maintainers of the Rook.io Project and is engaged in several more open source projects, for example a Prometheus exporter for Dell Hardware (Dell OMSA Metrics), k8s-vagrant-multi-node an easy local multi node Kubernetes environment, and others. Besides Containers and Kubernetes he is expert on Software Defined Storage, Golang and Continuous Integration (with GitLab CI). He passionately enjoys working on open source projects, such as Rook, Ancientt and other projects.

1. Rook: Storage for
Containers in Containers
“Where has my data gone now?”
Kim-Norman Sahm and Alexander Trost
Cloudical Deutschland GmbH

2. .Alexander Trost.
.DevOps Engineer.
.Kim-Norman Sahm.
.CTO.

3. ● Storage for containerized Applications
○ Container Storage Interface (CSI)
○ What is Rook?
○ How can Rook Ceph help?
● Challenges
○ Block vs Filesystem vs Object
○ Choosing the right type of Storage
○ 2nd Day Operations
■ Restore
■ Disaster Recovery
● Summary
Agenda

4. Storage for containerized Applications

5. Container Storage Interface (CSI)

6. In a Nutshell...

7. One interface for storage
backend and container
orchestrator to implement.
For users to be able to
consume storage.

8. What is Rook?

9. ● Storage Operators for Kubernetes
● Automate
○ Deployment
○ Bootstrapping
○ Configuration
○ Upgrading
● Provision
○ Consume Storage by PVCs
What is Rook?

10. 🎉 v1.4 released
⭐ 7.4K+ Github Stars
💾 160M+ Downloads
🤝 275+ Contributors
🎓 CNCF Graduated

13. How can Rook Ceph help?

14. ● Run Ceph in Kubernetes
● Connect to an existing Ceph cluster:
○ Consume Storage
○ Manage Ceph Cluster
How can Rook help?

15. Challenges

16. ● Block vs Filesystem vs Object
● Choosing the right type of Storage
● 2nd Day Operations
○ Restore
○ Disaster Recovery
Challenges

17. Block vs.
Filesystem vs.
Object

18. Block
“Raw”
(Disk, USB Stick, /dev/sda, etc.)
Block vs. Filesystem vs. Object
Filesystem
“Ready for Use”
(NFS, CephFS, Gluster, etc.)
Object
“HTTP Interface”
(S3, Swift, etc.)

19. Block Storage:
Databases. Applications which don’t
“share” data.
Anything that does DIRECTIO and
can utilize “Kernel level FS / block
caching”.
Choosing the right type
of Storage
Filesystem Storage:
Applications unable to use Object
Storage, but must share data
between them.
Object Storage:
Cloud Native Applications.
...

20. 2nd Operations

21. 2nd Operations
● “Backups are easy” + “Restore hopefully works”
○ Velero + Hooks
○ Stashed
● Disaster Recovery
○ What data is needed?
○ Create a plan for if data XYZ is missing.
■ E.g., can certain data be recalculated in a bad case.

22. Summary

23. Summary
● Rook Ceph can be used to create but also manage existing Ceph Cluster.
● Kubernetes driven easy to use storage solution
● CRD based integration in Kubernetes
● Block / Object / Filestorage in one backend instead of different solutions
● Open Source :-)

24. Call our Experts!
Enterprise Support for OpenSource
projects, like Rook.
Twitter 🐦 @cloudical_gmbh
cloudical.io/expert-call/

25. “The door to both the beginning and the end.”
- From Kozo Fuyutsuki, NGE
The End