From da16e2a82a8e8a0593cf90cfa54aa27e6b8ba9ad Mon Sep 17 00:00:00 2001
From: wangxy518 <40482095+wangxy518@users.noreply.github.com>
Date: Mon, 20 Aug 2018 16:44:01 +0800
Subject: [PATCH] Update node-allocatable.md

---
 contributors/design-proposals/node/node-allocatable.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/contributors/design-proposals/node/node-allocatable.md b/contributors/design-proposals/node/node-allocatable.md
index 4fe22c374..07f52b74b 100644
--- a/contributors/design-proposals/node/node-allocatable.md
+++ b/contributors/design-proposals/node/node-allocatable.md
@@ -249,7 +249,7 @@ Users are expected to specify `KubeReserved` and `SystemReserved` based on their
 
 Resource requirements for Kubelet and the runtime is typically proportional to the number of pods running on a node.
 Once a user identified the maximum pod density for each of their nodes, they will be able to compute `KubeReserved` using [this performance dashboard](http://node-perf-dash.k8s.io/#/builds).
-[This blog post](http://blog.kubernetes.io/2016/11/visualize-kubelet-performance-with-node-dashboard.html) explains how the dashboard has to be interpreted.
+[This blog post](https://kubernetes.io/blog/2016/11/visualize-kubelet-performance-with-node-dashboard/) explains how the dashboard has to be interpreted.
 Note that this dashboard provides usage metrics for docker runtime only as of now.
 
 Support for evictions based on Allocatable will be introduced in this phase.