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
Is your feature request related to a problem? Please describe:
Cannot clone/create a DataVolume from existing pvc in the current namespace.
Describe the solution you'd like: namespace field would be optional. When empty, current namespace would be used.
Exactly the same as typical k8s manifests.
Describe alternatives you've considered:
Detecting current namespace and injecting it - not exactly feasible.
Additional context:
I don't know (and don't care) in which namespace my resources are deployed. I create one "template" DataVolume (OS image) that is used for VMs to be created (cloned) from.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe:
Cannot clone/create a DataVolume from existing pvc in the current namespace.
Describe the solution you'd like:
namespace
field would be optional. When empty, current namespace would be used.Exactly the same as typical k8s manifests.
Describe alternatives you've considered:
Detecting current namespace and injecting it - not exactly feasible.
Additional context:
I don't know (and don't care) in which namespace my resources are deployed. I create one "template" DataVolume (OS image) that is used for VMs to be created (cloned) from.
The text was updated successfully, but these errors were encountered: