From 44be6e2b664c635523b7c733e7a6196096ebd16c Mon Sep 17 00:00:00 2001 From: Glen-Tigera Date: Thu, 3 Sep 2026 17:07:06 -0400 Subject: [PATCH] Proxy Calico OSS e2e test binaries from S3 projectcalico/calico#13566 publishes version-matched Kubernetes e2e test binaries to s3://calico-public//files/e2e/ so a consumer can fetch one architecture instead of unpacking the ~1.2 GB release archive. The bucket only reaches the web through per-prefix proxies here, and /calico/charts/* was the only one, so those objects are currently unreachable from docs.tigera.io. Calico Enterprise needs no equivalent rule because downloads.tigera.io maps to its bucket root. The path mirrors the Enterprise layout, so a consumer resolves a binary the same way for either product. The rule is narrow rather than /calico/:version/files/* to keep the proxied surface to what is published today, and carries no force, so a real docs file still wins. Co-Authored-By: Claude Opus 5 (1M context) --- netlify.toml | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/netlify.toml b/netlify.toml index 21474666ce..f94cc55e05 100644 --- a/netlify.toml +++ b/netlify.toml @@ -144,6 +144,17 @@ command = "[[ $PREVIEW_TYPE == cloudpreview ]] && echo Building deploy preview f status = 200 headers = {X-From = "Netlify"} +# Version-matched Kubernetes e2e test binaries for Calico Open Source, proxied +# from the same bucket as the charts above. Calico releases publish these under +# /files/e2e/, matching the layout Calico Enterprise serves from +# downloads.tigera.io, so a consumer resolves a binary the same way for either +# product. +[[redirects]] + from = "/calico/:version/files/e2e/*" + to = "https://calico-public.s3.amazonaws.com/:version/files/e2e/:splat" + status = 200 + headers = {X-From = "Netlify"} + # FOSSA attribution reports for Calico Enterprise (proxied from S3) [[redirects]] from = "/calico-enterprise/fossa-reports/:version/attribution-report.html"