Use absolute paths in e2e tests

This commit is contained in:
stefanprodan
2019-02-24 01:11:04 +02:00
parent e0e673f565
commit e2347c84e3
+2 -2
View File
@@ -26,7 +26,7 @@ kubectl -n istio-system wait --for=condition=complete job/istio-init-crd-10
kubectl -n istio-system wait --for=condition=complete job/istio-init-crd-11
echo 'Installing Istio control plane'
helm upgrade -i istio istio.io/istio --wait --namespace istio-system -f ./istio-values.yaml
helm upgrade -i istio istio.io/istio --wait --namespace istio-system -f ${REPO_ROOT}/e2e/istio-values.yaml
export KUBECONFIG="$(kind get kubeconfig-path)"
@@ -46,7 +46,7 @@ kubectl -n test apply -f ${REPO_ROOT}/artifacts/loadtester/
kubectl -n test rollout status deployment/flagger-loadtester
echo '>>> Initialising canary'
kubectl apply -f ./workload.yaml
kubectl apply -f ${REPO_ROOT}/e2e/workload.yaml
cat <<EOF | kubectl apply -f -
apiVersion: flagger.app/v1alpha3