From 51dc54bcb9627dbd91dd4b74d34c5119ffc54389 Mon Sep 17 00:00:00 2001 From: Yoni Bettan Date: Wed, 12 Jan 2022 11:45:09 +0200 Subject: [PATCH] ci: removing the timeout from the rollout command It makes the flow fail for some reason. Signed-off-by: Yoni Bettan --- .github/workflows/e2e-k3s.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/e2e-k3s.yaml b/.github/workflows/e2e-k3s.yaml index f765f2988d..b54b08e8d1 100644 --- a/.github/workflows/e2e-k3s.yaml +++ b/.github/workflows/e2e-k3s.yaml @@ -50,7 +50,7 @@ jobs: run: | kubectl create ns sample-application kubectl -n sample-application apply -Rf sample-apps/hotrod/ - kubectl -n sample-application get deploy --output name | xargs -r -n1 -t kubectl -n sample-application rollout status --timeout=300s + kubectl -n sample-application get deploy --output name | xargs -r -n1 -t kubectl -n sample-application rollout status kubectl -n sample-application run strzal --image=djbingham/curl \ --restart='OnFailure' -i --rm --command -- curl -X POST -F \ 'locust_count=6' -F 'hatch_rate=2' http://locust-master:8089/swarm