Repository navigation
[Feature] Implement the functionality of specifying storage class mapping in HR tenant Kubernetes #1424
Description
Activity
From telegram chat: https://t.me/cozystack/14370
𝚔𝚟𝚊𝚙𝚜, [9/16/2025 1:24 PM]
It should be possible. You can create sc targeting needed sc manually inside the tenant kubernetes cluster.Petr Dondukov, [9/16/2025 1:25 PM]
OMG! Thanx a lot!Petr Dondukov, [9/16/2025 1:26 PM]
Is it possible to implement the functionality of specifying storage class mapping in HR tenant Kubernetes?- changed the title
[-][Feature] Ability to use multiple storage classes in a tenant Kubernetes[/-][+][Feature] Implement the functionality of specifying storage class mapping in HR tenant Kubernetes[/+]on Sep 16, 2025 𝚔𝚟𝚊𝚙𝚜, [9/16/2025 1:28 PM]
yeah we have an issue somewhere, let me find it𝚔𝚟𝚊𝚙𝚜, [9/16/2025 1:34 PM]
I have not found exact issue, but it is related to
kubevirt/csi-driver#59𝚔𝚟𝚊𝚙𝚜, [9/16/2025 1:34 PM]
we need to extend this a bit to generate a proper list of available storageclasses thoughHi, Petr Dondukov (@kinseii). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
- You requested the ability to specify multiple storage class mappings in HR tenant Kubernetes, beyond the current single default ("kubevirt").
- You shared a Telegram chat confirming manual creation of storage classes inside tenant clusters is possible.
- You referenced limit what infraStorageClassNames are accessible within infra cluster kubevirt/csi-driver#59 as related, noting it needs extension to support generating a proper list of available storage classes.
- The feature is considered feasible but requires further implementation work.
Next Steps:
- Please let me know if this issue is still relevant with the latest version of the cozystack repository by commenting here.
- If I don’t hear back within 7 days, I will automatically close this issue.
Thanks for your understanding and contribution!
Bump
Timofei Larkin (@lllamnyp) The user is still interested in the feature to specify multiple storage class mappings in HR tenant Kubernetes beyond the current single default. Could you please assist with this issue?
- added a commit that references this issue
on Jun 26, 2026
When creating a tenant cluster, we specify one of the Storage Classes, which will then be used by kubevirt by default (in a tenant cluster, it is named “kubevirt”). Is it possible to pass several Storage Classes, or is this a limitation of kubevirt itself?
Update: Is it possible to implement the functionality of specifying storage class mapping in HR tenant Kubernetes?