hook
hook copied to clipboard
tinkerbell
Tink worker image pull retry
Description
Image pull retry for tink-worker image
Why is this needed
There could be races where linuxkit network or dns may not have been fully set up and functional yet and image pull fails because of that.
Fixes: #
Implement image pull retry loop for tink-worker image. This loop attempts an image pull every 5 seconds, upto 10 times
How Has This Been Tested?
Tested by re-running a full provisioning workflows on bare metal server and simulate image pull failures artificially to test out the retry logic.
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have:
- [ ] updated the documentation and/or roadmap (if required)
- [ ] added unit or e2e tests
- [ ] provided instructions on how to upgrade
