-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Controller: Optimize sync process. #12918
base: main
Are you sure you want to change the base?
Controller: Optimize sync process. #12918
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: sergeylanzman The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Hi @sergeylanzman. Thanks for your PR. I'm waiting for a kubernetes 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-sigs/prow repository. |
✅ Deploy Preview for kubernetes-ingress-nginx canceled.
|
413e74e
to
8128c81
Compare
501833f
to
4e62cf4
Compare
/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.
/retitle Controller: Optimize sync process.
/triage accepted
/kind bug
/priority backlog
Looks good so far! Please ping us as soon as your WIP is ready for a final review. 🙂
Also I'm tempted to cherry-pick this to release-1.12 and release-1.11. @sergeylanzman @strongjz WDYT?
I wouldn't consider this a bug like the author says, its an optimization. I am torn, this changes how the sync process works, we do our best to ensure compatibility in patch versions. I can see folks arguing that changing how the sync process works should be in a minor release. We have to remember that folks who do gitops push patch changes almost immediately, so with that in mind we should save it for 1.13. |
What this PR does / why we need it:
Add many optimization for sync process. On huge cluster with four digit number of ingress and pods controller take up to 50GB memory and sync process too long. This PR try optimize code for less memory and cpu usage
Types of changes
How Has This Been Tested?
Local tests
Checklist: