Hi, > > looking up a service isn't openshift specific - its working with > > kubernetes resources (which may or may not have associated openshift > > resources). > > > > Totally agree. This should have remained `minishift service`, looking up > service URLs via route, ingress and node port. I would have expected that > to be contributed upstream whch would only look at ingress and node port.
Be are basing our implementation on the use of _oc_ which is not available in Minikube. So in this particular case we don't have much to backport. > One of the defining goals of minishift was to make the transition from > minikube to minishift easy. Keeping commands consistent is key to that Sure, but consistency with Minikube cannot be the only goal. There are other considerations as well. On other names we for example aligned with Minikube. We called the extension mechanism also 'addons', even though they work differently. Minikube implemented now the ability to create multiple instances. Something we followed and had input to. The plan is to align as much as possible there as well. So we are for sure interested to keep consistency. However, in some cases it also makes sense to do things differently. > I'm not contributing to minishift any more, busy with other things..., but I > would hope that the minishift team is contributing to minikube too - guide > minikube in line with what for minishift would be a win for everyone IMO. We follow issues which are relevant to us, however, have not contributed enough to Minikube. Moving forward it would be nice to see some more collaboration on code level as well. However, all the work up to Minishift 1.0.0 barely touched Minikube inherited code. There are only a few things we could have contributed back so far. Two come to mind: * Driver initialisation (together with the ability to pass through driver specific options) * Host folder framework Both things would be good fits for Minikube as well. Up to know we were really hands on to just get Minishift 1.0.0 and CDK 3.0.0 ready. Moving forward we can have a discussion now whether we should try to get for example the things mentioned above into Minikube. However, this will take quite some doing and will slow us down with feature development for Minishift. --Hardy
signature.asc
Description: PGP signature
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
