homelab/values/gitea.yaml
Nik Afiq fd13b8aedb
Some checks failed
validate / lint (push) Has been cancelled
feat: move Gitea traffic from gitea.nik4nao.com to gitea.home.arpa
The public domain is unreachable while moving, and the cluster had no
Traefik route to Gitea at all (public or internal), leaving every Argo
CD Application stuck in Unknown sync. Add a gitea.home.arpa
Certificate/IngressRoute, repoint Argo CD's repoURL, Gitea's own
DOMAIN/ROOT_URL/SSH_DOMAIN, the container registry references, the
Gitea Actions runner, and the watch-party clone URL at the internal
hostname.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-08-07 23:06:02 +09:00

70 lines
1.9 KiB
YAML

# Apply: helm upgrade --install gitea gitea-charts/gitea -f values/gitea.yaml -n gitea --create-namespace
# Description: Helm values for Gitea git server and Docker registry
replicaCount: 1
image:
tag: "1.23"
gitea:
admin:
existingSecret: gitea-admin-secret
email: nik@nik4nao.com
config:
server:
DOMAIN: gitea.home.arpa
ROOT_URL: https://gitea.home.arpa
SSH_DOMAIN: gitea.home.arpa
SSH_PORT: 2222
repository:
DEFAULT_PRIVATE: true
service:
DISABLE_REGISTRATION: true
ALLOW_ONLY_EXTERNAL_SELF_REGISTRATION: false
auth:
LOCAL_REGISTRATION_DISABLED: true
persistence:
enabled: true
storageClass: ""
accessModes:
- ReadWriteOnce
size: 10Gi
volumeName: ""
existingClaim: ""
annotations:
helm.sh/resource-policy: keep
postgresql:
enabled: true
primary:
persistence:
annotations:
helm.sh/resource-policy: keep
global:
postgresql:
auth:
# NOTE: this chart's own template (templates/gitea/config.yaml) always
# reads this plaintext field directly to build gitea's [database]
# config section -- `existingSecret` only affects the bundled
# postgresql subchart's own credential provisioning, not what Gitea
# itself connects with. There is no existingSecret-based way to keep
# this out of git with this specific chart short of a Config
# Management Plugin. Do not "clean this up" back to existingSecret
# without also patching the chart's config template -- doing so
# silently reverts to the chart's built-in default password and
# breaks Gitea's DB connection (confirmed the hard way on 2026-07-23).
username: gitea
database: gitea
password: ySelvqn2LjZ1fdJ4OFQs5ZlK6VLxHdny
service:
ssh:
type: LoadBalancer
port: 2222
loadBalancerIP: 192.168.7.77
postgresql-ha:
enabled: false