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.
2026-04-23 19:00:15 +00:00
parent 8e081ddfda
commit 12675417bd
1 changed files with 1 additions and 1 deletions
@@ -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