Docs fixes

fluxcd · Mar 25, 2019 · 3c4253c · 3c4253c
1 parent 77ba28e
commit 3c4253c
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 6 deletions.
diff --git a/docs/gitbook/install/flagger-install-on-eks-appmesh.md b/docs/gitbook/install/flagger-install-on-eks-appmesh.md
@@ -23,11 +23,11 @@ Prerequisites:
 
 ### Create a Kubernetes cluster
 
-In order to create an EKS cluster you can use [eksctl](https://eksctl.io).
-Eksctl is an open source command-line utility made by Weaveworks in collaboration with Amazon, 
+In order to create an EKS cluster you can use [EKSctl](https://eksctl.io).
+EKSctl is an open source command-line utility made by Weaveworks in collaboration with Amazon, 
 it's written in Go and is based on EKS CloudFormation templates.
 
-On MacOS you can install eksctl with Homebrew:
+On MacOS you can install EKSctl with Homebrew:
 
 ```bash
 brew tap weaveworks/tap
@@ -126,8 +126,8 @@ Status:
 
 ### Install Prometheus
 
-In order to expose the App Mesh metrics to Flagger, 
-you'll need to use Prometheus to scrapes the Envoy sidecars.
+In order to collect the App Mesh metrics that Flagger needs to run the canary analysis, 
+you'll need to setup a Prometheus instance to scrape the Envoy sidecars.
 
 Deploy Prometheus in the `appmesh-system` namespace:
 

diff --git a/docs/gitbook/usage/appmesh-progressive-delivery.md b/docs/gitbook/usage/appmesh-progressive-delivery.md
@@ -9,7 +9,7 @@ You'll need an EKS cluster configured with App Mesh, you can find the install gu
 Flagger takes a Kubernetes deployment and optionally a horizontal pod autoscaler (HPA), 
 then creates a series of objects (Kubernetes deployments, ClusterIP services, App Mesh virtual nodes and services). 
 These objects expose the application on the mesh and drive the canary analysis and promotion.
-The only App Mesh object you need to creat by yourself is the mesh resource.
+The only App Mesh object you need to create by yourself is the mesh resource.
 
 Create a mesh called `global` in the `appmesh-system` namespace:
 
@@ -162,6 +162,12 @@ kubectl -n test describe svc/ingress | grep Ingress
 LoadBalancer Ingress:     yyy-xx.us-west-2.elb.amazonaws.com
 ```
 
+Wait for the ELB to become active:
+
+```bash
+ watch curl -sS ${INGRESS_URL}
+```
+
 Open your browser and navigate to the ingress address to access podinfo UI.
 
 ### Automated canary promotion