diff options
| author | Piotr Szczesniak <pszczesniak@google.com> | 2016-05-09 10:50:00 +0200 |
|---|---|---|
| committer | Piotr Szczesniak <pszczesniak@google.com> | 2016-05-11 21:36:15 +0200 |
| commit | 102bd762fb8c97e81f269d09818e47bf738365bc (patch) | |
| tree | ab7f73983bd703d28de653aac1ba334dfe94e187 /node-allocatable.md | |
| parent | c2bdbed46e0babee4c19690486ba099af5ae6a6a (diff) | |
Removed obsolete metrics API proposal
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: |