Skip to content

Existing pvc new doc #899

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 4 commits into from
Closed

Existing pvc new doc #899

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9444d44
Existing PVC updated2
JamieWeider72 Aug 1, 2024
406e0e6
Existing PVC updated3
JamieWeider72 Aug 1, 2024
51abbfa
Existing PVC new version
JamieWeider72 Aug 1, 2024
464e104
Existing PVC latest version
JamieWeider72 Aug 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 7 additions & 10 deletions docs/Researcher/user-interface/workspaces/blocks/Persistent-Volume-Chain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,6 @@ There are two different ways of creating data source of type PVC:

To select an existing PVC in the Run:ai platform, the admin is responsible for performing a number of actions prior to creating the data source via the Run:ai UI (or API). These actions provide Run:ai with access to the existing PVC, authorization to share across the selected scope and eventually result in exposing the existing PVC in the UI for the user to select.

Click the link for more information on [creating a data source of type PVC via API](https://envinaclickstaging.staging.run.ai/api/docs\#tag/PVC/operation/create\_pvc\_asset).

The actions taken by the admin are based on the scope (cluster, department or project) that the admin wants for data source of type PVC.

### For a cluster scope
Expand All @@ -42,8 +40,8 @@ The actions taken by the admin are based on the scope (cluster, department or pr
1. Provide Run:ai with visibility and authorization to share the PVC to your selected scope by implementing the following label:
[run.ai/cluster-wide](http://run.ai/cluster-wide): "true"

!!!NOTE
This step is also relevant for creating the data source of type PVC via API.
!!! NOTE
This step is also relevant for creating the data source of type PVC via API.

In the Run:ai platform finish creating the data source of type PVC:

Expand All @@ -52,7 +50,7 @@ In the Run:ai platform finish creating the data source of type PVC:
1. Complete all mandatory fields
1. Click Create

### For a department scope:
### For a department scope

1. Locate the PVC in the runai namespace
1. Provide Run:ai with visibility and authorization to share the PVC to your selected scope by implementing the following label:
Expand All @@ -63,7 +61,7 @@ In the Run:ai platform finish creating the data source of type PVC:
1. Complete all mandatory fields
1. Click Create

### For a project scope:
### For a project scope

!!! NOTE
For project scope, no labels are required.
Expand All @@ -83,7 +81,6 @@ When creating a data source of type PVC using a new PVC, Run:ai creates the PVC
1. Complete all mandatory fields
1. Click Create

**NOTES**:

* When creating data source of type PVC using a new PVC, the PVC is created immediately in the cluster runai namespace (even if no workload has requested to use this PVC)
* A PVC created in the cluster by selecting the option “New PVC” never appears as a PVC in the “Existing PVC“ option.
!!! NOTES
When creating data source of type PVC using a new PVC, the PVC is created immediately in the cluster runai namespace (even if no workload has requested to use this PVC).
A PVC created in the cluster by selecting the option “New PVC” never appears as a PVC in the “Existing PVC“ option.
Loading