From f1eb1c73666ea2db5e2ab06284016f4a0e62c120 Mon Sep 17 00:00:00 2001 From: Barun Acharya Date: Thu, 18 Apr 2024 16:40:04 +0530 Subject: [PATCH] fix(ci): check for controller readiness after restart Signed-off-by: Barun Acharya --- .github/workflows/ci-latest-release.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci-latest-release.yml b/.github/workflows/ci-latest-release.yml index fb851cddb0..d6c64af00d 100644 --- a/.github/workflows/ci-latest-release.yml +++ b/.github/workflows/ci-latest-release.yml @@ -102,7 +102,8 @@ jobs: fi kubectl apply -f pkg/KubeArmorOperator/config/samples/kubearmor-test.yaml kubectl wait -n kubearmor --timeout=5m --for=jsonpath='{.status.phase}'=Running kubearmorconfigs/kubearmorconfig-test - kubectl wait --timeout=5m --for=condition=ready pod -l kubearmor-app,kubearmor-app!=kubearmor-snitch -n kubearmor + kubectl wait --timeout=7m --for=condition=ready pod -l kubearmor-app,kubearmor-app!=kubearmor-snitch,kubearmor-app!=kubearmor-controller -n kubearmor + kubectl wait --timeout=1m --for=condition=ready pod -l kubearmor-app=kubearmor-controller -n kubearmor kubectl get pods -A - name: Test KubeArmor using Ginkgo