summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKai Chen <kaichen@outlook.com>2018-03-21 23:57:32 +0800
committerKai Chen <kaichen@outlook.com>2018-03-21 23:57:32 +0800
commit15872884fbba61ddafcffa0da25939571a204aa7 (patch)
treeadaede6099aa52c86522d3acf2970fc1f67407ac
parente926accd78d2822b49589e511cd31a52b57c30b8 (diff)
Add hyperlink to the referenced issue
-rw-r--r--contributors/design-proposals/instrumentation/monitoring_architecture.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/instrumentation/monitoring_architecture.md b/contributors/design-proposals/instrumentation/monitoring_architecture.md
index 1b4cd206..59e4ccbc 100644
--- a/contributors/design-proposals/instrumentation/monitoring_architecture.md
+++ b/contributors/design-proposals/instrumentation/monitoring_architecture.md
@@ -66,7 +66,7 @@ The monitoring architecture should
master API (today the master metrics API), such that core Kubernetes features do not
depend on non-core components
* requires Kubelet to only export a limited set of metrics, namely those required for
- core Kubernetes components to correctly operate (this is related to #18770)
+ core Kubernetes components to correctly operate (this is related to [#18770](https://github.com/kubernetes/kubernetes/issues/18770))
* can scale up to at least 5000 nodes
* is small enough that we can require that all of its components be running in all deployment
configurations