From 5ed5d1e5b66fda4ebd6f4d0ddee975613f84008b Mon Sep 17 00:00:00 2001 From: stefanprodan Date: Tue, 26 Mar 2019 11:57:01 +0200 Subject: [PATCH] Fix load tester install command for zsh --- docs/gitbook/install/flagger-install-on-eks-appmesh.md | 8 ++++---- docs/gitbook/usage/appmesh-progressive-delivery.md | 2 +- docs/gitbook/usage/progressive-delivery.md | 6 ++++++ 3 files changed, 11 insertions(+), 5 deletions(-) diff --git a/docs/gitbook/install/flagger-install-on-eks-appmesh.md b/docs/gitbook/install/flagger-install-on-eks-appmesh.md index 91955db2..d243cdfb 100644 --- a/docs/gitbook/install/flagger-install-on-eks-appmesh.md +++ b/docs/gitbook/install/flagger-install-on-eks-appmesh.md @@ -24,11 +24,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, -it's written in Go and is based on EKS CloudFormation templates. +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 a Kubernetes-native tool written in Go. -On MacOS you can install EKSctl with Homebrew: +On MacOS you can install eksctl with Homebrew: ```bash brew tap weaveworks/tap diff --git a/docs/gitbook/usage/appmesh-progressive-delivery.md b/docs/gitbook/usage/appmesh-progressive-delivery.md index 4d849f66..c5a61f47 100644 --- a/docs/gitbook/usage/appmesh-progressive-delivery.md +++ b/docs/gitbook/usage/appmesh-progressive-delivery.md @@ -38,7 +38,7 @@ Deploy the load testing service to generate traffic during the canary analysis: helm upgrade -i flagger-loadtester flagger/loadtester \ --namespace=test \ --set meshName=global.appmesh-system \ ---set backends[0]=podinfo.test +--set "backends[0]=podinfo.test" ``` Create a canary custom resource: diff --git a/docs/gitbook/usage/progressive-delivery.md b/docs/gitbook/usage/progressive-delivery.md index f0660e63..2e9063a6 100644 --- a/docs/gitbook/usage/progressive-delivery.md +++ b/docs/gitbook/usage/progressive-delivery.md @@ -2,6 +2,8 @@ This guide shows you how to use Istio and Flagger to automate canary deployments. +### Bootstrap + Create a test namespace with Istio sidecar injection enabled: ```bash @@ -109,6 +111,8 @@ service/podinfo-primary virtualservice.networking.istio.io/podinfo ``` +### Automated canary promotion + Trigger a canary deployment by updating the container image: ```bash @@ -159,6 +163,8 @@ prod frontend Succeeded 0 2019-01-15T16:15:07Z prod backend Failed 0 2019-01-14T17:05:07Z ``` +### Automated rollback + During the canary analysis you can generate HTTP 500 errors and high latency to test if Flagger pauses the rollout. Create a tester pod and exec into it: