-
Notifications
You must be signed in to change notification settings - Fork 61
✨ Use priority queue / ctrl-runtime v0.22.3 / 30m resync #1260
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
Merged
akutz
merged 1 commit into
vmware-tanzu:main
from
akutz:feature/async-watcher-image-watcher-use-priority-queue
Oct 22, 2025
Merged
✨ Use priority queue / ctrl-runtime v0.22.3 / 30m resync #1260
akutz
merged 1 commit into
vmware-tanzu:main
from
akutz:feature/async-watcher-image-watcher-use-priority-queue
Oct 22, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5ffc31b to
93cc13c
Compare
bryanv
approved these changes
Oct 22, 2025
d395a14 to
9ab4a89
Compare
9ab4a89 to
e290349
Compare
e290349 to
c0d1124
Compare
c0d1124 to
abd2df4
Compare
This patch updates the VM controller to use the controller-runtime priority queue feature by default in combination with v0.22.0 of controller-runtime. This feature ensures that reconcile requests that are not part of an initial list or resync have lower priority than those requests enqueued for any other reason. This should allow VM Operator to handle VM reconciliation when the queues are do large due to a high number of VMs. This patch also changes from a 10m resync to 30m, relying on the async watcher to enqueue VMs for reconciliation in a timely manner. This also means other controllers need to ensure they are properly using requeues / mappers to ensure objects are not relying on resync to refresh status in a timely manner.
abd2df4 to
5efe7b2
Compare
Minimum allowed line rate is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do, and why is it needed?
This patch updates the VM controller to use the controller-runtime priority queue feature by default in combination with v0.22.3 of controller-runtime. This feature ensures that reconcile requests that are not part of an initial list or resync have lower priority than those requests enqueued for any other reason. This should allow VM Operator to handle VM reconciliation when the queues are do large due to a high number of VMs.
This patch also changes from a 10m resync to 30m, relying on the async watcher to enqueue VMs for reconciliation in a timely manner. This also means other controllers need to ensure they are properly using requeues / mappers to ensure objects are not relying on resync to refresh status in a timely manner.
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes
NAAre there any special notes for your reviewer:
Please add a release note if necessary: