fix(a2a): startupProbe + tolerant liveness + resource headroom - #138
Merged
Conversation
…pod flapping) The a2a-shared pod was restart-flapping (31 restarts) under cluster strain: liveness /healthz had no timeoutSeconds (default 1s), so a briefly-slow health check failed and kubelet killed the pod. Add a startupProbe (up to ~5min to clone tenants + boot), make liveness/readiness tolerant (5s timeout, 6 failures), and bump resources (memory headroom + CPU burst, requests kept modest to still schedule on strained durable nodes). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session-Id: 17fb89fd-3579-433b-a6c4-9c9e7f3ec549
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
1 participant
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.
Stops the a2a-shared pod's restart-flapping (31 restarts): liveness /healthz had no timeoutSeconds (1s default) so slow-under-load checks killed it. Adds startupProbe (~5min clone+boot grace), tolerant liveness/readiness (5s timeout, 6 failures), and modest resource bump (memory headroom + CPU burst; requests still schedulable on strained nodes).