Skip to content

gitea Runbook

Metadata

Field Value
Service gitea
Criticality Tier 2
Owner Platform / SCM owner
Namespace gitea
Clusters dev, local
Last validated 2026-05-20
Related service page ../services/gitea.md

Trigger Conditions

  • Gitea UI is unavailable.
  • Git operations fail.
  • PostgreSQL or PVC state is unhealthy.
  • The external route fails after ingress changes.

1. Health Checks

kubectl -n gitea get pods,svc,pvc,ingressroute
kubectl -n gitea logs deploy/gitea --tail=200
kubectl -n gitea get statefulset

2. Troubleshooting Workflows

kubectl -n gitea describe deploy gitea
kubectl -n gitea logs statefulset/gitea-db --tail=100
kubectl -n gitea describe ingressroute

Check DB credentials, PVC state, and middleware references.

3. Disaster Recovery

  1. Restore DB backup or PVC snapshot.
  2. Restore Gitea secrets.
  3. Reconcile the target overlay.
  4. Validate web and Git traffic.

4. Scaling and Resource Management

kubectl -n gitea top pod
kubectl -n gitea describe deploy gitea

Tune app or DB resources in Git if traffic or migrations saturate the current limits.

5. Maintenance Procedures

  • Rotate admin and DB secrets.
  • Revalidate ingress after Traefik or Authelia changes.
  • Review PVC locality before node maintenance.

6. Rollback Strategy

  • Revert the active overlay to the last known-good revision.
  • Restore the DB snapshot if schema or credentials caused the outage.

7. Post-Incident Actions

  1. Record manual changes in a changelog fragment.
  2. Update the service page if cluster mappings or routes changed.
  3. Extend this runbook with the incident-specific signature.