Open nirs opened 7 months ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
/remove-lifecycle rotten
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Description:
The instruction can work only in a very specific case:
Other issues:
What you expected:
Simple instructions that work for any use case
If providing an automate way (like current example), document the preconditions
URL: https://kubevirt.io/quickstart_minikube/#virtctl
Additional context:
For creating ramen development environment, supporting testing kubevirt vms, we install virtctl first, as a required tool, and than created the clusters and provision them using a tool. The tool will access a test vm in the cluster using virtctl to validate the deployment.
We provide our own documentation pointing to the specific kubevirt version we use: https://github.com/RamenDR/ramen/blob/main/docs/user-quick-start.md#setting-up-your-machine