Set k8s imagePullPolicy to Always #455
Open
Conversation
This file contains 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
To prevent certain corner cases where images could be pushed with the same tag to a container registry, the imagePullPolicy for k8s jobs should use "Always" to ensure the container registry is always checked for newer versions of the container, even if one is already cached locally. This shouldn't negatively impact performance as it won't re-pull an image if it already exists locally and there isn't a newer one available on the registry. Signed-Off-By: Robert Clark <[email protected]>
terrykong
approved these changes
Jan 16, 2025
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.
To prevent certain corner cases where images could be pushed with the same tag to a container registry, the imagePullPolicy for k8s jobs should use "Always" to ensure the container registry is always checked for newer versions of the container, even if one is already cached locally. This shouldn't negatively impact performance as it won't re-pull an image if it already exists locally and there isn't a newer one available on the registry.