We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
master
Hello folks I am not sure if this is a bug or in general how its supposed to be but this is on the intersection of Ops and Dev.
So my case is that I deploy kafka-ui on a k8s cluster, with basic auth enabled.
AUTH_TYPE: "LOGIN_FORM" SPRING_SECURITY_USER_NAME: admin SPRING_SECURITY_USER_PASSWORD: ${PROD_PWD}
Everything is fine - Until I try to naively scale the deployment from 1 instance to 2. Replicas to K8s lingo on the helm deployment.
Replicas to K8s lingo
replicas: 1
What I think is happening is that you get 2 identical instances of Kafka-UI - (pods) deployed.
Naively I would expect It would work,
Deploy 2 instances of kafka-ui under the same k8s service or behind a Load Balancer no sticky sessions.
replicas: 2
Not Available
Authentication failures
No response
The text was updated successfully, but these errors were encountered:
Hello there javapapo! 👋
Thank you and congratulations 🎉 for opening your very first issue in this project! 💖
In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀
Sorry, something went wrong.
I guess there is no solution - since the Spring Security context is not shared... so you can not loadbalance.
Hi, this repo is not maintained (#4255). Glad to help you here though: https://github.com/kafbat/kafka-ui
oops!
Thanks @Haarolean - will try to migrate to the new-deployment.
No branches or pull requests
Issue submitter TODO list
master
-labeled docker image and the issue still persists thereDescribe the bug (actual behavior)
Hello folks I am not sure if this is a bug or in general how its supposed to be but this is on the intersection of Ops and Dev.
So my case is that I deploy kafka-ui on a k8s cluster, with basic auth enabled.
Everything is fine - Until I try to naively scale the deployment from 1 instance to 2.
Replicas to K8s lingo
on the helm deployment.What I think is happening is that you get 2 identical instances of Kafka-UI - (pods) deployed.
Expected behavior
Naively I would expect It would work,
Your installation details
Steps to reproduce
Deploy 2 instances of kafka-ui under the same k8s service or behind a Load Balancer no sticky sessions.
What I think is happening is that you get 2 identical instances of Kafka-UI - (pods) deployed.
Screenshots
Not Available
Logs
Authentication failures
Additional context
No response
The text was updated successfully, but these errors were encountered: