Skip to content

Commit a54fa18

Browse files
[linstor-gui] Bump nginx proxy buffer for oauth2-proxy session cookies
Keycloak access+refresh+id tokens push the oauth2-proxy session cookie to ~8-10 KB (split across multiple Set-Cookie headers), which overflows ingress-nginx's default proxy_buffer_size and produces "upstream sent too big header" -> HTTP 502 on /oauth2/callback right after a successful Keycloak login. Mirror the dashboard ingress: proxy-buffer-size: 100m and proxy-buffers-number: "4". Verified on dev10 — unauthenticated requests now return 302 to Keycloak instead of 502. Co-Authored-By: Claude Opus 4.6 <[email protected]> Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent f53d3dd commit a54fa18

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

‎packages/system/linstor-gui/templates/ingress.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,6 +25,13 @@ metadata:
2525
acme.cert-manager.io/http01-ingress-class: {{ $exposeIngress }}
2626
{{- end }}
2727
nginx.ingress.kubernetes.io/proxy-body-size: 100m
28+
# Keycloak access+refresh+id tokens make the oauth2-proxy session
29+
# cookie ~8–10 KB (split across multiple Set-Cookie headers), which
30+
# overflows the default proxy_buffer_size and causes "upstream sent
31+
# too big header" -> HTTP 502 on /oauth2/callback. Same numbers as
32+
# dashboard ingress.
33+
nginx.ingress.kubernetes.io/proxy-buffer-size: 100m
34+
nginx.ingress.kubernetes.io/proxy-buffers-number: "4"
2835
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
2936
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
3037
spec:

0 commit comments

Comments
 (0)