fix(ko): Ko builder push vs load behavior #8845
Merged
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.
Ko v0.13.0 introduced a change to the handling of image names when loading images into a Docker daemon (instead of pushing to a registry).
Specifically, ko v0.13.0 assumes that if the image repo name matches the
LocalDomain
field, the build image should be loaded into the Docker daemon, regardless of the values of thePush
andLocal
fields. In fairness, the comment onLocalDomain
says "Use withLocal=true
." 😃. For reference, the implementation of this behavior is in ko'smakePublisher()
function.This change ensures that Skaffold only sets the
LocalDomain
field for images that should be loaded.Fixes: #8760 #8786
Related: ko-build/ko#820