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.
This commit is contained in:
@@ -228,7 +228,7 @@ jobs:
|
|||||||
# Wait for ESO CRDs and deployment directly instead of Flux Kustomization status
|
# 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/clustersecretstores.external-secrets.io
|
||||||
kubectl wait --for=condition=established --timeout=600s crd/externalsecrets.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
|
# 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
|
||||||
|
|||||||
Reference in New Issue
Block a user