support minikube w/ hyperkit
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 722
- Forks
- 48
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 8
Description
Currently ctlptl always uses docker as the driver for minikube
We should be able to customize it to use hyperkit.
This isn't quite as simple as changing a flag, because you also need to do some additional registry plumbing to connect the hyperkit vm to the registry
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing ctlptl’s minikube setup and the existing Docker-driver and registry handling. Determine how hyperkit connectivity affects the registry plumbing, then verify that minikube can use hyperkit and still connect to the configured registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- cli, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100