fix(ical-proxy): roll out main-73b5d97 (WriteTimeout above fetch timeout) #1038

2026-09-27T16:14:24Z

Ghost commented

2026-09-27 16:14:24 +00:00

What

Bump the pinned ical-proxy image in kubernetes/apps/ical-proxy/deployment.yaml from main-4783abe to main-73b5d97, and update the comment above it.

Why

main-73b5d97 is the merge of konairius/ical-proxy #9 (REN-232). It is the only change since main-4783abe: the server WriteTimeout rises from 10s to 40s (30s upstream fetch timeout + 10s headroom). Before, a slow-but-legitimate upstream (10-30s) had its connection closed before /proxy could write the response.

Verification

git log 4783abe..73b5d97 in ical-proxy = exactly 7a278e2 + merge 73b5d97 (reviewed in REN-237); diff touches only server/main.go + its test.
Registry: gitea.renner.uno/konairius/ical-proxy:main-73b5d97 manifest returns 200 (anonymous pull, same as the current tag).
Not applied to the cluster yet: rollout happens when Flux reconciles this merge. Post-merge check: new pod Ready, /health healthy, a slow upstream through /proxy completes.

Production impact

One Deployment, image-only change, normal rolling update driven by Flux. No config, probe, Service, Ingress or RBAC change. No client-visible change except slow upstreams no longer being cut off.

Revert

Revert this commit (sets the tag back to main-4783abe); Flux rolls the previous image.

Refs: REN-239, REN-232

🤖 Generated with Claude Code

## What Bump the pinned ical-proxy image in `kubernetes/apps/ical-proxy/deployment.yaml` from `main-4783abe` to `main-73b5d97`, and update the comment above it. ## Why `main-73b5d97` is the merge of konairius/ical-proxy #9 (REN-232). It is the only change since `main-4783abe`: the server `WriteTimeout` rises from 10s to 40s (30s upstream fetch timeout + 10s headroom). Before, a slow-but-legitimate upstream (10-30s) had its connection closed before `/proxy` could write the response. ## Verification - `git log 4783abe..73b5d97` in ical-proxy = exactly 7a278e2 + merge 73b5d97 (reviewed in REN-237); diff touches only `server/main.go` + its test. - Registry: `gitea.renner.uno/konairius/ical-proxy:main-73b5d97` manifest returns 200 (anonymous pull, same as the current tag). - Not applied to the cluster yet: rollout happens when Flux reconciles this merge. Post-merge check: new pod Ready, `/health` healthy, a slow upstream through `/proxy` completes. ## Production impact One Deployment, image-only change, normal rolling update driven by Flux. No config, probe, Service, Ingress or RBAC change. No client-visible change except slow upstreams no longer being cut off. ## Revert Revert this commit (sets the tag back to `main-4783abe`); Flux rolls the previous image. Refs: REN-239, REN-232 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Ghost added 1 commit 2026-09-27 16:14:24 +00:00

fix(ical-proxy): roll out main-73b5d97 (WriteTimeout above fetch timeout)

ci/woodpecker/pr/ci-manifests-test Pipeline was successful

Details

ci/woodpecker/pr/ci-scripts-test Pipeline was successful

Details

ci/woodpecker/pr/pr-review Pipeline was successful

Details

1e680eda4f

Bump the pinned ical-proxy image from main-4783abe to main-73b5d97.
The only change is konairius/ical-proxy #9 (REN-232): the server
WriteTimeout goes from 10s to 40s (30s upstream fetch timeout + 10s
headroom), so a slow-but-legitimate upstream is no longer cut off
before /proxy can write its response.

Refs: REN-239, REN-232

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

Ghost approved these changes

2026-09-27 16:18:16 +00:00

Ghost left a comment

Approve at 1e680eda4fa99bba573a55b6850c98caa8a79a17.

Checked:

Diff: only kubernetes/apps/ical-proxy/deployment.yaml. The image tag goes main-4783abe → main-73b5d97, plus a comment. No probe, Service, Ingress or RBAC change.
ical-proxy git log 4783abe..73b5d97: 7a278e2 and merge 73b5d97 only (reviewed in REN-237). server/main.go now has WriteTimeout = proxyFetchTimeout (30s) + 10s headroom, and the client Timeout uses the same constant.
Registry, anonymous pull token: main-73b5d97 manifest 200 (sha256:2a518408…, amd64, built 2026-09-27T16:11Z, after the merge). The current main-4783abe also returns 200.
Blast radius: 2 replicas, default RollingUpdate gated by the /health readinessProbe. A bad image never becomes Ready and the old pods keep serving. The Traefik ingress sets no response timeout that would cut the 40s window short.
Revert: revert this commit and Flux rolls back to main-4783abe.

Approve at `1e680eda4fa99bba573a55b6850c98caa8a79a17`. Checked: - Diff: only `kubernetes/apps/ical-proxy/deployment.yaml`. The image tag goes `main-4783abe` → `main-73b5d97`, plus a comment. No probe, Service, Ingress or RBAC change. - ical-proxy `git log 4783abe..73b5d97`: 7a278e2 and merge 73b5d97 only (reviewed in REN-237). `server/main.go` now has WriteTimeout = proxyFetchTimeout (30s) + 10s headroom, and the client Timeout uses the same constant. - Registry, anonymous pull token: `main-73b5d97` manifest 200 (sha256:2a518408…, amd64, built 2026-09-27T16:11Z, after the merge). The current `main-4783abe` also returns 200. - Blast radius: 2 replicas, default RollingUpdate gated by the `/health` readinessProbe. A bad image never becomes Ready and the old pods keep serving. The Traefik ingress sets no response timeout that would cut the 40s window short. - Revert: revert this commit and Flux rolls back to `main-4783abe`.

Ghost merged commit 89af8c355c into master

2026-09-27 16:18:16 +00:00

Ghost referenced this issue from a commit

2026-09-27 16:18:17 +00:00

Merge pull request 'fix(ical-proxy): roll out main-73b5d97 (WriteTimeout above fetch timeout)' (#1038) from atlas/ren-239-ical-proxy-main-73b5d97 into master

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: konairius/homelab#1038