Understood - thanks!

On Thursday, November 30, 2017 at 8:55:31 PM UTC-8, Tim Hockin wrote:
>
> If it came in via the public IP, as you said: 
> `https://PublicIP:31245/app/rest/init` 
> <https://PublicIP:31245/app/rest/init> then the 192 address isn't part 
> of the request. 
>
> On Thu, Nov 30, 2017 at 8:35 PM, Kyunam Kim <kim.k...@gmail.com 
> <javascript:>> 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, Kyunam Kim <kim.k...@gmail.com> 
> 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 - 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 <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 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, the 3rd party 
> web 
> >> >> > app 
> >> >> > starts an internal setup process and errors out by saying 
> >> >> > 'http://192.168/88/100:31245/app/admin' is not reachable from 
> >> >> > 'MY-APP-DEPLOYMENT-768D8FBC5D-CP92L'. 
> >> >> > 
> >> >> > I interpreted this as, Docker container with host name 
> >> >> > MY-APP-DEPLOYMENT-768D8FBC5D-CP92L cannot reach to 
> >> >> > http://192.168/88/100:31245/app/admin. 
> >> >> > 
> >> >> > What k8s' magic can I do to make this container to be able to 
> reach 
> >> >> > 1) 
> >> >> > http://192.168/88/100:31245/app/admin or 2) 
> >> >> > http://172.17.0.7:6443/app/admin 
> >> >> > (Service's Endpoints) ? 
> >> >> > 
> >> >> > Hope this helps. 
> >> >> > 
> >> >> > On Thursday, November 30, 2017 at 2:19:35 PM UTC-8, Rodrigo Campos 
> >> >> > wrote: 
> >> >> >> 
> >> >> >> 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 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' capability do I use to make this happen? 
> >> >> >> 
> >> >> >> 
> >> >> >> Sorry, not sure I follow. Does it work for you using the service 
> >> >> >> name? 
> >> >> >> (Or 
> >> >> >> service+namespace)? 
> >> >> >> 
> >> >> >> Unless you prohibited it in some way (like with network policy, 
> but 
> >> >> >> that 
> >> >> >> is probably not the case) that should work. 
> >> >> >> 
> >> >> >> So, I might be missing something, sorry in advance :) 
> >> >> > 
> >> >> > -- 
> >> >> > You received this message because you are subscribed to the Google 
> >> >> > Groups 
> >> >> > "Kubernetes user discussion and Q&A" group. 
> >> >> > To unsubscribe from this group and stop receiving emails from it, 
> >> >> > send 
> >> >> > an 
> >> >> > email to kubernetes-use...@googlegroups.com. 
> >> >> > To post to this group, send email to kubernet...@googlegroups.com. 
>
> >> >> > Visit this group at 
> https://groups.google.com/group/kubernetes-users. 
> >> >> > For more options, visit https://groups.google.com/d/optout. 
> >> > 
> >> > -- 
> >> > You received this message because you are subscribed to the Google 
> >> > Groups 
> >> > "Kubernetes user discussion and Q&A" group. 
> >> > To unsubscribe from this group and stop receiving emails from it, 
> send 
> >> > an 
> >> > email to kubernetes-use...@googlegroups.com. 
> >> > To post to this group, send email to kubernet...@googlegroups.com. 
> >> > Visit this group at https://groups.google.com/group/kubernetes-users. 
>
> >> > For more options, visit https://groups.google.com/d/optout. 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups 
> > "Kubernetes user discussion and Q&A" group. 
> > To unsubscribe from this group and stop receiving emails from it, send 
> an 
> > email to kubernetes-use...@googlegroups.com <javascript:>. 
> > To post to this group, send email to kubernet...@googlegroups.com 
> <javascript:>. 
> > Visit this group at https://groups.google.com/group/kubernetes-users. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to kubernetes-users+unsubscr...@googlegroups.com.
To post to this group, send email to kubernetes-users@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to