On Thu, May 11, 2017 at 5:56 PM, Roland Huss <[email protected]> wrote:
> That is not true. You can actually categorize commands. Most commands at >> the >> top level are much more about managing the VM, than anything around >> Kubernetes >> or OpenShift. The 'openshift' command creates a namespace for commands >> which >> directly effect OpenShift. >> > > But isn't it all about "Service" as central element, a concept which is > common to both Kubernetes and OpenShift ? That this is implemented > differently in minikube and minishift is, well, an implementation detail > which imo must not leak into the UX. > > If it would be 'minishift openshift route' then I might agree. But not for > "service". > > In fact, I did a demo today with both minikube and minishift and stumbled > about this very UX difference hardly. You can't explain this to someone > without apologizing. > > I agree anything Service related belongs on the Kube side of the equation. Unless OpenShift has something special extensions to the Service object that I am not aware of (which is very possible, I am highly ignorant of many things). > .... roland > > > > > >> --Hardy >> >> _______________________________________________ >> Devtools mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/devtools >> > > _______________________________________________ > Devtools mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/devtools > >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
