Files
devops-infra-helm-charts-gcp/helm-overrides/k8s-admin-prd-ase1/gitea/custom-values.yaml
T
2026-08-31 00:50:37 +05:30

66 lines
2.1 KiB
YAML

gitea:
# Adopting the standalone install from localvm-kubernetes-setup's
# deploy_gitea.sh (helm release "gitea", namespace "gitea") — same
# config, translated to values so it's GitOps-managed from here on.
# See devops-infra-argo-config values/admin/incubator-infra-k8s-admin-prd-ase1-values.yaml
# for the nameOverride that makes Argo's render match the existing
# release/object names instead of creating a second Gitea.
#
# sqlite + valkey/postgres disabled: sqlite is enough for a lab, and
# the valkey-cluster pod was stuck Pending until the StorageClass was
# fixed (claude.md issue #2/#3) — disabling it avoids that dependency.
# persistence.size must stay 10Gi to match the already-bound PVC —
# local-path-provisioner doesn't support volume expansion.
persistence:
size: 10Gi
postgresql:
enabled: false
postgresql-ha:
enabled: false
valkey:
enabled: false
valkey-cluster:
enabled: false
resources:
requests:
cpu: 100m
memory: 300Mi
limits:
memory: 500Mi
gitea:
config:
database:
DB_TYPE: sqlite3
actions:
ENABLED: true
admin:
username: gitadmin
# The running install set this via a plaintext --set-string flag
# at install time — the admin account already exists, so switching
# to existingSecret here doesn't touch it (Gitea's admin-creation
# Job is install-time only, doesn't re-run on upgrade). Still worth
# creating this Secret now so a future full reinstall doesn't fail
# on a missing values reference:
# kubectl -n gitea create secret generic gitea-admin-credentials \
# --from-literal=username=gitadmin \
# --from-literal=password='<the password you already set>'
existingSecret: gitea-admin-credentials
email: "admin@local.lab"
ingress:
enabled: true
className: contour
hosts:
- host: gitea.192.168.1.7.nip.io
paths:
- path: /
pathType: Prefix
- host: gitea.100.90.248.118.nip.io
paths:
- path: /
pathType: Prefix