From 1bb11dfe3a7ac7f8a901c05a9d66bd6ca45b5ff7 Mon Sep 17 00:00:00 2001 From: MichaelFisher1997 Date: Wed, 22 Apr 2026 10:08:20 +0000 Subject: [PATCH] fix: force nfs storage reconcile during flux bootstrap The NFS HelmRelease can remain in a failed state from an earlier bootstrap attempt even after the backing NFS export is corrected and the pod becomes healthy. Request a fresh reconcile of the HelmRelease and addon kustomization before waiting on addon-nfs-storage so the bootstrap step can observe the recovered state. --- .gitea/workflows/deploy.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 1039c46..cdf693f 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -243,6 +243,10 @@ jobs: namespace: external-secrets EOF # Wait for the storage layer and private access components + TS=$(date --iso-8601=seconds) + kubectl -n flux-system annotate helmrelease/nfs-subdir-external-provisioner reconcile.fluxcd.io/requestedAt="$TS" --overwrite || true + kubectl -n flux-system annotate kustomization/addon-nfs-storage reconcile.fluxcd.io/requestedAt="$TS" --overwrite || true + kubectl -n flux-system wait --for=condition=Ready helmrelease/nfs-subdir-external-provisioner --timeout=600s kubectl -n flux-system wait --for=condition=Ready kustomization/addon-nfs-storage --timeout=600s kubectl -n flux-system wait --for=condition=Ready kustomization/addon-tailscale-operator --timeout=300s