Merge pull request #8620 from ialidzhikov/enh/vpa-update-modes-docs

docs: Update VPA update mode docs

Author: k8s-ci-robot

vertical-pod-autoscaler/docs/quickstart.md

@@ -14,16 +14,16 @@ each controller that you want to have automatically computed resource requiremen
 This will be most commonly a **Deployment**.
 There are five modes in which *VPAs* operate:
 
-- `"Auto"` (**Deprecated**): VPA assigns resource requests on pod creation as well as updates
+- `"Auto"` [__deprecated__]: 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). **This mode is deprecated and will be removed in a future API version.**
   **Use explicit modes like "Recreate", "Initial", or "InPlaceOrRecreate" instead.**
-- `"Recreate"`: VPA assigns resource requests on pod creation as well as updates
+- `"Recreate"` [__default__]: 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).
   This mode should be used rarely, only if you need to ensure that the pods are restarted
   whenever the resource request changes.
-- `"InPlaceOrRecreate"`[__alpha feature__]: VPA assigns resource requests on pod creation as well as updates
+- `"InPlaceOrRecreate"`[__beta feature__]: VPA assigns resource requests on pod creation as well as updates
   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.
   If `in-place` update fails, it falls back to evicting the pods, performing a _recreation_.
   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).