On Wed, May 10, 2017 at 9:15 AM, Gerard Braad <[email protected]> wrote:
> Hi, > > On Wed, May 10, 2017 at 2:58 AM, Lalatendu Mohanty <[email protected]> > 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@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 > [email protected] > https://www.redhat.com/mailman/listinfo/devtools > -- Praveen Kumar https://fedoraproject.org/wiki/User:Kumarpraveen
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
