Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@ryanemerson
Copy link
Contributor

@ryanemerson ryanemerson commented Sep 3, 2025

Closes #42305

The {project_name} single-cluster setup is targeted at use cases that:

* Deploy to an infrastructure with transparent networking, like for example a single {kubernetes} cluster.
* Desire all healthy ${project_name} instances to handle user requests.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ahus1 I changed this from "all nodes serve traffic" as "node" is overloaded in the context of Kubernetes and ultimately it's user requests being routed to the instances. Happy to revert though if you have strong opinions on this.

@ryanemerson ryanemerson marked this pull request as ready for review September 3, 2025 09:48
@ryanemerson ryanemerson requested review from a team as code owners September 3, 2025 09:48
@ryanemerson
Copy link
Contributor Author

Thanks for the fix @ahus1, too much bash for me today it seems 🙂

@ahus1 ahus1 merged commit 4fec0a8 into keycloak:main Sep 3, 2025
54 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document that single-cluster deployments expect all Keycloak instances to serve traffic

2 participants