Files
my-rook-config/Documentation
Travis Nielsen fb86955f01 core: examples set default priority class names
By default, we should set the priority class to one of the built-in
priority class names to ensure that pods critical to the storage
will be able to remain running when resources are low. Otherwise,
critical rook pods could be evicted and affect many other pods
that rely on the storage to continue functioning. The options have
been available in the CRs, but until now we have just not set the
defaults in the examples. Critical rook components are now set to
the priority class system-node-critical if they are generally pinned
to a node, and system-cluster-critical if they are critical to the storage.
Some pods such as the operator and crash collector do not have a
default priority class set in the examples since they don't affect
the data path.

Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
2022-04-19 16:09:34 -06:00
..
2021-11-30 09:12:53 +01:00
2022-02-23 11:51:29 +05:30
2021-11-30 09:12:53 +01:00
2022-03-03 15:52:07 +00:00
2021-11-30 09:12:53 +01:00
2022-04-07 21:28:18 +05:30
2021-11-30 09:12:53 +01:00
2021-11-30 09:12:53 +01:00
2022-02-19 20:32:01 +09:00

Rook

Rook is an open source cloud-native storage orchestrator, providing the platform, framework, and support for a diverse set of storage solutions to natively integrate with cloud-native environments.

Rook turns storage software into self-managing, self-scaling, and self-healing storage services. It does this by automating deployment, bootstrapping, configuration, provisioning, scaling, upgrading, migration, disaster recovery, monitoring, and resource management. Rook uses the facilities provided by the underlying cloud-native container management, scheduling and orchestration platform to perform its duties.

Rook integrates deeply into cloud native environments leveraging extension points and providing a seamless experience for scheduling, lifecycle management, resource management, security, monitoring, and user experience.

The Ceph operator was declared stable in December 2018 in the Rook v0.9 release, providing a production storage platform for several years already.

Quick Start Guide

Starting Ceph in your cluster is as simple as a few kubectl commands. See our Quickstart guide to get started with the Ceph operator!

Designs

Ceph is a highly scalable distributed storage solution for block storage, object storage, and shared filesystems with years of production deployments. See the Ceph overview.

For detailed design documentation, see also the design docs.

Need help? Be sure to join the Rook Slack

If you have any questions along the way, please don't hesitate to ask us in our Slack channel. You can sign up for our Slack here.