How to explicit name the KadaluStorage in a PVC? #461
Replies: 1 comment 4 replies
-
|
Create two Storage classes by specifying the storage_name. Refer this doc for creating custom Storage classes. |
Beta Was this translation helpful? Give feedback.
-
|
I tried to see if we have any mechanism to pass a key=value pair to PVC yaml. Currently couldn't find any such things, hence the above method is the only solution i can think of. |
Beta Was this translation helpful? Give feedback.
-
|
Should we have 'storage.replicaX' storage config at all? Looks like we can manage without any such things, and handle it similar to external config. The reason we started with Replica1 as a standard one initially was because we didn't support distribute. Now that we have that support, one volume can have one storage-config.... That way, people will be very clear what they need to refer to during PVC. @aravindavk what do you think? |
Beta Was this translation helpful? Give feedback.
-
|
Default storage classes created for each Volume types(Subvolume types). But users are not limited with these storage classes. |
Beta Was this translation helpful? Give feedback.
-
|
We can remove the default Storage classes if it is confusing. |
Beta Was this translation helpful? Give feedback.
-
Example:
I have two storages. One is HDD other is SSD and both are of type Replica2.
Question:
How can I create a PVC that askes for SSD storage?
Beta Was this translation helpful? Give feedback.
All reactions