Using Kubernetes Informer to refactor code for scheduler's events #118
Conversation
This file contains 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
|
TODO: This PR will be merged after finishing the implementation on Kubernetes Event parsing. |
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.
The scheduler spun up a Go process to manage execution of a Plugin. Each of the process held a connection to Kubernetes cluster using Kubernetes Watch class. The connection often closed by the default "time-to-alive", which was a few minutes. To improve the connectivity and reduce the number of connection, Kubernetes Informer is implemented. Internally, the nodescheduler.go handles Kubernetes events from the Informer.
Additionally, scheduler events that are sent to the cloud to inform users about Plugin execution are improved. The events include when a Kubernetes Pod for Plugin is created and when the Pod container finishes pulling container image. This detailed messages will provide better understanding on what is actually happening in the node.