Refresh and pin the PaperTrade runtime base - #11
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
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.
The local Kaniko path could reuse the cached
apt-get upgradelayer when rebuilding PaperTrade's runtime base. A requested runtime refresh could therefore produce a new app image on an old OS package set; the current production candidate demonstrated this with four fixable high-severity findings.This change disables RUN-layer caching for the heavy runtime-base build, requires every registry push to yield a digest, and passes the freshly built base into the app build by digest. The release manifest records the base digest for auditability.
Validation:
bash -n scripts/k8s/build-local-image.sh;git diff --check.