text: « Previous 1 2 3 4
  Cloud-native storage for Kubernetes with Rook
  Memory
  Conclusions
  The idea behind Rook is not particularly revolutionary. Packing Ceph, the storage solution that has been tried and tested for years, into containers and then rolling them out to Kubernetes is an obvious choice. However, the way Rook tackles the problem is impressive, because the solution for a supposedly trivial task involved a huge amount of brain power, development, and quality assurance. The Rook people are quite aware that they are dealing with 21st century gold (i.e., data), and they deal with it very carefully.
  Given that Rook is still officially beta, it works excellently. If you want to mate up Kubernetes and Ceph, you will definitely want to take a look at Rook. To date, it is the best solution for this problem.
  Rook keeps the promise of redundant storage for cloud-native apps. A Rook volume is no different from a typical Kubernetes volume in terms of the inside view. In the background, however, Rook ensures that replication and redundancy are handled by Ceph. In doing so, Rook solves the dilemma that neither the container environment, the developers, nor the customers cared to tackle – redundant storage.
  Infos
  - OpenStack:
  - Kubernetes:
  - Docker:
  - Rook:
  - Ceph:
  - Rook namespace examples:
  - Prometheus for Kubernetes:
  - Prometheus and Rook:
  - CockroachDB:
  - Minio:
  - Upbound:
  « Previous 1 2 3 4
  Buy this article as PDF
  (incl. VAT)