rook/rook

Storage Orchestration for Kubernetes

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 29 minutes ago
Added to GitGenius on April 7th, 2021
Created on July 8th, 2016
Open Issues & Pull Requests: 141 (+0)
GitHub issues: Enabled
Number of forks: 2,862
Total Stargazers: 13,657 (+0)
Total Subscribers: 263 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Rook is an open source cloud-native storage orchestrator for Kubernetes that automates the deployment and management of Ceph, a distributed storage system providing file, block, and object storage capabilities. Written in Go, Rook enables Ceph to integrate natively with Kubernetes by building on Kubernetes resources to handle deployment, configuration, provisioning, scaling, upgrades, and monitoring. The project automates Ceph management to deliver self-managing, self-scaling, and self-healing storage services within Kubernetes environments. Rook's Ceph storage provider has reached stable status, with the project itself designated as a graduated-level project by the Cloud Native Computing Foundation.

The repository demonstrates substantial community engagement and maintenance activity.

Rook's relevance extends across multiple domains within cloud-native infrastructure. This breadth reflects Rook's role as a comprehensive storage solution for modern container orchestration platforms.

The project maintains active community channels and governance structures. Regular community meetings occur on the second Tuesday of each month at 9:00 AM Pacific Time via Zoom, with agendas and past meeting recordings publicly available. The community communicates through Slack channels, GitHub discussions and issues, and Twitter at @rook_io. Security vulnerabilities are reported to a dedicated CNCF email address with a formal security release process documented in the repository.

The project is licensed under Apache 2.0 and strongly recommends using official releases rather than unreleased master branch builds, which may contain unsupported changes and incompatibilities. Documentation, quickstart guides, and contribution guidelines are maintained to support both operators deploying Rook and developers contributing to the project.