Skip to content

chore(k8s): commit dev SealedSecrets for FluxCD GitOps - #80

Merged
jcschaff merged 1 commit into
mainfrom
chore/flux-dev-sealed-secrets
Jul 29, 2026
Merged

chore(k8s): commit dev SealedSecrets for FluxCD GitOps#80
jcschaff merged 1 commit into
mainfrom
chore/flux-dev-sealed-secrets

Conversation

@jcschaff

Copy link
Copy Markdown
Member

Commits the vcell-ai-rke-dev SealedSecrets (encrypted; bitnami.com/v1alpha1) so FluxCD can build the overlay from git. Only the vxrails controller can decrypt them — safe in a public repo. Raw secrets.dat stays gitignored; no plaintext Secret is committed. Part of wiring VCell-AI into vcell-fluxcd GitOps.

🤖 Generated with Claude Code

FluxCD builds the overlay from git, so the vcell-ai-rke-dev SealedSecrets must be
in the repo. Un-ignore and commit secret-{backend,frontend,ghcr,litellm}.yaml for
that overlay only. They are encrypted SealedSecrets (bitnami.com/v1alpha1) — the
RSA-encrypted blobs can only be decrypted by the vxrails controller, so they are
safe in a public repo (the purpose of Sealed Secrets). Raw secrets.dat stays
gitignored; no plaintext Secret is ever committed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XpNzobVi83p3YKL9sqtGwZ
@jcschaff
jcschaff merged commit 91d3b65 into main Jul 29, 2026
@jcschaff
jcschaff deleted the chore/flux-dev-sealed-secrets branch July 29, 2026 03:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant