From a6437956ce16e6f2dcd232d0529eba149ed4483f Mon Sep 17 00:00:00 2001 From: Omer Aplatony Date: Fri, 10 Jan 2025 13:45:56 +0200 Subject: [PATCH] Update vertical-pod-autoscaler/docs/sidecar-containers.md Co-authored-by: Marco Voelz --- vertical-pod-autoscaler/docs/sidecar-containers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vertical-pod-autoscaler/docs/sidecar-containers.md b/vertical-pod-autoscaler/docs/sidecar-containers.md index 634a21bbebf..2fcd5226064 100644 --- a/vertical-pod-autoscaler/docs/sidecar-containers.md +++ b/vertical-pod-autoscaler/docs/sidecar-containers.md @@ -19,7 +19,7 @@ When you create a VPA resource for a pod, it automatically attempts to manage AL This default "manage everything" approach can cause problems with sidecars because: - Sidecar containers often have their own resource requirements set by their injection webhooks - VPA's automatic management may conflict with these requirements -- Without proper handling, this can lead to resource conflicts and pod instability +- Without proper handling, this can lead to problems like endless eviction loops Example of a VPA resource that explicitly configures one container but affects all: