feat(vmclass): add events about available nodes and sizing policies changed #606
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
eofff
force-pushed
the
feat/vmclass/add-events-about-node-and-policy-changes
branch
from
40ac6c9 to
7dd0311
Compare
eofff
changed the title
Signed-off-by: Valeriy Khorunzhin <[email protected]>
eofff
force-pushed
the
feat/vmclass/add-events-about-node-and-policy-changes
branch
from
7dd0311 to
2599df7
Compare
Isteb4k
requested changes
Dec 25, 2024
| @@ -175,3 +202,30 @@ func (h *DiscoveryHandler) maxAllocatableResources(nodes []corev1.Node) corev1.R | |||
| } | |||
| return resourceList | |||
| } | |||
|
|
|||
| func nodeNamesDiff(prev, current []string) (added, removed []string) { | |||
There was a problem hiding this comment.
Cover this fn with unit test please
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.
Description
Using new events api.
Add event when list of available nodes changed.
Add event when sizing policies changed.
Why do we need it, and what problem does it solve?
What is the expected result?
Checklist