Hi, > Agree. We definitely should find out a way to contribute to Minikube. But > the current code base is grown different from each other e.g. the service > sub-command as it does not depend on the Kubernetes code now.
+1 > We need to address this issue from a long term point of view. Basically > find a model where both us get benefited from each other. We had some > discussion around it but nothing concrete at this point. One of the idea is > to use minikube as a go library in Minishift . I think this is the thing we should be focusing on. Right now there is no easy way to contribute back. If we could make the core of Minikube more of a library/ dependency we could indeed fix bugs directly upstream. --Hardy
signature.asc
Description: PGP signature
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
