Deploy Backstage to dev and prod through Nixidy #88
Labels
No labels
automation
automerge
ci
infra
migrated/beads
priority/P2
refactoring
repo-maintenance
status/in-progress
testing
type/epic
type/task
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
Personal/cluster#88
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Deploy Backstage to the cluster's dev and prod environments through the existing Nixidy/ArgoCD GitOps workflow, including environment configuration, ingress, persistence, and backend-only secrets.
Context
This is the cluster-side delivery work for Personal/backstage#30, the overall secure hosting gate. The application-side Keycloak integration is tracked in Personal/backstage#32; do not duplicate that code here.
The intended public URLs are:
This repository defines applications in
env/devandenv/prod, generates manifests with Nixidy, and uses encrypted SOPSSopsSecretresources for secrets. Generated manifests are committed but must not contain plaintext credentials.Scope
NODE_ENV=production.Acceptance criteria
BACKSTAGE_BASE_URL,AUTH_KEYCLOAK_CLIENT_ID,AUTH_KEYCLOAK_BASE_URL,AUTH_KEYCLOAK_REALM, andNODE_ENV=productionvalues.AUTH_KEYCLOAK_CLIENT_SECRETis stored in an encrypted SOPSSopsSecret, materializes as a Kubernetes Secret in the application's namespace, and is referenced only by the backend workload. No plaintext secret appears in Git or generated manifests.Related