Re: [kubernetes-users] Unexpected Behavior When Scaling Application

If you repeatedly. Curl it always gives the right answer? Can you verify that from both VMs? What is the error case? You said "the home page" - is that your apps home page or something else? On Nov 22, 2017 5:23 PM, wrote: > Thanks for sticking with me Tim. > > So what I currently have is a p

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

Thanks for sticking with me Tim. So what I currently have is a pod that has two containers in it. One container has the port 5000 and one has the port 5432. When I run `kubectl get pods` I can see my the IP for my pod and I can curl that from any machine. I exposed this deployment using `kubect

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

Sorry. When you `kubectl get services` you get a listing which includes the "cluster IP" of a service. This is a VIP that is reachable by your cluster nodes. You can SSH into a VM and curl your cluster IP and it will give us a clue where the process is breaking down. In particular, curl it 100

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

When you say curl the Services custerIP, what do you mean? Which service? I'm relatively new to kubernetes/GCP so still finding my feet. -- 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 st

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

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, wrote: > So the application is created using Flask, which is a python web-framework. > Logging into the application is simply done b

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

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

[kubernetes-users] Ansible if kubeadm init/join was already run

Hi, I'm wrapping kubeadm in an Ansible playbook. I want to skip init and join tasks if they were already successfully run. Is there a recommended command to check kubeadm status for automation tools? -- You received this message because you are subscribed to the Google Groups "Kubernetes user

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

Things to try: Log in to each VM and try accessing the service's clusterIP, eg with curl. Make sure kube-proxy is running on both VMs. Check kube-proxy logs for any obvious errors, like failure to sync with master. Try connecting to the VM IP on the service node port. On Nov 22, 2017 5:49 AM

Re: [kubernetes-users] Unexpected Behavior When Scaling Application

If I have to bet, I'd bet it's the application. But okay, that is what you see. But else do you see in Kubernetes? Logs of kube-proxy, etc.? How do you keep the users logged in the application? Is there any container restart when this happens? Are you using GKE? And how do you connect, via a pub

[kubernetes-users] Unexpected Behavior When Scaling Application

Hi there, I’ve deployed an application to a Google Cloud Kubernete Cluster. The application is built using the Python web-framework Flask and uses a CloudSQL Postgres database for persistence. The script I used to deploy the application is this: https://gist.github.com/tnolan8/85e91394d9ec1327f