-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
do not hold the lock after controller has started #178
do not hold the lock after controller has started #178
Conversation
This enables controller to be able to create new watches after it has started. This is required for cases where you are writing some meta-controller which discovers new types to watch during the reconcilation.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: droot 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 |
@DirectXMan12 did some analysis and found reconciliation workers are accessing thread-safe fields like |
I'll take a look when I'm a bit more coherent -- at a glance this looks ok, but I'd like to take a bit closer look |
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.
I don't see this as having an issue because the Queue is thread safe. We could use this change :)
/lgtm |
…ter-start do not hold the lock after controller has started
Update GitBook doc generation page
This enables controller to be able to create new watches after it has started.
This is required for cases where you are writing some meta-controller
which discovers new types to watch during the reconcilation.