diff options
| author | Daniel Smith <dbsmith@google.com> | 2015-07-09 18:02:10 -0700 |
|---|---|---|
| committer | Daniel Smith <dbsmith@google.com> | 2015-07-10 10:54:47 -0700 |
| commit | 66f367dcbb7a54e35c176b9737419e729b9eabea (patch) | |
| tree | 2865168ec5a621065f307358aa4c53826e2dba6c /resources.md | |
| parent | af4d34389316ecef46b8eeda226b62be31c309d8 (diff) | |
Auto-fixed docs
Diffstat (limited to 'resources.md')
| -rw-r--r-- | resources.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/resources.md b/resources.md index 17bb5c18..8c29a1f6 100644 --- a/resources.md +++ b/resources.md @@ -149,7 +149,7 @@ The following are planned future extensions to the resource model, included here ## Usage data -Because resource usage and related metrics change continuously, need to be tracked over time (i.e., historically), can be characterized in a variety of ways, and are fairly voluminous, we will not include usage in core API objects, such as [Pods](pods.md) and Nodes, but will provide separate APIs for accessing and managing that data. See the Appendix for possible representations of usage data, but the representation we'll use is TBD. +Because resource usage and related metrics change continuously, need to be tracked over time (i.e., historically), can be characterized in a variety of ways, and are fairly voluminous, we will not include usage in core API objects, such as [Pods](../pods.md) and Nodes, but will provide separate APIs for accessing and managing that data. See the Appendix for possible representations of usage data, but the representation we'll use is TBD. Singleton values for observed and predicted future usage will rapidly prove inadequate, so we will support the following structure for extended usage information: |
