From b5c948f42c2736c262f83e0627a60b787b702de9 Mon Sep 17 00:00:00 2001 From: ddeyo Date: Fri, 7 Sep 2018 11:22:22 -0700 Subject: [PATCH] updates --- ee/ucp/admin/configure/collect-cluster-metrics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ee/ucp/admin/configure/collect-cluster-metrics.md b/ee/ucp/admin/configure/collect-cluster-metrics.md index 769fbb1be5..581d6b00b5 100644 --- a/ee/ucp/admin/configure/collect-cluster-metrics.md +++ b/ee/ucp/admin/configure/collect-cluster-metrics.md @@ -72,7 +72,7 @@ To configure your external Prometheus server to scrape metrics from Prometheus i 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 an external domain to access UCP from the Prometheus node. + On AWS with Kube’s cloud provider configured, you can replace `ClusterIP` with `LoadBalancer` in the service YAML then access the service through the load balancer. If running Prometheus external to UCP, change the following domain for the inventory container in the Prometheus deployment from `ucp-controller.kube-system.svc.cluster.local` to an external domain to access UCP from the Prometheus node. ``` kubectl apply -f - <