Repository navigation
setup-secrets: Cluster sources and destinations through shared's helpers - #31
Merged
Merged
Conversation
The destinations that write Kubernetes Secrets are now in the setup-secrets group cluster, which runs after every start of k3s, and retry while k3s and the workloads come up. Sources that read a Secret, or generate a value when it is missing, use kubeSecretSource; the API keys read from the workloads use kubeExecSource, which waits for the rollout first. A generated value is made only when the Secret or its field is missing, never because the API didn't answer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
andsens
force-pushed
the
setup-secrets-groups
branch
from
November 19, 2026 21:57
7e205c8 to
00d5e8e
Compare
andsens
enabled auto-merge (squash)
November 19, 2026 21:57
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
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.
Needs nixos-homelab/shared#37 and andsens/nixos-setup-secrets#14. shared and setup-secrets are locked to those branches (and homelab-monitoring to current main, which current shared needs); relock to main before merging.
The destinations that write Kubernetes Secrets move to
kubeSecretDestination/clusterDestination, so they're in the setup-secrets groupcluster, which runs after k3s and retries while it and the workloads come up. Sources that read a Secret usekubeSecretSource(withgeneratewhere a value was generated before; now only when the Secret or field is missing, never when the API fails). API keys read from a workload usekubeExecSource, which waits for the rollout. The credstore-backed ones stay in thehostgroup.sabnzbd keeps running the host gnugrep inside the container, as before;
cutruns on the host.Checked:
nix flake checkpasses locally (VM tests included where the repo has them).🤖 Generated with Claude Code