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
Spike for discussions and review on how Minikube can reuse the existing Windows machine.
It works with only one driver at a time (kvm2) to create a default CP node. This must continue to be made. The other configuration to be added and extended is the capability to connect in the already running Windows VM preferably via SSH
Reusing the flag namespace of the SSH driver enabling windows via flag is ugly and confusing. Need a brainstorm to adapt and extend minikube capabilities internally.
One possible direction is TO NOT extend minikube internally, and reuse the created Linux CP only to join the VM externally, so swdt would be responsible for hooking the pieces. With a CMD like:
swdt start
Assess possibilities.
The text was updated successfully, but these errors were encountered:
knabben
added
the
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
label
Mar 25, 2024
Spike for discussions and review on how Minikube can reuse the existing Windows machine.
It works with only one driver at a time (kvm2) to create a default CP node. This must continue to be made. The other configuration to be added and extended is the capability to connect in the already running Windows VM preferably via SSH
Reusing the flag namespace of the SSH driver enabling windows via flag is ugly and confusing. Need a brainstorm to adapt and extend minikube capabilities internally.
One possible direction is TO NOT extend minikube internally, and reuse the created Linux CP only to join the VM externally, so swdt would be responsible for hooking the pieces. With a CMD like:
Assess possibilities.
The text was updated successfully, but these errors were encountered: