coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

Migrate forgejo's in-pod Postgres onto CloudNativePG (later) #328

New issue
Closed
opened 2026-06-15 00:18:07 +00:00 by coilysiren · 1 comment
coilysiren commented 2026-06-15 00:18:07 +00:00
Owner
Copy link

Optional, lower-priority follow-up: migrate forgejo's in-pod postgres:17 (deploy/forgejo.yml:99) onto the shared CloudNativePG-managed cluster, so all app Postgres lives under one operator with consistent backups/upgrades.

Why later, not now

Forgejo is the source-of-truth git server - its Postgres works and is isolated today. No urgency. Worth doing only once CloudNativePG is proven in-cluster (see the parent task) so the migration is low-risk.

Scope (when picked up)

  • Provision a forgejo database/role on the shared CloudNativePG cluster
  • Plan + test a dump/restore (or logical replication) cutover with forgejo quiesced
  • Update deploy/forgejo.yml to point at the managed cluster and drop the in-pod postgres container
  • Verify backups + restore path

Refs

  • Depends on: CloudNativePG operator landing first (parent backlog #326)
Optional, lower-priority follow-up: migrate forgejo's in-pod `postgres:17` (`deploy/forgejo.yml:99`) onto the shared CloudNativePG-managed cluster, so all app Postgres lives under one operator with consistent backups/upgrades. ## Why later, not now Forgejo is the source-of-truth git server - its Postgres works and is isolated today. No urgency. Worth doing only once CloudNativePG is proven in-cluster (see the parent task) so the migration is low-risk. ## Scope (when picked up) - [ ] Provision a `forgejo` database/role on the shared CloudNativePG cluster - [ ] Plan + test a dump/restore (or logical replication) cutover with forgejo quiesced - [ ] Update `deploy/forgejo.yml` to point at the managed cluster and drop the in-pod postgres container - [ ] Verify backups + restore path ## Refs - Depends on: CloudNativePG operator landing first (parent backlog https://forgejo.coilysiren.me/coilyco-flight-deck/infrastructure/issues/326)
coilysiren commented 2026-06-17 08:22:31 +00:00
Author
Owner
Copy link

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: burndown-2026-06.

Backlog burndown 2026-06-17: closing low-priority (P3/P4) to bring the open count to a manageable level. Nothing lost — reopen if this resurfaces. Batch tag: `burndown-2026-06`.
coilysiren 2026-06-17 08:22:31 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/infrastructure#328
No description provided.