feat: add metrics to show target size of every node group #6361
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 type of PR is this?
/kind feature
What this PR does / why we need it:
This PR aims to add a new metric that displays the target size of all node groups.This metric is essential for obtaining a clear understanding of the target size of each node group while using the cluster autoscaler.
for example, we can on comparing this metric with the number of Kubernetes nodes to determine if the environment behaves as expected.This is crucial in detecting issues promptly, especially in the production environment.
The periodic update of this value has already been implemented in the UpdateNodes function of ClusterStateRegistry.We just need to add the reporting metrics functionality.This method does not increase the number of calls to the cloud provider nor does it affect other logic.
We kindly request your review of this PR and your thoughts on the proposed implementation.
Thank you for your time and consideration.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: