-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rkt: Force rkt fetch
to fetch from remote to conform the image pull policy.
#31378
rkt: Force rkt fetch
to fetch from remote to conform the image pull policy.
#31378
Conversation
rkt fetch
to fetch from remote to conform the fetch policy.rkt fetch
to fetch from remote to conform the image pull policy.
Since kubelet only calls Unfortunately, because it appears We should update the known issues to note this new and less-egregious known-issue as well. Reviewed 1 of 1 files at r1. Comments from Reviewable |
2076516
to
4deb1f4
Compare
Link rkt/rkt#2937 in the comments. |
4deb1f4
to
de402ac
Compare
@k8s-bot test this please, issue #IGNORE |
GCE e2e build/test passed for commit de402ac. |
Automatic merge from submit-queue |
Fix #27646
Use
--no-store
option forrkt fetch
to force it to fetch from remote.However,
--no-store
will fetch the remote image regardless of whether the content of the image has changed or not.This causes performance downgrade when the image tag is ':latest' and the image pull policy is 'always'.
The issue is tracked in rkt/rkt#2937.
This change is