mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-09-19 15:09:56 +00:00
Code Issues Packages Projects Releases Wiki Activity

cleanup: remove the use of text in markdown

Browse Source 
We do not have `text` in the new section of the MarkDown Rules. Hence
dropping them.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
This commit is contained in:
Prasanna Kumar Kalever 2020-11-11 12:57:40 +05:30 committed by mergify[bot]
parent 8475a3b97e
commit 817edfd1c7
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/capabilities.md
View File

@ -14,7 +14,7 @@ We have provisioner, controller expand and node stage secrets in storage class.
For the provisioner and controller expand stage secret in storageclass, the
user needs to have the below mentioned ceph capabilities.
```text
```
"mon", "profile rbd",
"mgr", "allow rw",
"osd", "profile rbd"
@ -23,7 +23,7 @@ user needs to have the below mentioned ceph capabilities.
And for the node stage secret in storageclass, the user needs to have the
below mentioned ceph capabilities.
```text
```
"mon", "profile rbd",
"osd", "profile rbd",
"mgr", "allow rw"
@ -34,7 +34,7 @@ below mentioned ceph capabilities.
Similarly in CephFS, for the provisioner and controller expand stage secret in
storageclass, the user needs to have the below mentioned ceph capabilities.
```text
```
"mon", "allow r",
"mgr", "allow rw",
"osd", "allow rw tag cephfs metadata=*"
@ -43,7 +43,7 @@ storageclass, the user needs to have the below mentioned ceph capabilities.
And for node stage secret in storageclass, the user needs to have
the below mentioned ceph capabilities.
```text
```
"mon", "allow r",
"mgr", "allow rw",
"osd", "allow rw tag cephfs *=*",

6
docs/development-guide.md
View File

@ -119,7 +119,7 @@ contribution. See the [DCO](DCO) file for details.
Contributors sign-off that they adhere to these requirements by adding a
Signed-off-by line to commit messages. For example:
```text
```
subsystem: This is my commit message
More details on what this commit does
@ -144,7 +144,7 @@ We follow a rough convention for commit messages that is designed to answer two
questions: what changed and why? The subject line should feature the what and
the body of the commit should describe the why.
```text
```
cephfs: update cephfs resize
use cephfs resize to resize subvolume
@ -154,7 +154,7 @@ Signed-off-by: Random J Developer <random@developer.example.org>
The format can be described more formally as follows:
```text
```
<component>: <subject of the change>
<BLANK LINE>
<paragraph(s) with reason/description>