.
>
> On Thu, Nov 30, 2017 at 8:35 PM, Kyunam Kim <kim.k...@gmail.com
> > wrote:
> > my guess is that the 3rd party web app copied it from the request.
> >
> > On Thursday, November 30, 2017 at 4:30:03 PM UTC-8, Tim Hockin wrote:
> >>
> >&
my guess is that the 3rd party web app copied it from the request.
On Thursday, November 30, 2017 at 4:30:03 PM UTC-8, Tim Hockin wrote:
>
> Did you tell the app about the 192 address? How did it know that IP
> to redirect you?
>
> On Thu, Nov 30, 2017 at 4:07 PM, Ky
hat is human error is reporting the issue?
>
>
> On Thu, Nov 30, 2017 at 3:27 PM, Kyunam Kim <kim.k...@gmail.com
> > wrote:
> > I'm not that smart to prohibit anything in k8s yet ;-)
> > Let me retry.
> >
> > My docker container runs a 3rd party web applicatio
:
>
> On Thursday, November 30, 2017, Kyunam Kim <kim.k...@gmail.com
> > wrote:
>
>> How do I make a container aware of the service's IP:NodePort or
>> ClusterIP:port address?
>> Let's say, I can access my application at http://public-ip:port/myapp
>> from th
How do I make a container aware of the service's IP:NodePort or
ClusterIP:port address?
Let's say, I can access my application at http://public-ip:port/myapp from
the external world.
I want a container(s) to be able to reach to http://public-ip:port
Or
to reach to ClusterIP:port.
What k8s'
