refactor(stage): restructure to 4-service pattern #2
No reviewers
Labels
No labels
bug
contribution welcome
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
feeldata/manifests!2
Loading…
Reference in a new issue
No description provided.
Delete branch "refs/pull/2/head"
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
Replace the monolithic single-service "website" stage layout with the 4-service pattern (api, graphql, web, db-migrate) matching dev and prod.
Changes
feeldata/monolithic directory (deployment, hpa, service, ingress, limits, monitors)migrate-postgresqlpipeline and RBACaws-credsfor CNPG S3 backupspostgresql.yamlto stage rootapi/,graphql/,web/,db-migrate/configmap.yamlwith*.stage.feeldata.appdomainsINITIAL— will be set by promote-to-stage pipelinePrerequisites before ArgoCD sync
feeldata-stagenamespacestage.feeldata.appandapi.stage.feeldata.appKnown limitation
NEXT_PUBLIC_API_URLis baked at build time in the web image. Promoted dev images will still point toapi.dev.feeldata.appfor client-side calls. Follow-up issue filed.