You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Researcher/user-interface/workspaces/blocks/Persistent-Volume-Chain.md
+11-7Lines changed: 11 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -21,11 +21,12 @@ For example: By selecting Department B as the scope of the asset, any user with
21
21
22
22
There are two different ways of creating data source of type PVC:
23
23
24
-
1. **Existing PVC** \- Data source of type PVC using an existing PVC in the cluster
25
-
1. **New PVC** \- Data source of type PVC by creating a new pvc in the cluster
24
+
1.**Existing PVC**—Data source of type PVC using an existing PVC in the cluster
25
+
1.**New PVC**—Data source of type PVC by creating a new pvc in the cluster
26
26

27
27
28
-
**NOTE**: If there are no existing PVCs that Run:ai has visibility or authorization to use, this option is disabled in the Run:ai platform. For details on providing visibility and authorization, see below Existing PVC.
28
+
!!! NOTE
29
+
If there are no existing PVCs that Run:ai has visibility or authorization to use, this option is disabled in the Run:ai platform. For details on providing visibility and authorization, see below Existing PVC.
29
30
30
31
## Existing PVC
31
32
@@ -39,10 +40,12 @@ The actions taken by the admin are based on the scope (cluster, department or pr
39
40
40
41
1. Locate the PVC in the runai namespace
41
42
1. Provide Run:ai with visibility and authorization to share the PVC to your selected scope by implementing the following label:
0 commit comments