-
Notifications
You must be signed in to change notification settings - Fork 5k
Open
Labels
co/qemu-driverQEMU related issuesQEMU related issueskind/improvementCategorizes issue or PR as related to improving upon a current feature.Categorizes issue or PR as related to improving upon a current feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Description
Now that #13639 is (soon to be) merged, we need a place to aggregate all the known issues so we can eventually graduate it from experimental to recommended driver.
- containerd runtime is broken (permissions on the socket file)
- crio runtime is broken (podman and crio-wipe return errors trying to mount a volume)
-
minikube service
(implemented with Implement socket_vmnet network (QEMU) #14989) -
minikube tunnel
(implemented with Implement socket_vmnet network (QEMU) #14989) - Full test suite on macOS arm64
- Full test suite on linux arm64
- Unconfigurable firmware paths
- Registry addon (kube-registry-proxy images has no arm64 version) (implemented with addons registry: Use multi-arch kube-registry-proxy image #16577)
- Windows support (find the correct qemu-system command line args) (experimental support implemented with Implement experimental QEMU on Windows code #15781)
- Cannot specify custom api server port
- Use VDE/Socket drivers for macOS networking (implemented with Implement socket_vmnet network (QEMU) #14989)
- Multi-node (based on Add multi-node support for QEMU #14527)
kakkoyun and caerulescens
Metadata
Metadata
Assignees
Labels
co/qemu-driverQEMU related issuesQEMU related issueskind/improvementCategorizes issue or PR as related to improving upon a current feature.Categorizes issue or PR as related to improving upon a current feature.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.