On Mon, Jul 30, 2018 at 3:18 PM Lalatendu Mohanty <[email protected]> wrote:
> > > On Mon, Jul 30, 2018 at 8:42 PM, Burr Sutter <[email protected]> wrote: > >> >> >> On Mon, Jul 30, 2018 at 2:57 AM Lalatendu Mohanty <[email protected]> >> wrote: >> >>> >>> >>> On Mon, Jul 30, 2018 at 7:36 AM, Gerard Braad <[email protected]> wrote: >>> >>>> Hi Burr, >>>> >>>> >>>> About monthly we try to sync up with them and exchange issues we share >>>> and discuss possible solutions. >>>> We try to align with Minikube feature-wise, but at the moment we have >>>> no bandwidth to handle porting changes back. >>>> Portability between our implementations is not the biggest problem, as >>>> long as you can guarantee an application deploys on both kubernetes and >>>> openshift in the same way. >>>> >>>> >>> If we put effort into this, would you be able to show a demo that we >>>> could use as a base line for this attempt? >>>> It would also help if you create an issue for us to discuss and track >>>> progress and issues along the way. >>>> Especially as it allows us to refer to issues/and questions at >>>> Minikube's end too. >>>> >>>> >>>> Gerard >>>> >>>> On Sun, Jul 29, 2018 at 12:22 AM Burr Sutter <[email protected]> >>>> wrote: >>>> >>>>> I saw about 200 users this week, but they were primarily "real >>>>> customers" since it was organized by our sales team - aka high quality >>>>> "leads". >>>>> >>>>> Next, the first whole week of August, my guess is that we will see >>>>> another 200 to 300 "real customers" (sales team organized) but I also have >>>>> about 400 off-the-street folks (organized by O'rielly Safari [1]). >>>>> >>>>> This later batch of people need me to be much more "kubernetes >>>>> upstream friendly", so I have a few questions along those lines. >>>>> >>>>> Which version of Minikube matches Minishift? >>>>> >>>> >>> >>> I just check Minikube 0.28.2 and if we compare major features Minishift >>> vs Minikube, Minishift has all the features of Minikube and some more. >>> However there is difference in the way these features are implemented. >>> >> >> I started working with minikube 0.28.1 - I wanted Kubernetes 1.10 and >> guessed it might be the right one >> >> I have now also seen a feature mismatch - like "minikube profile list" >> and "minikube profile set myprofile" does not seem to work. >> > > Because Minikube has some half baked features. If we want to have same > features implemented in Minikube then it wont be copy pasting code but we > need to spend considerable amount of work for this. They do not share the > same code base now. > > Question: When you use Minikube and Minishift do you feel they are equally > polished or one is better than the other? > I find them to be fairly equal except for: - minikube start up is a LOT faster - minikube profiles are not worth using - not sure what the equivalent of "oc project" is in "kubectl" - what namespace am I in? - minishift addon enable admin-user is unique otherwise, they feel basically the same so far. I have not yet completed my demo scripts, perhaps I will run across something else that feels different. the first "demo script" (or lab) is about done here: https://github.com/burrsutter/9stepsawesome/blob/master/1_installation_ready.adoc > >> >>> >>> >>>> https://github.com/kubernetes/minikube/releases >>>>> https://github.com/minishift/minishift/releases >>>>> Is there an easy way (or documented way) to match these up? >>>>> >>>> >>> We never documented this. Personally I feel Minikube is not maintained >>> properly and some of its features are half baked. Do you need an >>> comparative writeup? >>> >> >> Yes and No :-) >> >> I think the task is pretty simple. On the both "releases" pages, it >> should indicate what version of Kubernetes/Openshift it is bringing along >> by default - this will then allow the user to pick the right version of >> kubectl as well. >> >> I do like how minikube's releases page offers "how to install" docs. >> >> By the way, I like telling people that minikube is the upstream to >> minishift >> much like Kubernetes is the upstream to OpenShift >> and kubectl is to oc. >> > > Minikube is not upstream to Minishift. The code base has diverged and it > can not be converged now. The code has diverged because we have different > mechanism to provision Kubernetes vs OpenShift. > > We have gone back and forth on this. We do not see any value from code > point of view if we make Minikube as our upstream. From marketing point of > view there might be value as you mentioned but for us it would be double > work. > > >> I am not sure if the minikube team has download numbers but I am betting >> they have seen a dramatic growth over the last 12 months as numerous 3rd >> parties are starting to offer "training" on Kubernetes via minikube. >> > > Yes, they get higher numbers than Minishift because Kubernetes has a > bigger community i.e. higher download numbers are not because Minikube is > awesome. Please correct me if I am wrong. > > > If you want to benefited from Minikube community then we should add code > in Minikube to provision OpenShift (not the default but if user wants) , > but then user gets confused around what to use for OpenShift. IMO both > should not co-exist. > > May be it is time we should take another look what we can do to address > this issue. > > -Lala > > >> >>> >>> >>>>> Ideally, my demos/labs are fully portable between minikube and >>>>> minishift. >>>>> >>>>> [1] >>>>> https://www.safaribooksonline.com/live-training/courses/9-steps-to-awesome-with-kubernetes/0636920196099/ >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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
