Please help: with Kubernetes/SpringBoot deployment / can't log into Cockpit

Camunda 7 Topics Discussion & Questions
1

We deploy Camunda to Azure using Kubernetes. As reported in other forum posts, we are not able to login to the Cockpit. We get “Wrong credentials, locked user or missing access rights to application”. When we shut down all the pods except one we are then able to log in.

We’ve read that the general solution to the problem is to use sticky sessions and we’ve made some attempts, but, alas, with no luck. I’m an experienced Camunda developer and really need to get into the Cockpit to perform trouble shooting, but I have little Kubernetes experience and no Azure experience. I have enlisted the help of engineers who do have the necessary skills to figure this out, but so far they have been unsuccessful.

The only information that I have from them is that the configuration pasted in below did not work.

Would someone be willing to help us with this? Any help is appreciated. Thanks

Screen Shot 2022-05-27 at 3.22.58 PM
Screen Shot 2022-05-27 at 3.22.58 PM1528×1090 171 KB

2

How many pods do you have for the application? Try with one to eliminate the sticky sessions setup.

3

Yes, when we go to having one pod, we can log in. That has been our workaround. But the point is, we need it to work with multiple pods. Perhaps, I’m not completely understanding your comment.

4

Which confirms that the pod configuration works, and your ingress works (generally).
So that nails it down specifically to sticky sessions.

Does your service point to any other ingresses? There’s a note at the bottom of the NGINX page indicating that if the service has multiple ingresses, sticky sessions won’t work.