mirror of
https://github.com/zitadel/zitadel.git
synced 2025-01-05 22:52:46 +00:00
docs(ta): add type expected downtime during update (#6818)
Co-authored-by: Silvan <silvan.reusser@gmail.com>
This commit is contained in:
parent
0dec125e6b
commit
61d86343a0
@ -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.
|
||||
|
Loading…
x
Reference in New Issue
Block a user