to communicate between your botkit-dev pods and api pods, read about
kubernetes service. They solve exactly that problem :)
On Mon, Feb 20, 2017 at 8:21 PM, Norman Khine wrote:
> It is only for internal usage between the two containers.
>
> one more question - what if i have another container but
It is only for internal usage between the two containers.
one more question - what if i have another container but which is in a
different pod, how would i connect to it without having to go out of the
ELB, for example, i have a botkit that needs to talk to the API container
that is in another pod
Local host or 127.0.0.1, depends if the service binds to ipv4 only and how
your client connects. But if local host doesn't work, try 127.0.0.1 :-)
On Monday, February 20, 2017, 'Tim Hockin' via Kubernetes user discussion
and Q&A wrote:
> 0.0.0.0 is valid as a bind-to address, meaning "any IP", b
0.0.0.0 is valid as a bind-to address, meaning "any IP", but as a
connect-to address you probably want 'localhost'
On Mon, Feb 20, 2017 at 2:11 PM, Matthias Rampke wrote:
> I see three containers in this.
>
> Yes, 0.0.0.0: should work if the graphql container binds to all
> interfaces. Try it
I see three containers in this.
Yes, 0.0.0.0: should work if the graphql container binds to all
interfaces. Try it out?
On Mon, Feb 20, 2017, 21:01 Norman Khine wrote:
> Hello, I have the following template file which has 2 containers:
>
>
> containers:
> - name: api
>
Hello, I have the following template file which has 2 containers:
containers:
- name: api
ports:
- containerPort: 3000
env:
- name: SERVERLESS_ENDPOINT
value: http://0.0.0.0:
- name: media
ports:
