Re: [Dev] Update on Kubernetes setup

2016-08-02 Thread Imesh Gunaratne
Hi Abhishek, Please always send mails to WSO2 Dev except when you have sensitive information (such as credentials, etc) to share with us. On Wed, Aug 3, 2016 at 10:29 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi Mentors, > > I am able to run Kubernetes cluster on my Mac now a

Re: [Dev] Update on Kubernetes setup

2016-08-03 Thread Abhishek Tiwari
Hi Imesh, Most important issue was the IP address of docker container is not accessibly directly, so I added a config in the test-config.json to specify docker-machine ip address. If it is not present, I try to get the IP address of the docker container. Vishanth, I am still working on completing

Re: [Dev] Update on Kubernetes setup

2016-08-03 Thread Vishanth Balasubramaniam
Alright Abhishek. On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi Imesh, > > Most important issue was the IP address of docker container is not > accessibly directly, so I added a config in the test-config.json to specify > docker-machine ip address. I

Re: [Dev] Update on Kubernetes setup

2016-08-03 Thread Imesh Gunaratne
​Hi Abhishek,​ On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi Imesh, > > Most important issue was the IP address of docker container is not > accessibly directly, so I added a config in the test-config.json to specify > docker-machine ip address. If i

Re: [Dev] Update on Kubernetes setup

2016-08-04 Thread Abhishek Tiwari
Hi Imesh, I am not trying access container in K8S, this problem was while running tests for regular container deployement (which we call default platform). Thanks Abhishek On Wednesday, August 3, 2016, Imesh Gunaratne wrote: > > ​Hi Abhishek,​ > > On Thu, Aug 4, 2016 at 9:39 AM, Abhishek Tiwar

Re: [Dev] Update on Kubernetes setup

2016-08-04 Thread Imesh Gunaratne
On Fri, Aug 5, 2016 at 7:29 AM, Abhishek Tiwari < abhishek.tiwari0...@gmail.com> wrote: > Hi Imesh, > > I am not trying access container in K8S, this problem was while running > tests for regular container deployement (which we call default platform). > ​Right, we might not need to consider stand