Log in to each VM and try accessing the service's clusterIP, eg with curl. Try connecting to the VM IP on the service node port.
On Wed, Nov 22, 2017 at 1:39 PM, <tomnola...@gmail.com> wrote: > So the application is created using Flask, which is a python web-framework. > Logging into the application is simply done by querying the db and then > retrieving a User. It is handled by the Flask-Login module which stores > user-session data in cookies <https://flask-login.readthedocs.io/en/latest/> > > There's no errors in kube-proxy logs. What else could possibly be causing > this? > > -- > 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. -- 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.
