You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: vertical-pod-autoscaler/docs/quickstart.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,19 +12,20 @@ resource requests for your pods.
12
12
In order to use it, you need to insert a *Vertical Pod Autoscaler* resource for
13
13
each controller that you want to have automatically computed resource requirements.
14
14
This will be most commonly a **Deployment**.
15
-
There are four modes in which *VPAs* operate:
15
+
There are five modes in which *VPAs* operate:
16
16
17
17
-`"Auto"`: VPA assigns resource requests on pod creation as well as updates
18
18
them on existing pods using the preferred update mechanism. Currently, this is
19
-
equivalent to `"Recreate"` (see below). Once restart free ("in-place") update
20
-
of pod requests is available, it may be used as the preferred update mechanism by
21
-
the `"Auto"` mode.
19
+
equivalent to `"Recreate"` (see below).
22
20
-`"Recreate"`: VPA assigns resource requests on pod creation as well as updates
23
21
them on existing pods by evicting them when the requested resources differ significantly
24
22
from the new recommendation (respecting the Pod Disruption Budget, if defined).
25
23
This mode should be used rarely, only if you need to ensure that the pods are restarted
26
-
whenever the resource request changes. Otherwise, prefer the `"Auto"` mode which may take
27
-
advantage of restart-free updates once they are available.
24
+
whenever the resource request changes.
25
+
-`"InPlaceOrRecreate"`[__alpha feature__]: VPA assigns resource requests on pod creation as well as updates
26
+
them on existing pods by leveraging [Kubernetes `in-place` update](https://kubernetes.io/blog/2025/05/16/kubernetes-v1-33-in-place-pod-resize-beta/) capability.
27
+
If `in-place` update fails, it falls back to evicting the pods, performing a _recreation_.
28
+
For more details, see the [In-Place Updates documentation](https://github.com/kubernetes/autoscaler/blob/master/vertical-pod-autoscaler/docs/features.md#in-place-updates-inplaceorrecreate).
28
29
-`"Initial"`: VPA only assigns resource requests on pod creation and never changes them
29
30
later.
30
31
-`"Off"`: VPA does not automatically change the resource requirements of the pods.
0 commit comments