coulomb/railiance-cluster
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-cluster/install/traefik
History
Exact
codex d775ba8fa7
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
RCLUSTER-WP-0020-T03: prepare wave-2 requests for cert-manager, traefik and k3s addons 
Requests only, no apply. cert-manager values (codifies out-of-band
acme nameservers arg), traefik HelmChartConfig resources, and a founder-run
.skip-based edit script for coredns/metrics-server/local-path-provisioner.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 276069@bnt-lap001
Assistant-Session: 2e192b3d-b3e8-4403-94d4-d55a2c8b476c
2026-10-22 00:02:21 +02:00
..
railiance01-helmchartconfig.yaml RCLUSTER-WP-0020-T03: prepare wave-2 requests for cert-manager, traefik and k3s addons 2026-10-22 00:02:21 +02:00
README.md Document independent node pull verification for ingress changes 2026-10-13 20:26:30 +02:00

README.md

Railiance01 Traefik upload timeout

Forgejo OCI blob uploads were cut off at 60 seconds with unexpected EOF and HTTP 499/500. The shared HTTPS entry point now declares a bounded 600-second request-read budget via the k3s-managed HelmChartConfig. It applies to all websecure request bodies; it does not disable timeouts or change authentication.

Validated against the installed chart traefik-38.0.201+up38.0.2 and its live values: the rendered difference is exactly one additional argument. Traefik remains 3.6.7. The separate HelmChartConfig survives k3s reconciliation; do not edit the generated Deployment or packaged traefik.yaml.

After node/capacity review, run from this repository:

ssh railiance01 'kubectl apply --server-side --dry-run=server -f -' < install/traefik/railiance01-helmchartconfig.yaml
ssh railiance01 'kubectl diff -f -' < install/traefik/railiance01-helmchartconfig.yaml
ssh railiance01 'kubectl apply --server-side -f -' < install/traefik/railiance01-helmchartconfig.yaml

Wait for the Helm controller to finish and the replacement Traefik pod to become Ready. Verify the actual argument, HTTPS endpoints and a previously failing large OCI publication. Confirm its registry digest and independently pull the immutable reference with sudo k3s crictl pull <image-reference> on railiance01. The verified pull receipt records the first successful release after this change.

Rollback: set the argument to 60s in this source and reapply with the same checks; this restores the former upload limitation.

References: Traefik read timeout and k3s customization.