Conversation
docs/architecture/rook.md
Outdated
| Kubernetes cluster, managing the lifecycle of Ceph daemons (monitors, managers, | ||
| OSDs, MDS, and RGW) as containerized workloads. It automatically handles tasks | ||
| such as OSD provisioning from available storage devices, the management of the | ||
| monitor quorum, and disaster recovery. |
There was a problem hiding this comment.
disaster recovery is not in the scope of rook. Maybe we can mention that "RGW multisite configuration can be called a remote replication on broader replication" for this context.
There was a problem hiding this comment.
I've removed the reference to disaster recovery, and I thank you for the correction.
I don't understand what "RGW multisite configuration can be called a remote replication on broader replication" means. Can you explain?
There was a problem hiding this comment.
"Disaster Recovery" concept is not inside Rook. But the multisite configurations (kind of it is also a disaster recovery/business continuity feature) is supported by rook. I mean that might be placed inside that context. I think the current sate looks good. Lets keep it like this
There was a problem hiding this comment.
Roger that, @senolcolak.
I'll create a Prysm page later today, and I'll designate you as the reviewer for it.
It's good to work with you.
Add a page explaining Rook's role in the CobaltCore ecosystem as it relates to Ceph. Signed-off-by: Zac Dover <zac.dover@clyso.com>
zdover23
force-pushed
the
docs-2026-03-03-docs-architecture-rook
branch
from
0cee50f to
499a3a7
Compare
2 participants
Add a page explaining Rook's role in the CobaltCore ecosystem as it relates to Ceph.