From cd75c246295fcee5ac909e6fa5b305a3d12b2043 Mon Sep 17 00:00:00 2001
From: Stefan Cordes <50696194+ca-stefan-cordes@users.noreply.github.com>
Date: Tue, 25 Feb 2025 12:18:57 +0100
Subject: [PATCH] Major LTS Zero limitiation

See https://help.salesforce.com/s/case-view?caseId=500Hx00000k8KS8IAM
---
 cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc b/cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc
index d4bdd89f..add56289 100644
--- a/cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc
+++ b/cloudhub-2/modules/ROOT/pages/ch2-architecture.adoc
@@ -203,7 +203,7 @@ These services do not process or transmit your data.
 == Availability and Scalability
 
 CloudHub 2.0 is designed to be highly available and scalable through redundancy,
-intelligent healing, and zero-downtime updates.
+intelligent healing, and zero-downtime updates (within same LTS/Edge version).
 It also enables you to scale and benefit from added reliability using
 xref:ch2-clustering.adoc[clustering].
 
@@ -227,6 +227,7 @@ CloudHub 2.0 supports updating your applications at runtime so end users of your
 If the application uses the rolling update deployment model, CloudHub 2.0 keeps the old version of your application running while your application update is deploying.
 Your domain points to the old version of your application until the newly uploaded version is fully started.
 This allows you to keep servicing requests from your old application while the new version of your application is starting.
+Zero Downtime is not available when switching from one LTS version to next major LTS version. You need to deploy with "recreate" deployment strategy.
 
 === Clustering