Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This introduces a new CRD to add the ability to create rados namespace for a given ceph block pool. Typically the name of the pool is the name of the blockpool created by rook. Closes: #7035 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
- Loading branch information
Showing
33 changed files
with
1,854 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,6 +30,7 @@ | |
"rgw", | ||
"security", | ||
"subvolumegroup", | ||
"namespace", | ||
"test" | ||
] | ||
], | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
--- | ||
title: CephBlockPoolRadosNamespace CRD | ||
weight: 3610 | ||
indent: true | ||
--- | ||
|
||
{% include_relative branch.liquid %} | ||
|
||
This guide assumes you have created a Rook cluster as explained in the main [Quickstart guide](quickstart.md) | ||
|
||
# CephBlockPoolRadosNamespace CRD | ||
|
||
RADOS currently uses pools both for data distribution (pools are shared into | ||
PGs, which map to OSDs) and as the granularity for security (capabilities can | ||
restrict access by pool). Overloading pools for both purposes makes it hard to | ||
do multi-tenancy because it not a good idea to have a very large number of | ||
pools. | ||
|
||
A namespace would be a division of a pool into separate logical namespaces. For | ||
more information about BlockPool and namespace refer to the [Ceph | ||
docs](https://docs.ceph.com/en/latest/man/8/rbd/) | ||
|
||
Having multiple namespaces in a pool would allow multiple Kubernetes clusters | ||
to share one unique ceph cluster without creating a pool per kubernetes cluster | ||
and it will also allow to have tenant isolation between multiple tenenats in a | ||
single kubernetes cluste without creating pool's per tenants. | ||
|
||
Rook allows creation of Ceph BlockPool | ||
[RadosNamespaces](https://docs.ceph.com/en/latest/man/8/rbd/) through the | ||
custom resource definitions (CRDs). | ||
|
||
## Creating CephBlockPoolRadosNamespace CR | ||
|
||
To get you started, here is a simple example of a CR to create a CephBlockPoolRadosNamespace on the CephBlockPool "replicapool". | ||
|
||
```yaml | ||
apiVersion: ceph.rook.io/v1 | ||
kind: CephBlockPoolRadosNamespace | ||
metadata: | ||
name: namespace-a | ||
namespace: rook-ceph # namespace:cluster | ||
spec: | ||
# blockPoolName is the name of Ceph BlockPool. Typically it's the name of the CephBlockPool CR. | ||
blockPoolName: replicapool | ||
``` | ||
|
||
## Settings | ||
|
||
If any setting is unspecified, a suitable default will be used automatically. | ||
|
||
### CephBlockPoolRadosNamespace metadata | ||
|
||
- `name`: The name that will be used for the Ceph BlockPool rados namespace. | ||
|
||
### CephBlockPoolRadosNamespace spec | ||
|
||
- `blockPoolName`: The metadata name of the CephBlockPool CR where the rados namespace will be created. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,9 @@ | ||
--- | ||
apiVersion: ceph.rook.io/v1 | ||
kind: CephBlockPoolRadosNamespace | ||
metadata: | ||
name: namespace-a | ||
namespace: rook-ceph # namespace:cluster | ||
spec: | ||
# blockPoolName is the name of the CephBlockPool CR where the namespace will be created. | ||
blockPoolName: replicapool |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.