Gitea gives a team its own service for hosting Git repositories and collaborating on code. Developers push and pull through familiar Git tools while using a web interface for the surrounding review and project work. It is useful when repository hosting should run on infrastructure the team controls. The service stores more than Git files, so its database, attachments and any additional package data must be included in backup planning.
Chart ownership
Gitea's Kubernetes documentation identifies the project chart and the dl.gitea.com/charts/ repository. Follow the chart's own configuration and upgrade instructions for the selected release. A chart using the same application image from another publisher is a different distribution.
Before adoption
Plan HTTPS and SSH access, user registration, authentication and administrator recovery. Repository files, database records, attachments and any package data need a coordinated backup and restore procedure. Check database dependencies and persistent-volume behavior before chart upgrades. If adding build runners, separately review where untrusted repository code executes and which secrets it can access; hosting source repositories does not establish a safe CI execution boundary.
Sources & further reading
Spotted something that needs another look?
Help improve this page →