rock/homelab
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: set proxy-body-size 0 on the Forgejo chart Ingress

Browse Source 
Two Ingresses claim forgejo.riotpiao.com and nginx honours the older chart one,
so the annotation on the other never applied and OCI pushes over 1m got 413.
This commit is contained in:
Story Crater Bot
2026-08-19 22:25:51 -07:00
parent 720181c900
commit 523b950759
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/bootstrap/phase3-forgejo/forgejo-values.yaml
+12
View File
@@ -78,6 +78,18 @@ ingress:
className: nginx
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
# This chart Ingress and the hand-written one in
# k8s/bootstrap/ingress/ingress.yaml both claim forgejo.riotpiao.com.
# ingress-nginx breaks the tie by oldest creationTimestamp, and the chart's
# is older, so it is the one actually serving — the annotations on the other
# have never applied. Duplicate should be removed; until then these must
# live here or they do nothing.
#
# proxy-body-size 0 is required for the OCI registry: nginx defaults to 1m,
# so any image layer above that fails the push with 413.
nginx.ingress.kubernetes.io/proxy-body-size: "0"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
hosts:
- host: forgejo.riotpiao.com
paths: