From 3a87dcd2eb8c438f0433b67a1e60d9364e582ea4 Mon Sep 17 00:00:00 2001 From: AvivGuiser Date: Mon, 30 Jun 2025 15:23:06 +0300 Subject: [PATCH] update docs regarding to use statefulset and not a deployment Closes #40090 Signed-off-by: AvivGuiser --- docs/guides/getting-started/getting-started-kube.adoc | 2 +- .../getting-started/getting-started-scaling-and-tuning.adoc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/getting-started/getting-started-kube.adoc b/docs/guides/getting-started/getting-started-kube.adoc index 72dbae0bc08..727de6f402b 100644 --- a/docs/guides/getting-started/getting-started-kube.adoc +++ b/docs/guides/getting-started/getting-started-kube.adoc @@ -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+"] ---- diff --git a/docs/guides/getting-started/getting-started-scaling-and-tuning.adoc b/docs/guides/getting-started/getting-started-scaling-and-tuning.adoc index c87789c724e..9775dee8e8b 100644 --- a/docs/guides/getting-started/getting-started-scaling-and-tuning.adoc +++ b/docs/guides/getting-started/getting-started-scaling-and-tuning.adoc @@ -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" />.