Add ImagePullPolicy and set it to PullAlways when deploying runners #211
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
wonderyl
reviewed
Sep 3, 2025
| Image: h.imageRef, | ||
| Name: "runner", | ||
| Image: h.imageRef, | ||
| ImagePullPolicy: corev1.PullAlways, |
Contributor
There was a problem hiding this comment.
I'm concerning this will make running runners slower. When you release a new node, do you give it a new tag or reuse the tag? I'm asking because technically if you give it a new tag in every build, you won't have the problem of stale images.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
When deploying runners with the latest image, set the ImagePullPolicy to Always to ensure the image is pulled every time.