From a10ef6f55ed70389cd3a597f49a85dd8dcbd6bdd Mon Sep 17 00:00:00 2001 From: ddeyo Date: Fri, 7 Sep 2018 11:19:59 -0700 Subject: [PATCH] updates --- ee/ucp/admin/configure/collect-cluster-metrics.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ee/ucp/admin/configure/collect-cluster-metrics.md b/ee/ucp/admin/configure/collect-cluster-metrics.md index f1c3944a0b..f1d0367e8c 100644 --- a/ee/ucp/admin/configure/collect-cluster-metrics.md +++ b/ee/ucp/admin/configure/collect-cluster-metrics.md @@ -70,7 +70,9 @@ To configure your external Prometheus server to scrape metrics from Prometheus i (cd $DOCKER_CERT_PATH && kubectl create secret generic prometheus --from-file=ca.pem --from-file=cert.pem --from-file=key.pem) ``` -3. Apply some YAML to create a Prometheus deployment and ClusterIP service. On AWS with Kube’s cloud provider configured, you could replace `ClusterIP` with `LoadBalancer` in the service YAML and then access the service through the load balancer. If you are running Prometheus external to UCP, change the following domain for inventory container in the Prometheus deployment from ucp-controller.kube-system.svc.cluster.local to a external domain for UCP accessible from the Prometheus node. +3. Create a Prometheus deployment and ClusterIP service using YAML as follows. + +On AWS with Kube’s cloud provider configured, you could replace `ClusterIP` with `LoadBalancer` in the service YAML then access the service through the load balancer. If you are running Prometheus external to UCP, change the following domain for inventory container in the Prometheus deployment from `ucp-controller.kube-system.svc.cluster.local` to a external domain to access UCP from the Prometheus node. ``` kubectl apply -f - <