-
Notifications
You must be signed in to change notification settings - Fork 1.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
Create shared package for watching Nodes in remote Clusters #2414
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Milestone
Comments
/milestone v0.3.4 |
/kind cleanup |
k8s-ci-robot
added
the
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
label
Apr 27, 2020
/milestone v0.3.x |
Closed #2577 in favor of this issue |
/milestone v0.3.6 |
/close |
@vincepri: Closing this issue. In response to this:
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/cleanup
Categorizes issue or PR as related to cleaning up code, process, or technical debt.
Note: this is only applicable once #2250 is merged
Goals
Non-Goals/Future Work
User Story
As a developer I would like the controllers I am writing to be able to react to events on Nodes in remote clusters so that my controller can reconcile the status of objects or take action based on the state of the Nodes
Detailed Description
The Machine Health Checking controller implemented primarily in #2250 needed to watch Nodes in remote clusters to be able to react as quickly as possible to Nodes which might be going unhealthy.
To achieve this, a method was implemented that keeps a map of clusters to informers that allows the controller to add event handlers for events coming from nodes in remote clusters.
This could be moved into the
external
package and made more reusable by making it a method on a new struct which keeps the map, lock and controller as fieldsAnd changing the signature of the
WatchClusterNodes
method to allow the event handler to be passed.It is currently assumed that each controller would only want to register one event handler per cluster, I'm not sure how true that is and as such, we should try to add the ability to check if event handler functions have been registered and add more if required.
/kind proposal
The text was updated successfully, but these errors were encountered: