Skip to content

Existing PVC updated #898

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

Merged
merged 1 commit into from
Aug 1, 2024
Merged

Existing PVC updated #898

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 11 additions & 7 deletions ...aces/blocks/Persistent Volume Chain (PVC) → ...kspaces/blocks/Persistent-Volume-Chain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,11 +21,12 @@ For example: By selecting Department B as the scope of the asset, any user with

There are two different ways of creating data source of type PVC:

1. **Existing PVC** \- Data source of type PVC using an existing PVC in the cluster
1. **New PVC** \- Data source of type PVC by creating a new pvc in the cluster
1. **Existing PVC**—Data source of type PVC using an existing PVC in the cluster
1. **New PVC**—Data source of type PVC by creating a new pvc in the cluster
![](img/10-pvc.png)

**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.
!!! 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.

## Existing PVC

Expand All @@ -39,10 +40,12 @@ The actions taken by the admin are based on the scope (cluster, department or pr

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:
[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.
[run.ai/cluster-wide](http://run.ai/cluster-wide): "true"

In the Run:ai platform finish creating the data source of type PVC:
!!!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:

1. Select your cluster as a scope
1. Select the existing PVC
Expand All @@ -62,7 +65,8 @@ The actions taken by the admin are based on the scope (cluster, department or pr

### For a project scope:

**NOTE**: For project scope, no labels are required.
!!! NOTE
For project scope, no labels are required.

1. In the Run:ai platform finish creating the data source of type PVC:
1. Select your project as a scope
Expand Down
1 change: 1 addition & 0 deletions mkdocs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -263,6 +263,7 @@ nav:
- 'Environments' : 'Researcher/user-interface/workspaces/blocks/environments.md'
- 'Compute Resources': 'Researcher/user-interface/workspaces/blocks/compute.md'
- 'Data Sources' : 'Researcher/user-interface/workspaces/blocks/datasources.md'
- 'Existing PVCs' : 'Researcher/user-interface/workspaces/blocks/Persistent-Volume-Chain.md'
- 'Creation' :
- 'Create an Environment' : 'Researcher/user-interface/workspaces/create/create-env.md'
- 'Create a Compute Resource' : 'Researcher/user-interface/workspaces/create/create-compute.md'
Expand Down
Loading