From 3a1842b83b113d689256678df7f52ca45e8588af Mon Sep 17 00:00:00 2001
From: Stoyan Vitanov <stoyan.vitanov@sap.com>
Date: Thu, 29 May 2025 12:23:43 +0300
Subject: [PATCH] docs(vpa): Remove redundant `in-place` reference from
`"Auto"` updateMode
This commit removes the now redundant mention of `in-place`
capability from `"Auto"` as the currently released version `v1.4.0` does
not instrument `in-place` updates as an `"Auto"` default strategy.
As of now, `"Auto"` preserves it's behavior to perform `"Recreate"` when
specified.
There is a separate `updateMode` (the `"InPlaceOrRecreate"`) specified
within the `quickstart.md` guide that handles `in-place` updates.
---
vertical-pod-autoscaler/docs/quickstart.md | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/vertical-pod-autoscaler/docs/quickstart.md b/vertical-pod-autoscaler/docs/quickstart.md
index 59f6352a0f..bf59b1f44e 100644
--- a/vertical-pod-autoscaler/docs/quickstart.md
+++ b/vertical-pod-autoscaler/docs/quickstart.md
@@ -16,9 +16,7 @@ There are four modes in which *VPAs* operate:
- `"Auto"`: VPA assigns resource requests on pod creation as well as updates
them on existing pods using the preferred update mechanism. Currently, this is
- equivalent to `"Recreate"` (see below). Once restart free ("in-place") update
- of pod requests is available, it may be used as the preferred update mechanism by
- the `"Auto"` mode.
+ equivalent to `"Recreate"` (see below).
- `"Recreate"`: VPA assigns resource requests on pod creation as well as updates
them on existing pods by evicting them when the requested resources differ significantly
from the new recommendation (respecting the Pod Disruption Budget, if defined).
--
GitLab