feat: add information to maxsurge and maxunavailable

Qovery · Jan 22, 2025 · e8c1797 · e8c1797
1 parent 204b2c6
commit e8c1797
Show file tree

Hide file tree

Showing 2 changed files with 13 additions and 1 deletion.
diff --git a/website/docs/using-qovery/configuration/advanced-settings.md b/website/docs/using-qovery/configuration/advanced-settings.md
@@ -1,5 +1,5 @@
 ---
-last_modified_on: "2025-01-21"
+last_modified_on: "2025-01-22"
 title: "Service Advanced Settings"
 description: "Learn how to set advanced settings on your infrastructure with Qovery"
 ---
@@ -117,6 +117,12 @@ Note: The default value on a GKE cluster is set to 10 GB since by default it for
 |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
 | integer | Define the percentage of a maximum number of pods that can be unavailable during the update process ([more info](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-unavailable)).  | `25`          |
 
+<Alert type="info">
+
+It's important to understand `maxSurge` and `maxUnavailable` govern availability, not strict real-time counting. Don't expect the exact numbers of pods to be unavailable at any given time during a rollout.
+
+</Alert>
+
 #### deployment.update_strategy.rolling_update.max_surge_percent ![](/img/advanced_settings/application.svg) ![](/img/advanced_settings/container.svg)
 
 | Type    | Description                                                                                                                                                                                            | Default Value |

diff --git a/website/docs/using-qovery/configuration/advanced-settings.md.erb b/website/docs/using-qovery/configuration/advanced-settings.md.erb
@@ -105,6 +105,12 @@ Note: The default value on a GKE cluster is set to 10 GB since by default it for
 |---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|
 | integer | Define the percentage of a maximum number of pods that can be unavailable during the update process ([more info](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#max-unavailable)).  | `25`          |
 
+<Alert type="info">
+
+It's important to understand `maxSurge` and `maxUnavailable` govern availability, not strict real-time counting. Don't expect the exact numbers of pods to be unavailable at any given time during a rollout.
+
+</Alert>
+
 #### deployment.update_strategy.rolling_update.max_surge_percent ![](/img/advanced_settings/application.svg) ![](/img/advanced_settings/container.svg)
 
 | Type    | Description                                                                                                                                                                                            | Default Value |