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, Kyunam Kim
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, Kyunam Kim wrote:
> service IP
>
> On Thursday, November 30, 2017 at 3:32:07 PM UTC-8, Tim Hockin wrote:
>>
>> It's not clear what 192 address represents -
service IP
On Thursday, November 30, 2017 at 3:32:07 PM UTC-8, Tim Hockin wrote:
>
> It's not clear what 192 address represents - the pod IP, the service
> IP, or an external LB IP?
>
> Also note that you have / characters where you need . characters - I
> assume that is human error is
It's not clear what 192 address represents - the pod IP, the service
IP, or an external LB IP?
Also note that you have / characters where you need . characters - I
assume that is human error is reporting the issue?
On Thu, Nov 30, 2017 at 3:27 PM, Kyunam Kim wrote:
> I'm
I'm not that smart to prohibit anything in k8s yet ;-)
Let me retry.
My docker container runs a 3rd party web application over which I have no
control and I have successful deployed it in k8s.
I can access it thru https://192.168.99.100:31245.
When I call https://PublicIP:31245/app/rest/init,
On Thursday, November 30, 2017, Kyunam Kim 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 the external world.
> I want a container(s) to be
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'