e2e: use kustomize to install the load tester

artifacts/flagger/account.yaml

@@ -2,7 +2,7 @@ apiVersion: v1
 kind: ServiceAccount
 metadata:
   name: flagger
-  namespace: istio-system
+  namespace: default
   labels:
     app: flagger
 ---
@@ -109,4 +109,4 @@ roleRef:
 subjects:
 - kind: ServiceAccount
   name: flagger
-  namespace: istio-system
+  namespace: default

artifacts/flagger/deployment.yaml

@@ -2,7 +2,7 @@ apiVersion: apps/v1
 kind: Deployment
 metadata:
   name: flagger
-  namespace: istio-system
+  namespace: default
   labels:
     app: flagger
 spec:
@@ -30,9 +30,6 @@ spec:
         command:
         - ./flagger
         - -log-level=info
-        - -control-loop-interval=10s
-        - -mesh-provider=$(MESH_PROVIDER)
-        - -metrics-server=http://prometheus.istio-system.svc.cluster.local:9090
         livenessProbe:
           exec:
             command:

docs/gitbook/usage/webhooks.md

@@ -116,10 +116,7 @@ that generates traffic during analysis when configured as a webhook.
 First you need to deploy the load test runner in a namespace with sidecar injection enabled:
 
 ```bash
-export REPO=https://raw.githubusercontent.com/weaveworks/flagger/master
-
-kubectl -n test apply -f ${REPO}/artifacts/loadtester/deployment.yaml
-kubectl -n test apply -f ${REPO}/artifacts/loadtester/service.yaml
+kubectl apply -k github.com/weaveworks/flagger//kustomize/tester
 ```
 
 Or by using Helm:

test/e2e-contour-tests.sh

@@ -11,7 +11,7 @@ echo '>>> Creating test namespace'
 kubectl create namespace test
 
 echo '>>> Installing load tester'
-kubectl -n test apply -f ${REPO_ROOT}/artifacts/loadtester/
+kubectl apply -k ${REPO_ROOT}/kustomize/tester
 kubectl -n test rollout status deployment/flagger-loadtester
 
 echo '>>> Initialising canary'

test/e2e-gloo-tests.sh

@@ -11,7 +11,7 @@ echo '>>> Creating test namespace'
 kubectl create namespace test
 
 echo '>>> Installing load tester'
-kubectl -n test apply -f ${REPO_ROOT}/artifacts/loadtester/
+kubectl apply -k ${REPO_ROOT}/kustomize/tester
 kubectl -n test rollout status deployment/flagger-loadtester
 
 echo '>>> Initialising canary'

test/e2e-linkerd-tests.sh

@@ -11,7 +11,7 @@ kubectl create namespace test
 kubectl annotate namespace test linkerd.io/inject=enabled
 
 echo '>>> Installing the load tester'
-kubectl -n test apply -f ${REPO_ROOT}/artifacts/loadtester/
+kubectl apply -k ${REPO_ROOT}/kustomize/tester
 kubectl -n test rollout status deployment/flagger-loadtester
 
 echo '>>> Initialising canary'

test/e2e-nginx-tests.sh

@@ -11,7 +11,7 @@ echo '>>> Creating test namespace'
 kubectl create namespace test
 
 echo '>>> Installing load tester'
-kubectl -n test apply -f ${REPO_ROOT}/artifacts/loadtester/
+kubectl apply -k ${REPO_ROOT}/kustomize/tester
 kubectl -n test rollout status deployment/flagger-loadtester
 
 echo '>>> Initialising canary'