From 75c73fa72a70fdfd2c48b98813603d720166f859 Mon Sep 17 00:00:00 2001
From: OdooSky v3 <m@havari.me>
Date: Mon, 11 May 2026 19:48:22 +0200
Subject: [PATCH] fix(traefik): raise websecure read/write timeouts to 1h for
 bundle uploads (chart 0.7.7)

---
 Chart.yaml  |  4 ++--
 values.yaml | 11 +++++++++++
 2 files changed, 13 insertions(+), 2 deletions(-)

diff --git a/Chart.yaml b/Chart.yaml
index cc687fe..8707059 100644
--- a/Chart.yaml
+++ b/Chart.yaml
@@ -23,8 +23,8 @@ description: |
       Git).
 
 type: application
-version: 0.7.6
-appVersion: "0.7.6"
+version: 0.7.7
+appVersion: "0.7.7"
 
 # All 6 subcharts now resolve from registry.odoosky.cloud (mirrored
 # 2026-05-08, KEDA stack added 2026-05-09). Mirror-first discipline
diff --git a/values.yaml b/values.yaml
index a2f9b9e..0c9b61b 100644
--- a/values.yaml
+++ b/values.yaml
@@ -128,6 +128,17 @@ cert-manager:
 # a default ingress for the registry + future platform endpoints.
 traefik:
   enabled: true
+  # Long upload timeouts on websecure. Tower's bundle upload endpoint
+  # (POST /api/migrations) streams 100s of MB; the upstream Traefik
+  # 5-min default readTimeout aborts the connection mid-upload on slow
+  # links, surfacing as HTTP/2 PROTOCOL_ERROR in the browser. Raise to
+  # 1h so 400+ MB bundles complete. Lab1's standalone Traefik (helm-
+  # installed outside this chart) was given the same override via
+  # `helm upgrade --reuse-values` on 2026-05-11 — keep these two in
+  # lockstep so a customer cluster doesn't silently regress.
+  additionalArguments:
+    - --entryPoints.websecure.transport.respondingTimeouts.readTimeout=3600s
+    - --entryPoints.websecure.transport.respondingTimeouts.writeTimeout=3600s
   service:
     type: LoadBalancer
   # Platform-level HTTP → HTTPS redirect. Without this, browsers that