upstream/keycloak
1
0
Fork 0
mirror of https://github.com/keycloak/keycloak.git synced 2026-06-03 22:03:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 18

update docs regarding to use statefulset and not a deployment

Browse source 
Closes #40090

Signed-off-by: AvivGuiser <avivguiser@gmail.com>
This commit is contained in:
AvivGuiser 2025-06-30 15:23:06 +03:00 committed by GitHub
parent df13273bac
commit 3a87dcd2eb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/guides/getting-started/getting-started-kube.adoc
View file

@ -32,7 +32,7 @@ minikube addons enable ingress
The {project_name} QuickStarts repository includes some example files to help deploy {project_name} to Kubernetes.
As a first step, create the {project_name} deployment and service by entering the following command:
As a first step, create the {project_name} statefulset and service by entering the following command:
[source,bash,subs="attributes+"]
----

2
docs/guides/getting-started/getting-started-scaling-and-tuning.adoc
View file

@ -47,7 +47,7 @@ If you are not using the Operator, please review the following:
- Your instances need a way to discover each other. For more information, see discovery in <@links.server id="caching" />.
- This cache is not optimal for clusters that span multiple availability zones, which are also called stretch clusters. For embedded Infinispan cache, work to have all instances in one availability zone. The goal is to avoid unnecessary round-trips in the communication that would amplify in the response times. On Kubernetes, use Pod affinity to enforce this grouping of Pods.
- This cache does not gracefully handle multiple members joining or leaving concurrently. In particular, members leaving at the same time can lead to data loss. On Kubernetes, you can use a StatefulSet with the default serial handling to ensure Pods are started and stopped sequentially.
- This cache does not gracefully handle multiple members joining or leaving concurrently. In particular, members leaving at the same time can lead to data loss. On Kubernetes, use a StatefulSet with the default serial handling to ensure Pods are started and stopped sequentially, using a deployment is not supported or recommended.
To avoid losing service availability when a whole site is unavailable, see the high availability guide for more information on a multi-site deployment. See <@links.ha id="introduction" />.