fix(vault-seed): re-push SOPS-sourced seeds hourly so OpenBao KV self-heals#1980
Merged
Conversation
…-heals
Every seed PushSecret was refreshInterval "0" (push once, never again).
When the 2026-06-10 incident re-initialized OpenBao with an empty KV
store, nothing re-seeded it: every consumer ExternalSecret went
SecretSyncedError ("Secret does not exist"), the infrastructure
Kustomization health-gated on three of them, and apps stayed blocked.
The seed sources (variables-base / variables-cluster, SOPS-decrypted by
Flux, and the Velero-owned velero-repo-credentials) are durable and
authoritative, so an hourly re-push is a no-op while the vault is
healthy and an automatic full re-seed after any data loss. This also
removes the manual "re-apply after token rotation" step.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 10, 2026
Contributor
Author
ℹ️ The 🧪 System Test failure here is pre-existing on main, not caused by this PR: every CI run since ~18:30 UTC today fails identically (including the unrelated Renovate PRs #1971/#1972/#1974). The test cluster's |
Contributor
|
🎉 This PR is included in version 1.47.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
All
seed-*PushSecrets userefreshInterval: "0"— push once, never again. When the 2026-06-10 incident re-initialized OpenBao with an empty KV store (see incident summary in #1979), nothing re-seeded it:SecretSyncedError("Secret does not exist")infrastructureKustomization health-gates on three of them (velero/velero-r2-credentials,openbao/vault-config-oidc,cert-manager/cloudflare-api-token) and has been timing out every 20m since ~16:30 UTCappsandinfrastructure-overprovisioningare blocked on it, and every CD run since fails at "Trigger Flux reconciliation"Fix
refreshInterval: 1hon the seven SOPS-sourced seeds (6 inpush-secrets.yaml+ the hetzner-onlyseed-hcloud). Their sources (variables-base/variables-cluster, SOPS-decrypted by Flux; the Velero-ownedvelero-repo-credentials) are durable and authoritative, so:Merging this PR is part of the live recovery: once applied, the seeds repopulate
infrastructure/{backup,dns,oidc,ghcr,hcloud}/*andapps/fleetdm/licenseand unblock the wedged ExternalSecrets. The generated secrets (dex client secret etc.) are handled in a companion PR.Validation
kubectl kustomize k8s/clusters/local/✅kubectl kustomize k8s/clusters/prod/✅🤖 Generated with Claude Code