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
The instruction can work only in a very specific case:
you set your default cluster (kubectl config use-context my-cluster)
the default cluster has kubevirt installed - not true for multi-cluster setup, e.g. hub and 2 managed clusters. typically the hub will be set as default since it is mostly used for managing DR
When kubevirt is not installed on the cluster, the commands fail in an unclear way
Other issues:
chmod is not needed, the install command does it
What you expected:
Simple instructions that work for any use case
Use same version of kubevirt
Example command for specific version of kubevirt
If providing an automate way (like current example), document the preconditions
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.
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.
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
kubevirt-bot
added
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Jul 26, 2024
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.
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
The text was updated successfully, but these errors were encountered: