fix(agent-pod): remote tui session for multi-agent

k8s/apps/api/kong-values.yaml

@@ -57,6 +57,17 @@ env:
   # nginx Ingress in ingress.yaml; both hops have to be unbuffered or the
   # buffered one dominates.
   nginx_proxy_proxy_buffering: "off"
+  # Any plugin that rewrites the request body — request-transformer on the
+  # llm-chat-* routes — reads it through `kong.request.get_body()`, and that
+  # returns nothing once nginx has spilled the body past
+  # client_body_buffer_size into a temp file. The plugin then re-serializes a
+  # body with no `messages`, and the upstream answers
+  #   HTTP 400 {"error":{"message":"[] is too short - 'messages'"}}
+  # Measured on /v1/ornith/chat/completions: 10588 B -> 200, 11088 B -> 400.
+  # An agent request carrying tool schemas clears that in one turn, so the
+  # buffer has to hold a whole conversation, not a chat message.
+  nginx_http_client_body_buffer_size: "16m"
+  nginx_http_client_max_body_size: "16m"
 
 ingressController:
   enabled: true
@@ -107,6 +118,16 @@ podDisruptionBudget:
   enabled: true
   minAvailable: 1
 
+# Status listener (metrics/health) is on by default at :8100 (chart default,
+# verified via `helm show values`). This just wires the ServiceMonitor the
+# chart already knows how to generate for it, so kong_http_requests_total /
+# kong_latency_* / kong_bandwidth_bytes land in Prometheus. Paired with the
+# cluster-wide `prometheus` KongClusterPlugin in kong-metrics.yaml.
+serviceMonitor:
+  enabled: true
+  labels:
+    release: kube-prometheus-stack
+
 # Spread the two replicas across nodes; `ScheduleAnyway` so a single-node
 # situation degrades to co-location instead of leaving a pod Pending.
 topologySpreadConstraints: