fix: wait on ESO deployment directly instead of Flux Kustomization status
Deploy Cluster / Terraform (push) Successful in 29s
Deploy Cluster / Ansible (push) Failing after 19m8s

The addon-external-secrets Flux Kustomization was timing out during bootstrap
because image pulls on fresh Proxmox VMs are slow. The critical dependency is
the ESO deployment being available for the Doppler ClusterSecretStore. Replace
the Kustomization readiness check with direct checks for ESO CRD establishment
and deployment rollout, which are the actual prerequisites for the next step.
This commit is contained in:
2026-04-23 07:32:19 +00:00
parent 4b7517c9c5
commit 8e081ddfda
+4 -1
View File
@@ -225,7 +225,10 @@ jobs:
kubectl -n flux-system rollout status deployment/helm-controller --timeout=600s kubectl -n flux-system rollout status deployment/helm-controller --timeout=600s
kubectl -n flux-system wait --for=condition=Ready gitrepository/platform --timeout=300s kubectl -n flux-system wait --for=condition=Ready gitrepository/platform --timeout=300s
kubectl -n flux-system wait --for=condition=Ready kustomization/infrastructure --timeout=600s kubectl -n flux-system wait --for=condition=Ready kustomization/infrastructure --timeout=600s
kubectl -n flux-system wait --for=condition=Ready kustomization/addon-external-secrets --timeout=600s # 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
# Create Doppler ClusterSecretStore now that ESO CRDs are available # Create Doppler ClusterSecretStore now that ESO CRDs are available
kubectl apply -f - <<'EOF' kubectl apply -f - <<'EOF'
apiVersion: external-secrets.io/v1 apiVersion: external-secrets.io/v1