-
Notifications
You must be signed in to change notification settings - Fork 96
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
feat(NodeController): made node polling interval configurable #256
feat(NodeController): made node polling interval configurable #256
Conversation
3bc0c8c
to
9e2bebc
Compare
Signed-off-by: Omri Cohen <[email protected]>
9e2bebc
to
b283985
Compare
Hi @omric-runai , Thanks for the PR. lgtm |
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.
@avishnu @abhilashshetty04 Since this is configurable, I think we need a helm value and template change to accommodate this?
Yes, we need a configurable parameter in the helm values.yaml |
… Start Signed-off-by: Omri Cohen <[email protected]>
05695bd
to
0f543ac
Compare
@omric-runai Thanks for the PR. Would you be interested in raising a helm chart change for allowing configuring this from Helm Chart? You can raise a separate PR for that if you want. |
Why is this PR required? What issue does it fix?:
This PR makes the polling interval of the node configurable, allowing users to get a higher update rate for their csistoragecapacities, and preventing scheduling issue.
What this PR does?:
This PR adds a new flag,
--node-polling-interval
, with a default value of 60s (same as the currant hard-coded value), which controls the polling rate of the node.Does this PR require any upgrade changes?:
No.
If the changes in this PR are manually verified, list down the scenarios covered::
Any additional information for your reviewer? :
N/A
Checklist:
<type>(<scope>): <subject>