From 61d86343a0b6765843c5df29da357a539d27ef2d Mon Sep 17 00:00:00 2001 From: mffap Date: Thu, 26 Oct 2023 15:10:34 +0200 Subject: [PATCH] docs(ta): add type expected downtime during update (#6818) Co-authored-by: Silvan --- docs/docs/support/technical_advisory.mdx | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/docs/support/technical_advisory.mdx b/docs/docs/support/technical_advisory.mdx index 28eb02a2d1..acc91234e8 100644 --- a/docs/docs/support/technical_advisory.mdx +++ b/docs/docs/support/technical_advisory.mdx @@ -159,3 +159,10 @@ A breaking behavior change refers to a modification or update that changes the b This change does not necessarily affect the APIs or any functions you are calling, so it may not require an update to your code. However, if you rely on specific results or behaviors, they may no longer be guaranteed after the change is implemented. Therefore, it is important to be aware of breaking behavior changes and their potential impact on your use of ZITADEL, and to take appropriate action if needed to ensure continued functionality. + +### Expected downtime during upgrade + +Expected downtime during upgrade means that ZITADEL might become unavailable during and upgrade. +ZITADEL is built for [zero downtime upgrades](/docs/concepts/architecture/solution#zero-downtime-updates) at upgrades can be executed without downtime by just updating to a more recent version. +When deploying certain changes a zero downtime upgrade might not be possible, for example to guarantee data integrity. +In such cases we will issue a technical advisory to make you aware of this unexpected behavior.