Skip to content

fix(chart): readiness probe timeout 3s — release v1.9.3 / chart 1.10.3 #60

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
louisgls merged 2 commits into from
Oct 21, 2026
Merged

fix(chart): readiness probe timeout 3s — release v1.9.3 / chart 1.10.3 #60

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
be2027f
fix(chart): readiness probe timeout 1s -> 3s
louisgls Oct 21, 2026
8aab8c3
chore(release): v1.9.3 + chart 1.10.3
louisgls Oct 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,20 @@ Two version streams move independently:

## [Unreleased]

## [1.9.3] — 2026-10-21

Re-cut of 1.9.2 so its signed binaries get published: the release pipeline
stopped on a tooling version check before building them. The application is
unchanged from 1.9.2. Chart `1.10.3` accompanies this release.

### Chart

- **`chart/1.10.3`** — `appVersion` follows the app to `1.9.3`. The readiness
probe now waits up to 3s (was the 1s Kubernetes default). `/readyz` checks
the upstream S3 with a 2s budget, so a slightly slow upstream used to show
up as sporadic `Readiness probe failed` events even though the proxy was
fine.

## [1.9.2] — 2026-10-21

Security maintenance. No functional change over 1.9.1 — same behaviour, patched
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -280,7 +280,7 @@ Top-level value keys:
| `service.type` / `service.port` | `ClusterIP` / `4433` | Standard k8s Service. |
| `ingress.enabled` | `false` | Optional Ingress. |
| `resources` | `cpu: 250m/500m`, `mem: 128Mi/256Mi` | k8s requests/limits. |
| `livenessProbe` / `readinessProbe` | `/healthz` / `/readyz` on `4433` (HTTPS) | Standard probes. |
| `livenessProbe` / `readinessProbe` | `/healthz` / `/readyz` on `4433` (HTTPS); readiness `timeoutSeconds: 3` | Standard probes. `/readyz` checks the upstream (ListBuckets, 2s budget), so keep its timeout above 2s. |
| `autoscaling` | disabled | HPA on CPU/memory. |
| `serviceMonitor` | disabled | Prometheus Operator scrape config. |
| `prometheusRule` | disabled | Alert bundle. |
Expand Down
4 changes: 2 additions & 2 deletions charts/s3proxy/Chart.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,5 +18,5 @@ maintainers:
annotations:
org.opencontainers.image.source: "https://github.com/intrinsec/s3proxy/"
type: application
version: 1.10.2
appVersion: "1.9.2"
version: 1.10.3
appVersion: "1.9.3"
4 changes: 4 additions & 0 deletions charts/s3proxy/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,10 @@ readinessProbe:
path: /readyz # Readiness endpoint
port: 4433
scheme: HTTPS
# /readyz issues a ListBuckets against the upstream and waits up to 2s for
# it. Keep the probe timeout above that, or a slow upstream call is cut by
# the kubelet at the 1s default and logged as a failed probe.
timeoutSeconds: 3

autoscaling:
enabled: false
Expand Down
Loading