diff options
| author | wangxy518 <40482095+wangxy518@users.noreply.github.com> | 2018-08-20 16:44:01 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-08-20 16:44:01 +0800 |
| commit | da16e2a82a8e8a0593cf90cfa54aa27e6b8ba9ad (patch) | |
| tree | bd9a6204a874b2f654ac519506689a52c76b8867 | |
| parent | 72e931e1142ce47634f974cd12dae2ebf34b4472 (diff) | |
Update node-allocatable.md
| -rw-r--r-- | contributors/design-proposals/node/node-allocatable.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/node/node-allocatable.md b/contributors/design-proposals/node/node-allocatable.md index 4fe22c37..07f52b74 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. |