Date: 2026-02-06
This document lists supported topology options for running Gitea on the Kubernetes host drg-k8s.auth.home.lan, plus optional runners and GitOps.
- Git service: Gitea in Kubernetes behind
ingress-nginx.
- Database: Postgres in Kubernetes (PVC) or external Postgres (preferred if available).
- Storage: PVC for Gitea
data.
- GitOps: Argo CD (UI) to manage cluster apps from Gitea.
- CI: Gitea Actions runners (UI in Gitea shows job status), runners can run:
- on
kryptovisor (docker-based) for simplest start, or
- in Kubernetes (for consolidation).
- Registry: optional self-hosted registry with UI (Harbor) if you want “all local”.
- Pros:
- Excellent UI for sync status, diffs, health, and history.
- Easy manual sync/rollback workflows.
- Cons:
- Adds an in-cluster control plane component.
- Pros:
- Minimal and very “git-native”.
- Cons:
- UI is not first-class without extra tools.
Decision: For UI-driven operations, pick Argo CD.
- Pros:
- Clean separation of concerns.
- Backups and upgrades can be handled independently.
- Cons:
- Requires another host/service.
- Pros:
- Cons:
- Single-node cluster means DB availability is tied to the node.
- Requires careful backups.
Notes:
- SQLite is acceptable for small instances, but it complicates scaling and concurrent workloads.
- For a “production-ready” posture, use Postgres.
- Pros: simplest.
- Cons: node-local; if the node fails, restore requires backup.
- Pros: enables easier data migration/restore.
- Cons: requires NFS server and tuning.
- Pros: simplest.
- Cons: some users prefer SSH.
- Requires:
- a stable TCP endpoint for SSH (typically
:22), not an Ingress HTTP route.
- either
hostNetwork/hostPort, or a LoadBalancer implementation, or a NodePort mapped from router/firewall.
- Pros: no cluster changes required to start CI.
- Cons: still depends on that host.
- Pros: consolidated operations.
- Cons: more cluster config (RBAC, storage, security).
- Use local build + manual image load or a simple image distribution pattern.
- Not recommended long-term.
- Pros: small footprint.
- Cons: no UI, limited features.
- Pros: UI, access control, retention policies, scanning integrations.
- Cons: larger footprint.