Isolate chained PaperTrade image builds - #12
Merged
Conversation
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.
BUILD_TARGET=allreused one Kaniko container for the runtime-base and app builds. The first executor invocation left its generated root filesystem behind, which caused the second invocation's package setup to fail before publishing the app image.The combined path now runs the runtime-base and app phases as separate helper invocations, so each gets a fresh builder pod. It carries the exact runtime-base digest into the app phase and production workflow output, and the deployment workflow uses this isolated combined path when a base refresh is requested.
Validation:
bash -n scripts/k8s/build-local-image.sh;git diff --check. The same two phases were also proven live with separate builder pods while producing the candidate for this maintenance window.