feat: persist messages separately and update ingress docs
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# deployments/k8s/ingress.yaml
|
||||
# Ingress для shared-sqs на домене qu.kube5s.ru
|
||||
# Created: 2026-04-09, Updated: 2026-04-10
|
||||
# Created: 2026-04-09, Updated: 2026-04-11
|
||||
apiVersion: networking.k8s.io/v1
|
||||
kind: Ingress
|
||||
metadata:
|
||||
@@ -11,6 +11,13 @@ metadata:
|
||||
nginx.ingress.kubernetes.io/proxy-body-size: 10m
|
||||
nginx.ingress.kubernetes.io/proxy-read-timeout: "30"
|
||||
nginx.ingress.kubernetes.io/proxy-send-timeout: "30"
|
||||
# Fix: 64KB+ payload (boto3/urllib3 2.0 шлёт headers и body отдельными TCP write,
|
||||
# botocore убирает TCP_NODELAY → последние ~16KB body не доходят за client_body_timeout).
|
||||
# Решение: proxy-request-buffering=off стримит body напрямую в backend без ожидания полного тела.
|
||||
nginx.ingress.kubernetes.io/client-body-buffer-size: "512k"
|
||||
nginx.ingress.kubernetes.io/proxy-request-buffering: "off"
|
||||
nginx.ingress.kubernetes.io/server-snippet: |
|
||||
client_body_timeout 120s;
|
||||
spec:
|
||||
ingressClassName: nginx
|
||||
rules:
|
||||
|
||||
Reference in New Issue
Block a user