[v0.37] cherry-picks for v0.37.1 - #4071
Open
crazy-max wants to merge 7 commits into
Open
Conversation
Move the existing exporter setup out of the node build loop without changing its behavior. Environment: Datadog workspace Co-Authored-By: OpenAI GPT-5.6 <noreply@openai.com> Signed-off-by: Tomas Perez Molina <tomas.perezmolina@datadoghq.com> (cherry picked from commit 1715f79)
Prepare each node's cloned exporter options so no node publishes the requested tag before all platforms complete. Environment: Datadog workspace Co-Authored-By: OpenAI GPT-5.6 <noreply@openai.com> Signed-off-by: Tomas Perez Molina <tomas.perezmolina@datadoghq.com> (cherry picked from commit aaf1e92)
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com> (cherry picked from commit 4b2dbec)
A recently started builder should use its StartedAt timestamp to decide whether BuildKit may still be coming up, but not as the absolute deadline for the client readiness wait. When the first client request arrived near the end of that startup window, the wait could inherit only a few milliseconds and fail with DeadlineExceeded even though the builder was still legitimately starting. Give those recent containers a fresh bounded wait from the current time while continuing to skip the wait for established builders. Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com> (cherry picked from commit bd28a1e)
Use the container start time only to decide whether readiness waiting is needed. Start a full timeout immediately before waiting so Docker dial time does not consume the readiness budget. Name the startup window and readiness timeout independently, and cover the exact startup-window boundary. Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com> (cherry picked from commit 310bba9)
Use the caller context for cleanup so slow container and volume removal can finish after the builder-status timeout expires. Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com> (cherry picked from commit 5b02414)
Create shared clients with the enclosing build context so completing one linked target doesn't cancel the Kubernetes connection still used by its siblings. Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com> (cherry picked from commit 8372345)
crazy-max
force-pushed
the
v0.37_picks_0.37.1
branch
from
September 10, 2026 16:53
d730e20 to
0bee4c5
Compare
crazy-max
marked this pull request as ready for review
September 10, 2026 17:14
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
3 participants
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.
backport of: