From 15872884fbba61ddafcffa0da25939571a204aa7 Mon Sep 17 00:00:00 2001 From: Kai Chen Date: Wed, 21 Mar 2018 23:57:32 +0800 Subject: Add hyperlink to the referenced issue --- .../design-proposals/instrumentation/monitoring_architecture.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- cgit v1.2.3