-
Notifications
You must be signed in to change notification settings - Fork 715
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
kinder: optimize the preparation of upgrade artifacts #2969
kinder: optimize the preparation of upgrade artifacts #2969
Conversation
During the "altering" of the node image used by kinder, there are two two download stages, one to download the init artifacts and one to download upgrade artifacts. For some e2e workflows we have matching init and upgrade versions. This is done just to test the upgrade command and not perform an actual upgrade. It causes the same artifacts to be downloaded two times, which is slow. During the preparation of bits installers, check if the init/upgrade versions match. If so, tell the upgrade bits installer to use the init directory as install source. This results in just copying the bits from the host, instead of downloading them again.
it's actually possible to see this change in action on top of this presubmit job log for this same PR: the artifacts for upgrade are just copied from init. so it works. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123, SataQiu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
During the "altering" of the node image used by kinder, there are two download stages, one to download the init artifacts and one to download upgrade artifacts.
For some e2e workflows we have matching init and upgrade versions. This is done just to test the upgrade command and not perform an actual upgrade. It causes the same artifacts to be downloaded two times, which is slow.
During the preparation of bits installers, check if the init/upgrade versions match. If so, tell the upgrade bits installer to use the init directory as install source. This results in just copying the bits from the host, instead of downloading them again.