Repository navigation
fix(chart): readiness probe timeout 3s — release v1.9.3 / chart 1.10.3 - #60
Merged
Merged
Conversation
/readyz pings the upstream with ListBuckets under a 2s budget (readinessProbeTimeout), but the chart left the probe at the Kubernetes default timeoutSeconds: 1. Any upstream call between 1s and 2s was cut by the kubelet and logged as "Readiness probe failed ... context canceled". Seen on kube02 on both 1.9.1 and 1.9.2 pods, several pods failing in the same second (upstream latency, not the proxy). Single failures stayed under failureThreshold, so no traffic was lost — only noise. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Re-cut of 1.9.2 so the Release workflow publishes its signed binaries: the v1.9.2 run stopped on the stale golangci-lint pin in release.yml (fixed in this branch). Application code is unchanged from 1.9.2. Chart 1.10.3 follows appVersion to 1.9.3 and carries the readiness probe timeout fix. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #59, which merged with the lint-pin commit only; these two commits landed on the branch just after.
Changes
fix(chart): readiness probe timeout 1s → 3s./readyzpings the upstream (ListBuckets) with a 2s budget, but the chart lefttimeoutSecondsat the k8s default of 1s. On kube02 (cockpit) this shows as sporadicReadiness probe failed … context canceled, several pods in the same second, on both 1.9.1 and 1.9.2 — upstream latency cut by the kubelet. Never crossedfailureThreshold, so noise only. README values table updated.Checks
helm lint charts/s3proxyOK; rendered probe hastimeoutSeconds: 3After merge
Tag
v1.9.3+chart-v1.10.3, bump cockpit to 1.10.3.🤖 Generated with Claude Code