diff options
| author | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-05-12 13:03:53 -0700 |
|---|---|---|
| committer | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-05-12 13:03:53 -0700 |
| commit | b2c83397b47d61cc015f89ce6883213d53ace985 (patch) | |
| tree | 206d128521cabbc9471b9511df6d06488275a457 /node-allocatable.md | |
| parent | 33e2c26d10b482b991644f5668f09c4381b088d2 (diff) | |
| parent | 102bd762fb8c97e81f269d09818e47bf738365bc (diff) | |
Merge pull request #25336 from piosz/remove-proposal
Automatic merge from submit-queue
Removed obsolete metrics API proposal
As requested in https://github.com/kubernetes/kubernetes/pull/24253#discussion_r60985010
ref #23376
Diffstat (limited to 'node-allocatable.md')
| -rw-r--r-- | node-allocatable.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/node-allocatable.md b/node-allocatable.md index fc2ffbf0..4e8e7820 100644 --- a/node-allocatable.md +++ b/node-allocatable.md @@ -41,7 +41,7 @@ Documentation for other releases can be found at Currently Node.Status has Capacity, but no concept of node Allocatable. We need additional parameters to serve several purposes: -1. [Kubernetes metrics](compute-resource-metrics-api.md) provides "/docker-daemon", "/kubelet", +1. Kubernetes metrics provides "/docker-daemon", "/kubelet", "/kube-proxy", "/system" etc. raw containers for monitoring system component resource usage patterns and detecting regressions. Eventually we want to cap system component usage to a certain limit / request. However this is not currently feasible due to a variety of reasons including: |