-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
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
Add a scaling guide under the high availability topic #29388
Comments
@vmuzikar @keycloak/core @ryanemerson I'd like for there to be a topic inbetween the getting start guides and the HA guides around scaling / performance. It would cover at least this issue and #29391. It could be laid out roughly like: Scaling and Performance Intro and when is scaling needed... Vertical scaling:
Horizontal Scaling:
Does something like this seem worthwhile and/or is it covered sufficiently by the HA guide? |
+1. These are all valid considerations for non-ha deployments, so I think it makes sense we document these topics outside of the HA guide.
My understanding is that HA is related to multi-site deployments. I think anti-affinity is an important consideration for single site deployments, so I would include this in your proposed guides. |
closes: keycloak#29388 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
closes: keycloak#29388 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
closes: keycloak#29388 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
@shawkins thank you for logging this issue, I myself was contemplating on something like this to be added to our roadmap. We shall definitely bring this to the team and find time to add more data points. I am also interested in using a Horizontal Pod Autoscaler in our provisioning layer within |
closes: keycloak#29388 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
closes: keycloak#29388 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
closes: keycloak#29388 Signed-off-by: Steve Hawkins <shawkins@redhat.com>
Description
We don't provide guidance around scale up / down. It would be good to mention that infinispan must do rebalancing as members join / leave. It would also be good to describe in rough terms when scale up / down should be done in response to cpu, memory, or throughput limitations.
The text was updated successfully, but these errors were encountered: