diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2017-09-18 23:36:13 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-18 23:36:13 -0700 |
| commit | ac30362be76df25999ade7fb2f2ab820fcd2e2bf (patch) | |
| tree | 4e22323a1cb34c441f8b4ffa645f001cdb504bb6 | |
| parent | 6e027b437314682e4a62d3e069a05242d4499ae0 (diff) | |
| parent | 60c9d482bfd36fb1903b3eb982f7e301c5f9c484 (diff) | |
Merge pull request #1086 from zouyee/resource
Automatic merge from submit-queue. .
update API group link in resource-metrics-api.md
| -rw-r--r-- | contributors/design-proposals/instrumentation/resource-metrics-api.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/instrumentation/resource-metrics-api.md b/contributors/design-proposals/instrumentation/resource-metrics-api.md index fee416e0..3e3df2be 100644 --- a/contributors/design-proposals/instrumentation/resource-metrics-api.md +++ b/contributors/design-proposals/instrumentation/resource-metrics-api.md @@ -72,7 +72,7 @@ directly using some custom API there. ## Proposed API -Initially the metrics API will be in a separate [API group](api-group.md) called ```metrics```. +Initially the metrics API will be in a separate [API group](../api-machinery/api-group.md) called ```metrics```. Later if we decided to have Node and Pod in different API groups also NodeMetrics and PodMetrics should be in different API groups. |