-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Decouple kubespray-defaults from download #10626
Decouple kubespray-defaults from download #10626
Conversation
Hi @VannTen. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
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.
Wow, thank you for the improvement! Indeed there are most likely a good amount of performance improvement we could do in kubespray.
/lgtm
8ff0dc1
to
0a84de9
Compare
Rebased to re-trigger the CI, sorry for the noise @MrFreezeex |
No worries! |
0a84de9
to
bc4e5ea
Compare
I guess git is better at resolving conflicts than tide, because I had no merge conflicts while rebasing ^^. |
(adding back my lgtm after the rebase) |
/assign @floryut |
bc4e5ea
to
46515b0
Compare
c28b7d3
to
86a83b2
Compare
/assign @liupeng0518 This ones is pretty "rebase annoying" even though git can solve the presumed conflicts with no problem... |
/approve |
e7fca2e
to
4a138ba
Compare
4a138ba
to
7ef4a90
Compare
7ef4a90
to
308ea0e
Compare
308ea0e
to
f53e02b
Compare
Hmmm I think the CI failure might be legit 🤔 EDIT: Just saw the linked issue about this failure 👍 |
Avoids doing re-importing the download role on every invocation of kubespray-defaults (and skipping everything). This has a measurable effect on playbook performance.
f53e02b
to
987268c
Compare
@MrFreezeex looks like CI will finally pass on this, can you review ? (Pretty please 🙏 ) |
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.
Sure, thanks again!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liupeng0518, MrFreezeex, VannTen 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 |
* Decouple role kubespray-defaults from download Avoids doing re-importing the download role on every invocation of kubespray-defaults (and skipping everything). This has a measurable effect on playbook performance. * Update docs refering to moved download defaults
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
This moves all defaults variable contained into the download role into kubespray-defaults, thus avoiding the need for the
kubespray-defaults role to add a dependency on dowload only to load variable (and doing a lot of nothing as described in the linked issue).
I tested this on a 3-master 3-etcd 9-nodes cluster, where it takes around 5 minutes less (this is not the exact same patch, because my cluster is in 1.25)
This was running upgrade-cluster.yml, with no real changes (the cluster was already at the target version).
With the patch
Without the patch
Which issue(s) this PR fixes:
Fixes #9279
Special notes for your reviewer:
There is a lot of potential further cleanup, but I tried to keep this simple.
In particular:
Does this PR introduce a user-facing change?: