[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4938":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":14,"rankGlobal":9,"rankLanguage":9,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":21,"hasPages":21,"topics":23,"createdAt":9,"pushedAt":9,"updatedAt":32,"readmeContent":33,"aiSummary":34,"trendingCount":15,"starSnapshotCount":15,"syncStatus":16,"lastSyncTime":35,"discoverSource":36},4938,"rook","rook\u002Frook","Storage Orchestration for Kubernetes","https:\u002F\u002Frook.io",null,"Go",13540,2821,262,84,0,2,11,45,8,"Apache License 2.0",false,"master",[24,25,26,27,28,29,30,31],"ceph","cloud-native","cncf","docker","etcd","kubernetes","storage","storage-cluster","2026-06-12 04:00:24","\u003Cimg alt=\"Rook\" src=\"Documentation\u002Fmedia\u002Flogo.svg\" width=\"50%\" height=\"50%\">\n\n[![CNCF Status](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fcncf%20status-graduated-blue.svg)](https:\u002F\u002Fwww.cncf.io\u002Fprojects)\n[![GitHub release](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Frelease\u002Frook\u002Frook\u002Fall.svg)](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Freleases)\n[![Docker Pulls](https:\u002F\u002Fimg.shields.io\u002Fdocker\u002Fpulls\u002Frook\u002Fceph)](https:\u002F\u002Fhub.docker.com\u002Fu\u002Frook)\n[![Go Report Card](https:\u002F\u002Fgoreportcard.com\u002Fbadge\u002Fgithub.com\u002Frook\u002Frook)](https:\u002F\u002Fgoreportcard.com\u002Freport\u002Fgithub.com\u002Frook\u002Frook)\n[![OpenSSF Scorecard](https:\u002F\u002Fapi.securityscorecards.dev\u002Fprojects\u002Fgithub.com\u002Frook\u002Frook\u002Fbadge)](https:\u002F\u002Fscorecard.dev\u002Fviewer\u002F?uri=github.com\u002Frook\u002Frook)\n[![CII Best Practices](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F1599\u002Fbadge)](https:\u002F\u002Fbestpractices.coreinfrastructure.org\u002Fprojects\u002F1599)\n[![Security scanning](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Factions\u002Fworkflows\u002Fsnyk.yaml\u002Fbadge.svg)](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Factions\u002Fworkflows\u002Fsnyk.yaml)\n[![Slack](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Frook-slack-blue)](https:\u002F\u002Fslack.rook.io)\n[![Twitter Follow](https:\u002F\u002Fimg.shields.io\u002Ftwitter\u002Ffollow\u002Frook_io.svg?style=social&label=Follow)](https:\u002F\u002Ftwitter.com\u002Fintent\u002Ffollow?screen_name=rook_io&user_id=788180534543339520)\n\n# What is Rook?\n\nRook is an open source **cloud-native storage orchestrator** for Kubernetes, providing the platform, framework, and support for Ceph storage to natively integrate with Kubernetes.\n\n[Ceph](https:\u002F\u002Fceph.com\u002F) is a distributed storage system that provides file, block and object storage and is deployed in large scale production clusters.\n\nRook automates deployment and management of Ceph to provide self-managing, self-scaling, and self-healing storage services.\nThe Rook operator does this by building on Kubernetes resources to deploy, configure, provision, scale, upgrade, and monitor Ceph.\n\nThe status of the Ceph storage provider is **Stable**. Features and improvements will be planned for many future versions. Upgrades between versions are provided to ensure backward compatibility between releases.\n\nRook is hosted by the [Cloud Native Computing Foundation](https:\u002F\u002Fcncf.io) (CNCF) as a [graduated](https:\u002F\u002Fwww.cncf.io\u002Fannouncements\u002F2020\u002F10\u002F07\u002Fcloud-native-computing-foundation-announces-rook-graduation\u002F) level project. If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Rook plays a role, read the CNCF [announcement](https:\u002F\u002Fwww.cncf.io\u002Fblog\u002F2018\u002F01\u002F29\u002Fcncf-host-rook-project-cloud-native-storage-capabilities).\n\n## Getting Started and Documentation\n\nFor installation, deployment, and administration, see our [Documentation](https:\u002F\u002Frook.github.io\u002Fdocs\u002Frook\u002Flatest-release) and [QuickStart Guide](https:\u002F\u002Frook.github.io\u002Fdocs\u002Frook\u002Flatest-release\u002FGetting-Started\u002Fquickstart).\n\n## Contributing\n\nWe welcome contributions. See [Contributing](CONTRIBUTING.md) to get started.\n\n## Report a Bug\n\nFor filing bugs, suggesting improvements, or requesting new features, please open an [issue](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Fissues).\n\n### Reporting Security Vulnerabilities\n\nIf you find a vulnerability or a potential vulnerability in Rook please let us know immediately at\n[cncf-rook-security@lists.cncf.io](mailto:cncf-rook-security@lists.cncf.io). We'll send a confirmation email to acknowledge your\nreport, and we'll send an additional email when we've identified the issues positively or\nnegatively.\n\nFor further details, please see the complete [security release process](SECURITY.md).\n\n## Contact\n\nPlease use the following to reach members of the community:\n\n-   Slack: Join our [slack channel](https:\u002F\u002Fslack.rook.io)\n-   GitHub: Start a [discussion](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Fdiscussions) or open an [issue](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Fissues)\n-   Twitter: [@rook_io](https:\u002F\u002Ftwitter.com\u002Frook_io)\n-   Security topics: [cncf-rook-security@lists.cncf.io](#reporting-security-vulnerabilities)\n\n## Community Meeting\n\nA regular community meeting takes place the [2nd Tuesday of every month at 9:00 AM PT (Pacific Time)](https:\u002F\u002Fzoom.us\u002Fj\u002F98052644520?pwd=K0R4RUZCc3NhQisyMnA5VlV2MVBhQT09).\nConvert to your [local timezone](http:\u002F\u002Fwww.thetimezoneconverter.com\u002F?t=9:00&tz=PT%20%28Pacific%20Time%29).\n\nAny changes to the meeting schedule will be added to the [agenda doc](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1exd8_IG6DkdvyA0eiTtL2z5K2Ra-y68VByUUgwP7I9A\u002Fedit?usp=sharing) and posted to [Slack #announcements](https:\u002F\u002Frook-io.slack.com\u002Fmessages\u002FC76LLCEE7\u002F).\n\nAnyone who wants to discuss the direction of the project, design and implementation reviews, or general questions with the broader community is welcome and encouraged to join.\n\n-   Meeting link: \u003Chttps:\u002F\u002Fzoom.us\u002Fj\u002F98052644520?pwd=K0R4RUZCc3NhQisyMnA5VlV2MVBhQT09>\n-   [Current agenda and past meeting notes](https:\u002F\u002Fdocs.google.com\u002Fdocument\u002Fd\u002F1exd8_IG6DkdvyA0eiTtL2z5K2Ra-y68VByUUgwP7I9A\u002Fedit?usp=sharing)\n-   [Past meeting recordings](https:\u002F\u002Fwww.youtube.com\u002Fplaylist?list=PLP0uDo-ZFnQP6NAgJWAtR9jaRcgqyQKVy)\n\n## Official Releases\n\nOfficial releases of Rook can be found on the [releases page](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Freleases).\nPlease note that it is **strongly recommended** that you use [official releases](https:\u002F\u002Fgithub.com\u002Frook\u002Frook\u002Freleases) of Rook, as unreleased versions from the master branch are subject to changes and incompatibilities that will not be supported in the official releases.\nBuilds from the master branch can have functionality changed and even removed at any time without compatibility support and without prior notice.\n\n## Licensing\n\nRook is under the Apache 2.0 license.\n\n[![FOSSA Status](https:\u002F\u002Fapp.fossa.io\u002Fapi\u002Fprojects\u002Fgit%2Bgithub.com%2Frook%2Frook.svg?type=large)](https:\u002F\u002Fapp.fossa.io\u002Fprojects\u002Fgit%2Bgithub.com%2Frook%2Frook?ref=badge_large)\n","Rook 是一个为 Kubernetes 设计的开源云原生存储编排器，旨在通过自动化部署和管理 Ceph 存储来提供自管理、自扩展和自愈的存储服务。该项目采用 Go 语言开发，能够利用 Kubernetes 的资源抽象能力实现 Ceph 集群的安装、配置、供给、扩展、升级以及监控等功能。Rook 适用于需要高可用性和可伸缩性的数据存储场景，如大数据处理、容器化应用的数据持久化等。它已被云原生计算基金会（CNCF）接纳为毕业项目，表明其在生产环境中的稳定性和成熟度得到了广泛认可。","2026-06-11 03:01:36","top_language"]