diff --git a/docs/FAQ.md b/docs/FAQ.md
index 2d1b4ec116..2c608f2f23 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -325,3 +325,15 @@ The query engine may behave differently for some functions. Please see [this art
 ## If downsampling and deduplication are enabled how will this work?
 
 [Deduplication](https://docs.victoriametrics.com/#deduplication) is a special case of zero-offset [downsampling](https://docs.victoriametrics.com/#downsampling). So, if both downsampling and deduplication are enabled, then deduplication is replaced by zero-offset downsampling
+
+## How to upgrade or downgrade VictoriaMetrics without downtime?
+
+Single-node VictoriaMetrics cannot be restarted / upgraded or downgraded without downtime, since it needs to be gracefully shut down and then started again. See [how to upgrade VictoriaMetrics](https://docs.victoriametrics.com/#how-to-upgrade-victoriametrics).
+
+[Cluster version of VictoriaMetrics](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html) can be restarted / upgraded / downgraded without downtime if the following conditions are met:
+
+* If every component of the cluster - `vminsert`, `vmselect` and `vmstorage` - has at least 2 instances.
+* If the cluster has enough compute resources (CPU, RAM, disk IO, network bandwidth) to perform rolling restart of all its components.
+* If the version used for upgrade / downgrade is compatible with the currently running version. The [CHANGELOG](https://docs.victoriametrics.com/CHANGELOG.html) contains compatibility notes for the published releases.
+
+See [updating / reconfiguring cluster nodes](https://docs.victoriametrics.com/Cluster-VictoriaMetrics.html#updating--reconfiguring-cluster-nodes) for details on cluster upgrade.