summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorWilliam Zhang <warmchang@outlook.com>2018-06-13 23:32:49 +0800
committerWilliam Zhang <warmchang@outlook.com>2018-06-13 23:32:49 +0800
commitb9c3580c1e3e0e95fd46aad6375a2406dd2c2a0b (patch)
treee40ee9692723abe7ef644f9fc885d4129a3bbb2d
parentd251c97aff20fe94fea9761a2ce9b922e6b68239 (diff)
Fix typo
Signed-off-by: William Zhang <warmchang@outlook.com>
-rw-r--r--contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md b/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md
index d990d7db..c4482a45 100644
--- a/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md
+++ b/contributors/design-proposals/autoscaling/vertical-pod-autoscaler.md
@@ -81,8 +81,7 @@ on historical utilization. It is designed to only kick in on Pod creation.
VPA is intended to supersede this feature.
#### In-place updates ####
-In-place Pod updates ([#5774]
-(https://github.com/kubernetes/kubernetes/issues/5774)) is a planned feature to
+In-place Pod updates ([#5774](https://github.com/kubernetes/kubernetes/issues/5774)) is a planned feature to
allow changing resources (request/limit) of existing containers without killing them, assuming sufficient free resources available on the node.
Vertical Pod Autoscaler will greatly benefit from this ability, however it is
not considered a blocker for the MVP.