[Devtools] minishift promotion

[James Strachan]

minikube has support for the command too "minikube service" though it only
understands nodeports AFAIK. On openshift we need to detect & support
Routes and/or nodeports depending on if there's a Route or service of type
NodePort

On Wed, May 10, 2017 at 12:34 PM, Burr Sutter <bsutter at redhat.com> wrote:

> That sounds interesting, how does minikube deal with this scenario?
>
> Perhaps my thinking is warped but by default, Services are inside the
> cluster, therefore you need to be inside the VM in order to curl them
>
> On Wed, May 10, 2017 at 12:29 PM James Strachan <jstracha at redhat.com>
> wrote:
>
>> FWIW gofabric8 has a 'gofabric8 service foo' which shows the URL to
>> access a service via its route / nodeport / ingress etc. Its pretty simple
>> code; we use something similar in funktion (funktion url foo)
>>
>> Maybe we need to add the service command to minishift too?
>>
>>
>> On Wed, May 10, 2017 at 12:08 PM, Burr Sutter <bsutter at redhat.com> wrote:
>>
>>> What is the trick to always get a nodeport for every Service I create?
>>> Right now, I do need the oc binary INSIDE the VM because I like to show
>>> that Services are normally in-VM only and Routes make them visible to the
>>> outside world (my laptops OS)
>>>
>>> But I can likely make the same point with nodeport
>>>
>>>
>>> On Wed, May 10, 2017 at 4:52 AM Praveen Kumar <prkumar at redhat.com>
>>> wrote:
>>>
>>>> On Wed, May 10, 2017 at 9:15 AM, Gerard Braad <gbraad at redhat.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> On Wed, May 10, 2017 at 2:58 AM, Lalatendu Mohanty <
>>>>> lmohanty at redhat.com> wrote:
>>>>> > Sure will do. With CDK 3 we do not have Kubernetes bits in the
>>>>> ISO/VM e.g.
>>>>> > kubectl binary. So we need to figure out if it is just the extra
>>>>> kubectl we
>>>>> > need or something else.
>>>>>
>>>>> `kubectl` should be treated like `oc`, and should therefore not be
>>>>> part of the ISO/VM for Minishift/CDK 3?
>>>>>
>>>>
>>>> Adding `kubectl` binary to iso shouldn't be intention but it should be
>>>> treated like 'oc'. We are already advertising openshift as enterprise ready
>>>> kubernetes so kube related stuff should work as expected IMO.
>>>>
>>>>
>>>>> However, reading the instructions, this behaviour is also different
>>>>> for `oc`
>>>>>
>>>>>
>>>>> rhel-ose$ vagrant ssh
>>>>> #Inside CDK shell - Create a Kubernetes context - We will use the
>>>>> OpenShift Client (oc) as as shortcut
>>>>> [vagrant at rhel-cdk ~]$ oc login -u openshift-dev -p devel
>>>>>
>>>>>
>>>>> which means that `oc` is on the path inside the VM. is this still the
>>>>> case for CDK 3.x?
>>>>>
>>>>
>>>> No, we did this for CDK-2.x because it was required to provision
>>>> openshift inside the VM but right now we are using client binary outside VM
>>>> to provision it.
>>>>
>>>>
>>>>>
>>>>> WDYT?
>>>>>
>>>>>
>>>>> Gerard
>>>>>
>>>>
>>>>> _______________________________________________
>>>>> Devtools mailing list
>>>>> Devtools at redhat.com
>>>>> https://www.redhat.com/mailman/listinfo/devtools
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Praveen Kumar
>>>> https://fedoraproject.org/wiki/User:Kumarpraveen
>>>> _______________________________________________
>>>> Devtools mailing list
>>>> Devtools at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/devtools
>>>>
>>>
>>> _______________________________________________
>>> Devtools mailing list
>>> Devtools at redhat.com
>>> https://www.redhat.com/mailman/listinfo/devtools
>>>
>>>
>>
>>
>> --
>> James
>> -------
>> Red Hat
>>
>> Twitter: @jstrachan
>> Email: james.strachan at gmail.com
>> Blog: https://medium.com/@jstrachan/
>>
>> fabric8: https://fabric8.io/
>> open source development platform
>>
>> funktion: https://funktion.fabric8.io/
>> open source event based lambda programming
>>
>


-- 
James
-------
Red Hat

Twitter: @jstrachan
Email: james.strachan at gmail.com
Blog: https://medium.com/@jstrachan/

fabric8: https://fabric8.io/
open source development platform

funktion: https://funktion.fabric8.io/
open source event based lambda programming
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/devtools/attachments/20170510/c163c590/attachment.htm>