From 2153762922fe3a0227b789240f53a00d7b04bcd7 Mon Sep 17 00:00:00 2001
From: sHa <sha@shadoll.dev>
Date: Mon, 13 Jul 2026 20:12:58 +0300
Subject: [PATCH] chore: Add initial Helm chart and values configuration for
 Gitea

---
 gitea/Chart.yaml  | 19 +++++++++++++++++++
 gitea/values.yaml |  9 +++++++++
 2 files changed, 28 insertions(+)
 create mode 100644 gitea/Chart.yaml
 create mode 100644 gitea/values.yaml

diff --git a/gitea/Chart.yaml b/gitea/Chart.yaml
new file mode 100644
index 0000000..4d27f16
--- /dev/null
+++ b/gitea/Chart.yaml
@@ -0,0 +1,19 @@
+apiVersion: v2
+name: gitea
+description: >-
+  Gitea git server — thin wrapper around the official gitea-charts/gitea
+  chart. The dependency version below is an exact, manually-reviewed pin:
+  it must only be bumped together with a compatibility check against the
+  appVersion (Gitea image tag), since gitea-charts' init scripts can require
+  a minimum Gitea version (e.g. chart 12.x requires Gitea >=1.26 for its
+  `gitea config edit-ini` init step).
+type: application
+version: 0.1.0
+appVersion: "1.26.1"
+annotations:
+  version-source: github-release:go-gitea/gitea
+  version-pattern: "s|^v||"
+dependencies:
+  - name: gitea
+    version: "12.6.0"
+    repository: "https://dl.gitea.com/charts/"
diff --git a/gitea/values.yaml b/gitea/values.yaml
new file mode 100644
index 0000000..53b2857
--- /dev/null
+++ b/gitea/values.yaml
@@ -0,0 +1,9 @@
+# Values here are passed through to the vendored gitea-charts/gitea subchart
+# (Chart.yaml dependency named "gitea"), so anything set from a consuming
+# HelmRelease must nest one level under `gitea:` — e.g. `gitea.image.tag`,
+# `gitea.gitea.config...`. Environment-specific values (secrets, hosts,
+# resources, DB config) are supplied by each cluster's HelmRelease; this
+# file only pins the auto-tracked image tag default.
+gitea:
+  image:
+    tag: "1.26.1"