From 5f6eb26d5a2389f4fa83d34e8eea2613f0f20fe5 Mon Sep 17 00:00:00 2001 From: Daniel Date: Tue, 5 Jun 2018 11:48:53 +0530 Subject: [PATCH] Update vertical-pod-autoscaler.md Minor spelling mistake --- .../design-proposals/autoscaling/vertical-pod-autoscaler.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md b/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md index 13d235f83..d990d7dbe 100644 --- a/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md +++ b/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md @@ -558,7 +558,7 @@ VPA controls the request (memory and CPU) of containers. In MVP it always sets the limit to infinity. It is not yet clear whether there is a use-case for VPA setting the limit. -The request is calculated based on analysis of the current and revious runs of +The request is calculated based on analysis of the current and previous runs of the container and other containers with similar properties (name, image, command, args). The recommendation model (MVP) assumes that the memory and CPU consumption are