-
Notifications
You must be signed in to change notification settings - Fork 185
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
autoscaler: update storageautoscaler design doc #3105
base: main
Are you sure you want to change the base?
Conversation
06ec85a
to
5ba07df
Compare
/assign @travisn @BlaineEXE @leelavg @nb-ohad |
5ba07df
to
f7f9c26
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: parth-gr The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
f7f9c26
to
80f27b4
Compare
docs/design/storage-auto-scale.md
Outdated
|
||
3) Check if the expansion is in progress: | ||
|
||
1) Load the actualOsdCount and actualOsdSize from the syncMap. |
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.
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.
Agreed, seems like the scraper has no reason to query the actual osd count and size. All the scraper is concerned with, is whether it appears the cluster is getting full.
So it seems to me the controller should just directly query prometheus for the osd count and size.
80f27b4
to
6323f07
Compare
6323f07
to
1ae5b28
Compare
Currrently the controller was dependent on reading cr status, update the controller to not depend on cr status Signed-off-by: parth-gr <[email protected]>
1ae5b28
to
7592e48
Compare
@parth-gr: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
Currrently the controller was dependednt on reading cr status, update the design so controller to not depend on cr status