Files

T

Erki AasandClaude Opus 4.8 e17b0e0b41 Make gitea OAuth2 JWT_SECRET a valid, stable 43-char key

GITEA__OAUTH2__JWT_SECRET must base64url-decode to 32 bytes. The size-32
claim decoded to 24 bytes, so 1.27 rejected it and generated its own key
on each boot; since app.ini lives on an emptyDir that regenerated every
restart and logged out all OAuth2 clients. size 43 decodes to 32 bytes,
so the rotated key is accepted and stays stable across restarts.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-09-15 22:38:10 +03:00

application.yaml

Make gitea OAuth2 JWT_SECRET a valid, stable 43-char key

2026-09-15 22:38:10 +03:00

kustomization.yaml

gitea to minimal kustomize

2026-01-05 06:26:23 +02:00

mariadb.yaml

gitea to minimal kustomize

2026-01-05 06:26:23 +02:00

README.md

gitea to minimal kustomize

2026-01-05 06:26:23 +02:00

README.md

Gitea

This application is managed by ArgoCD

Should ArgoCD be down manifests here can be applied with:

kustomize build . | kubectl apply -f -

Gitea DOES NOT go through Traefik. It has its own IP because ssh :22 would conflict with kube worker ssh. On its own IP, at the moment it doesn't flirt with Traefik — also has its own certificate.