Files
infra-librechat/k8s/ingress/ingress.yaml
T
2026-08-23 08:12:21 +02:00

40 lines
1.5 KiB
YAML

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: librechat
namespace: librechat
annotations:
nginx.ingress.kubernetes.io/proxy-body-size: "20m"
nginx.ingress.kubernetes.io/proxy-read-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-send-timeout: "3600"
nginx.ingress.kubernetes.io/proxy-buffering: "off"
nginx.ingress.kubernetes.io/proxy-http-version: "1.1"
nginx.ingress.kubernetes.io/proxy-buffer-size: "128k"
nginx.ingress.kubernetes.io/proxy-buffers-number: "8"
nginx.ingress.kubernetes.io/proxy-busy-buffers-size: "256k"
# configuration-snippet (WebSocket Upgrade/Connection headers) removed —
# this cluster's ingress-nginx has snippet annotations disabled
# (admission webhook rejects them outright). If any LibreChat feature
# turns out to need raw WebSocket upgrade specifically (vs. the SSE/
# HTTP-1.1 streaming already covered by proxy-buffering/proxy-http-version
# above), this needs a different mechanism — e.g. a ConfigMap-based
# global nginx snippet if the cluster admin allows one, since per-Ingress
# snippets are blocked here.
spec:
ingressClassName: nginx
tls:
- hosts:
- librechat.sttlab.local
secretName: sttlab-tls
rules:
- host: librechat.sttlab.local
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: librechat
port:
number: 80