From 12675417bd2e9d22fcc02da89c13bd73045a79bf Mon Sep 17 00:00:00 2001 From: MichaelFisher1997 Date: Thu, 23 Apr 2026 19:00:15 +0000 Subject: [PATCH] fix: use correct namespace and deployment name for ESO rollout check The ESO deployment is named external-secrets-external-secrets in the external-secrets namespace, not external-secrets in kube-system. --- .gitea/workflows/deploy.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 892b730..5f8e620 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -228,7 +228,7 @@ jobs: # Wait for ESO CRDs and deployment directly instead of Flux Kustomization status kubectl wait --for=condition=established --timeout=600s crd/clustersecretstores.external-secrets.io kubectl wait --for=condition=established --timeout=600s crd/externalsecrets.external-secrets.io - kubectl -n kube-system rollout status deployment/external-secrets --timeout=600s + kubectl -n external-secrets rollout status deployment/external-secrets-external-secrets --timeout=600s # Create Doppler ClusterSecretStore now that ESO CRDs are available kubectl apply -f - <<'EOF' apiVersion: external-secrets.io/v1